Get Started
Data
Analytics
Session Replay
Feature Experiment Web Experiment
Admin
SDKs APIs
Partners
FAQ
What is Amplitude? Create a new account Create a project in Amplitude Plan your implementation Instrumentation pre-work
Use Autocapture to get fast insights What events will you need? Track progress as you instrument Amplitude Questions your engineer might ask you Cross-platform instrumentation vs. separate platform instrumentation
The Amplitude Home page Create a chart Spaces: Keep your work organized Start from a template
Understand your users' activity Analyze your acquisition channels Analyze the adoption of a feature Understand the conversion rate of an important flow How Amplitude identifies your users
Helpful definitions User property definitions Event property definitions Browser compatibility for Amplitude's product website How to organize your team for implementation Optimize your Amplitude workflow to improve user engagement Analyze A/B test results in Amplitude Cookies and consent management
Migrate From Adobe Migrate From Mixpanel Migrate From mParticle Migrate From Segment Migrate from Google Analytics

Migrate From Mixpanel

The Amplitude Professional Services team has compiled this Mixpanel to Amplitude Implementation Guide to help you implement Amplitude and start getting insights right out of the gate.

With the goal of driving tangible conversion, retention, and product outcomes, this guide provides you with recommended use cases and business questions, a proposed taxonomy, and example charts that can be used for your implementation.

Customer case study

Learn about how Whisk migrated from Mixpanel to Amplitude on the Amplitude Blog.

Implementation process

The steps below provide a roadmap to the process of migrating to Amplitude.

Set product metrics

  • Before you dive into the data, ensure all stakeholders and team members agree on what you want to get out of the data. What use cases would the team like to focus on?
  • See list of suggested Mixpanel to Amplitude use cases and business questions/metrics down below.

Design a data taxonomy

  • Your data taxonomy should have events and properties that can answer your core metrics.
  • See the Data Taxonomy Playbook and the sample taxonomy below for best practices.

Instrument your taxonomy

You can send data to Amplitude client-side, server-side, or through a third party.

Suggested use cases and business questions

Amplitude provides a workbook with the most common use cases from other Amplitude customers who've migrated from Mixpanel. For more information, see the Mixpanel to Amplitude Migration Workbook

Common use cases by industry

Goal: Understand product engagement.

Key points:

  • See how your users convert through critical funnels: acquisition (free trial, sales, partner, POC), onboarding, activation, workflow, cross-sell/upsell funnels.
  • Target the right customers at the right time to move them through a critical funnel.
  • Find patterns in the way your customers move through key milestones (acquisition, onboarding, activation, renewal).
  • Understand different customer segments’ use and adoption to define key personas based on use cases and needs.
  • Optimize your product experience to target different customers personas needs and make them more successful.
Goal: Understand what makes your users purchase.

Key questions:

  • What's the efficiency of marketing channels?
  • How many users complete sign-up and money transfer in one session?
  • How do users engage with product features?
  • What impacts user retention?
  • What's the % of users that have used accounts with > 2 currencies in the last 30 days?
  • How much revenue do we get from a customer?
  • What impacts referrals?
Goal: Understand revenue and conversion drivers.

Key questions:

  • How often do users look at products?
  • What's our purchase conversion rate?
  • And what's the falloff in each step? (rates of- click to category page, click to product, add to cart, view cart, start checkout, order conversion)
  • What features do users interact with that lead to conversions?
  • What are the drivers that lead from user registration to first purchase?
  • How many purchases include more than one item?
  • Does the ATC (add to cart) decreased by user or device type?
Goal: Understand the acquisition and subscription drivers of your users' engagement with your product.

Key questions:

  • What's the total length of time from content consumption in the Free Trial for churned trials vs. subscription converters?
  • What activities are common between users who convert vs don't convert after the Free Trial expires?
  • How do users interact with our site and how do they consume content?
  • What is the percentage of content consumed per genre?
  • What brings users back?

Suggested Mixpanel to Amplitude taxonomy

Amplitude provides a suggested Mixpanel to Amplitude Taxonomyfor tracking a minimum set of Events, Event Properties, User Properties.

