Documentation Index
Fetch the complete documentation index at: https://mintlify.com/mixpanel/docs/llms.txt
Use this file to discover all available pages before exploring further.
Migration Guides
Comprehensive guides to help you migrate from other analytics platforms to Mixpanel.Why Migrate to Mixpanel?
Mixpanel’s event-based analytics model provides:- Flexible data model - Schema-on-read approach lets you track what matters without upfront configuration
- Powerful analysis - Deep insights into user behavior with funnels, retention, flows, and more
- User-centric analytics - Track individual user journeys, not just aggregated sessions
- Real-time data - See user behavior as it happens
- Easy to implement - Simple SDKs and APIs for quick integration
Migration Overview
Migrating to Mixpanel typically involves three key steps:1. Data Audit
Before migrating, identify:- Key events and properties you currently track
- Most important reports and metrics
- User identification and identity management approach
- Data volume and historical data requirements
2. Implementation
Choose your tracking method:- Client-side SDKs - JavaScript, iOS, Android, React Native
- Server-side SDKs - Node.js, Python, Ruby, Java, PHP, Go
- CDPs - Segment, mParticle, Rudderstack
- Warehouse Connectors - Snowflake, BigQuery, Redshift, Databricks
- Import API - Direct API integration
3. Validation
Verify your implementation:- Test events are arriving with correct properties
- User identification is working properly
- Reports show expected results
- Historical data (if imported) matches expectations
Platform-Specific Migration Guides
Google Analytics to Mixpanel
Migrate from Google Analytics 4 or Universal Analytics to Mixpanel’s event-based analytics. Key Differences:- Mixpanel uses events and properties instead of sessions
- More granular user-level tracking
- Better identity management across devices
- More flexible analysis capabilities
- Use BigQuery export and Warehouse Connectors for historical data
- Implement Mixpanel SDK for forward-looking tracking
- Use Google Tag Manager for quick implementation
- Fresh implementation recommended (event model vs session model)
- Use Mixpanel JavaScript SDK with auto-tracking
- Leverage Marketing KPI templates
- Event data from BigQuery (GA4 only)
- User properties
- Custom dimensions and metrics (mapped to event properties)
Amplitude to Mixpanel
Migrate from Amplitude to Mixpanel with minimal code changes. Key Similarities:- Both use event-based data models
- Similar SDK APIs for easy code migration
- Compatible identity management approaches
- User profiles for dimensional data
- Group analytics for B2B use cases
- Lookup tables for data enrichment
- More intuitive UI and report building
-
Free Migration Service (under 15M events)
- Automated migration via API
- Exports Amplitude data, transforms, and loads into Mixpanel
- Includes events and user profiles
-
Warehouse Connectors (larger datasets)
- Export Amplitude data to your warehouse
- Use provided SQL transformations
- Set up recurring sync with Mixpanel
-
SDK Migration
- Very similar SDK methods (minimal code changes)
- Find and replace Amplitude calls with Mixpanel equivalents
Adobe Analytics to Mixpanel
Migrate from Adobe Analytics’ schema-based model to Mixpanel’s flexible event-based approach. Key Differences:| Adobe Analytics | Mixpanel |
|---|---|
| Schema-on-write (pre-defined metrics) | Schema-on-read (flexible properties) |
| “Hits” with eVars | Events with properties |
| Complex visitor ID concatenation | Simple distinct_id management |
| Requires upfront admin configuration | Send data and query immediately |
- Data Model: Fundamental differences mean fresh implementation recommended
- Historical Data: Import to separate project if needed (expect 5% discrepancy)
- Identity Management: Adobe’s visitor ID logic vs Mixpanel’s simplified approach
- Metrics: Adobe’s calculated metrics vs Mixpanel’s on-the-fly analysis
-
Fresh Implementation
- Use Mixpanel JavaScript SDK with auto page tracking
- Track key “value moment” events
- Use Marketing KPI templates
-
CDP Migration
- Add Mixpanel as destination in Segment/mParticle/Rudderstack
- Reuse existing CDP tracking
-
Warehouse Migration
- Transform Adobe data in warehouse to event format
- Import via Warehouse Connectors or API
- Set up projects with Simplified ID Merge before sending data
- Test with limited data in dev project first
- Expect higher discrepancy range due to model differences
Historical Data Migration
Should You Import Historical Data?
Consider these factors: Pros:- Year-over-year trend analysis
- Maintain historical context
- Complete user journey history
- Time and resource intensive
- Potential data discrepancies due to model differences
- Impact on billing (historical events count toward quota)
- Identity management complexity
- Import 1 year or less of historical data
- Use separate project for historical data if models differ significantly
- Focus on most important events, not all data
- Validate data thoroughly before production use
Historical Data Import Methods
- Warehouse Connectors - For data already in Snowflake, BigQuery, Redshift, or Databricks
- Import API - Programmatic import for custom data sources
- CDP Replay - Use Segment Replay or similar features
- Migration Services - Mixpanel’s free migration service (Amplitude, under 15M events)
Implementation Methods
Client-Side SDKs
Best for:- Web applications
- Mobile apps
- User interaction tracking
Server-Side SDKs
Best for:- Business-critical events (purchases, signups)
- Backend process tracking
- Avoiding ad-blockers
Customer Data Platforms
Supported CDPs: Benefits:- Single SDK for multiple destinations
- Easy to add Mixpanel to existing setup
- Built-in data transformation and filtering
Warehouse Connectors
Supported warehouses:- Snowflake
- Google BigQuery
- Amazon Redshift
- Databricks
- Native integration with your data warehouse
- Automated recurring syncs
- No-code setup
- Mirror mode for data updates
Migration Checklist
Planning Phase
- Audit current tracking implementation
- Identify key events and properties
- Document user identification approach
- Determine historical data requirements
- Choose implementation method
- Create tracking plan for Mixpanel
Implementation Phase
- Set up dev and production Mixpanel projects
- Choose identity management API (Simplified recommended)
- Implement tracking in dev environment
- Enable debug mode for testing
- Verify events appear in Mixpanel
- Validate event properties and user identification
- Import historical data (if needed)
Validation Phase
- Test key user flows
- Verify identity management works correctly
- Build essential reports
- Compare results with previous analytics tool
- Train team on Mixpanel
- Deploy to production
- Monitor for issues
Post-Migration
- Set up data governance (Lexicon)
- Create board templates
- Configure alerts
- Document implementation for team
- Schedule regular data quality checks
Getting Help
Mixpanel Customer Success and Support have helped thousands of customers migrate from other analytics platforms. Enterprise Migration Packages: Support Resources:- Contact Support - Technical questions and implementation help
- Slack Community - Connect with other users
- Professional Services - Dedicated migration assistance
- Enterprise customers: Contact your Customer Success Manager
- All customers: success@mixpanel.com or get support
Related Resources
- Quickstart Guide - Get started with Mixpanel
- Tracking Best Practices - Implement tracking correctly
- Identity Management - Choose the right ID approach
- Data Governance - Maintain data quality
- Implementation Guides - Step-by-step tutorials