On this page

Migrate From mParticle

Use Amplitude for both your Analytics and CDP needs. This document covers the steps to:

  1. Migrate your Source and Destination configuration.
  2. Update SDK implementation to send data to Amplitude.
  3. Validate the migration is successful.

The following table maps mParticle offerings to their Amplitude equivalents.

mParticleAmplitude
ConnectionsSources & Destinations
AudiencesAudiences
Data Management

Recommended best practice

Follow a strict release process and configure multiple environments. Validate changes within each environment before deploying.

Add a source

To add a new source:

  1. From Data, click Sources in the Connections section.
  2. Click Add Source.
  3. Browse or search for the source you want to add.
  4. Follow the on-screen prompts.

For detailed instructions, refer to the documentation for the source you want to add.

Update SDK implementation

Both mParticle and Amplitude SDKs capture first-party data by tracking user interactions. Aside from syntax differences, they work similarly. The following table maps concepts between mParticle and Amplitude.

mParticleAmplitudeNotes
app_keyapi_keyUnique key to validate source of the data.
WorkspaceProjectProjects allow you to organize your data.
UserUserUser who is performing action.
IdentifyIdentifyIdentify updates properties/attributes of the user.
EventEventEvents track the action user is performing.
ScreenEventCreate an Event to track Screen views.
PageEventCreate an Event to track Page views.
GroupA Group is a collection of users. In Amplitude, one user can belong to multiple groups. Each group can have properties available to query or forward on actions performed by any user in the group.
KitsPluginsPlugins extend Amplitude by running custom code on every event.

Documentation for Browser SDK 2.

Identify

mParticle

typescript
var identityRequest = {
userIdentities: { email: 'updated-email@example.com' }
}
mParticle.Identity.modify(identityRequest, identityCallback);

Amplitude

typescript
setUserId('12091906-01011992');
identify(
  Identify()
    .set('email', 'updated-email@example.com')
);

Track

mParticle

typescript
mParticle.logEvent('Article Completed',
    mParticle.EventType.EVENT-TYPE,
    {
        'title':'How to Create a Tracking Plan',
        'course':'Intro to Analytics'}
);

Amplitude

typescript
track('Article Completed', {
  title: 'How to Create a Tracking Plan',
  course: 'Intro to Analytics',
});

Group

Amplitude

Assign user to a group:

typescript
amplitude.setGroup('Working Group', 'UNIVAC')

Update properties of a group:

typescript
groupIdentify(
  'Working Group',
  'UNIVAC' ,
  new Identify()
    .set('principles', ['Eckert', 'Mauchly']);
    .set('site', 'Eckert–Mauchly Computer Corporation');
    .set('statedGoals', 'Develop the first commercial computer');
    .set('industry', 'Technology')
);

For all other SDKs, refer to the relevant SDK documentation.

Validate events

Data validation is a critical step in the instrumentation process. Validate your event data using Amplitude's debugging tools.

Add a destination

To add a new destination:

  1. From Data, click Destinations in the Connections section.
  2. Click Add Destination.
  3. Browse or search for the destination you want to add.
  4. Follow the on-screen prompts.

For detailed instructions, refer to the documentation for the destination you want to add.

Migration checklist

Validate the migration to minimize impact on downstream data consumers.

  • [x] Added all sources to Amplitude
  • [x] Migrated existing tracking code to Amplitude SDKs
  • [x] Validated events are flowing in to Amplitude correctly
  • [x] Added all destinations to Amplitude
  • [x] Validated data is flowing into destinations correctly
  • [x] Validated downstream consumers aren't affected (for example, BI, Mktg, ML, Ops)

Frequently asked questions

Was this helpful?