Send live event data from your website to Amplitude and/or migrate your existing historical data from Mixpanel to Amplitude.

Send live event data from your product to Amplitude

Amplitude's recommendation depends on the method you use to track events.

For client-side event tracking:

  • Amplitude’s SDK Catalog. Use your existing instrumentation method and reference Amplitude mapping to replace instrumentation.

For server-side event tracking:

Map existing Mixpanel methods to Amplitude

Amplitude offers several methods that map to Mixpanel methods.

Event tracking

  • Mixpanel track events with the 'mixpanel.track()' method, which takes an event name and sets of properties.
  • Amplitude tracks events with the 'amplitude.getinstance().logEvent()' method. This also takes an event name and set of properties as a JSON object.

Property tracking

Super properties in Mixpanel are properties that attach to all subsequent events. Amplitude's User Properties function similarly in that once set, these properties attach to all subsequent events that Amplitude ingests.

  • In Mixpanel, super properties are set with the 'mixpanel.register()' method.
  • In Amplitude, update user properties with the 'amplitude.identify()' method.

User identification

  • Mixpanel uses a combination of distinct_id (a randomly generated identifier on a specific platform) and user_id (explicitly set by the instrumenting teams) to identify a user with the 'mixpanel.identify()' method.
  • Amplitude uses a combination of device_id (a randomly generated id on a specific platform) and user_id (explicitly set by the instrumenting teams) to identify a user with the 'amplitude.identify()' method.

For more on how Amplitude resolves user identifies, see Track unique users

Migrate existing historical data from Mixpanel to Amplitude

Amplitude offers a few options to migrate your historical data from Mixpanel to Amplitude:

  • Amplitude Batch Event Upload API
    • Export your data directly out of Mixpanel via API and upload into Amplitude with the Batch API.
    • If you host your data in a another external source, you can also use the batch endpoint to upload data into Amplitude.
  • Professional Services
    • For custom services lead by the Amplitude Professional Services team, contact your Amplitude account manager.

Data privacy considerations

Along with the ingestion methods above, here are some features or areas to consider when managing your customer data:

The Mixpanel import tool

Amplitude provides a tool that can import historical Mixpanel events into your Amplitude project. When you add your Mixpanel project's API key or service account credentials, this tool uses Mixpanel's Export API to export event data from Mixpanel, and import it to your Amplitude project. The integration doesn't support user profile information.

If you need to import user profile information, Amplitude provides the following options:

Troubleshooting

The import tool responds with an authentication error

Make sure you provide the correct authentication to the Mixpanel import tool.

If you use your Mixpanel project's API key, be sure to reference the correct project. Each project in Mixpanel has its own API key.

If you use a Mixpanel service account, ensure you enter the credentials as follows:

Service account value Amplitude field
Username The username field in the import tool
Password The API Key field
Project ID The Project ID field

If you don't have the username and password for your Mixpanel project's service account, create a new service account associated with your project, and copy the values.

Ensure your Mixpanel service account has the necessary permissions to access the information you need. Test your credentials with Mixpanel's Download Data page. If the page responds with a 200 status, your service account has the necessary permissions.

The import tool doesn't complete or responds with a generic error

The data set may be too large to process. Try again with a more narrow time range.

The tool imports fewer transactions than it should

  • Amplitude detects and excludes duplicate events. If your data contains a large number of duplicates, the events that Amplitude imports may be fewer than expected.

  • Some Mixpanel events may not be compatible with Amplitude events due to missing information. If your Mixpanel instrumentation doesn't capture fields like name, date, or device ID, Amplitude may not import them.

GDPR information

Amplitude is fully GDPR compliant.

For more information about compliance, see Security and Privacy.

Amplitude maintains a user privacy API that allows you to service end user data deletion requests.

Feedback or questions

For any feedback or questions on this implementation guide, submit them here.

Was this page helpful?

Thanks for your feedback!

December 21st, 2024

Need help? Contact Support

Visit Amplitude.com

Have a look at the Amplitude Blog

Learn more at Amplitude Academy

Terms of Service Privacy Notice Acceptable Use Policy Legal

© 2024 Amplitude, Inc. All rights reserved. Amplitude is a registered trademark of Amplitude, Inc.