---
title: Migration Overview
description: "Overview of migration paths to Statsig from other feature flagging, experimentation, and product analytics platforms with planning checklists."
product: general
token_estimate: 667
---
# Migration Overview

> For AI agents: a documentation index is available at [/llms.txt](/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

Migrating to Statsig moves your events, feature flags, experiments, and decision workflows into one platform and a single source of truth. The process runs in four phases: audit and plan, set up live data, import historical data, then validate and decommission your legacy tool. For provider-specific steps, refer to the Amplitude, LaunchDarkly, and Mixpanel guides.

## Migration phases

### 1. Audit and plan

- Identify the datasets, events, and feature flags you want to move
- Decide what needs full historical backfill vs. what can start fresh
- Document any dashboards or KPIs that need rebuilding in Statsig

### 2. Set up live data

- Implement Statsig SDKs to start streaming new events and feature flag evaluations
- Validate critical events are firing with the correct schema
- Use Statsig for the newly recorded events and flags

### 3. Import historical data

- Export data from your existing tool (S3 or warehouse is preferred)
- Transform the schema to Statsig's event format (`event`, `user`, `timestamp`, `metadata`)
- Import using Statsig's Event Webhook, S3 ingestion, or warehouse ingestion

### 4. Validate and decommission

- Compare metrics between your legacy tool and Statsig to ensure parity
- Rebuild dashboards and charts in Statsig
- Decommission old pipelines once Statsig is your single source of truth

## Best practices

- **Start small**: Run a pilot project or test migration before backfilling all history
- **Align IDs early**: Ensure `userID` and `stableID` mapping is consistent. Identity mismatches are the most common failure point
- **Shard historical imports**: Break large datasets into daily partitions for stability
- **Rebuild insights intentionally**: Don't port all events and flags directly. Use migration as a chance to clean up stale data
- **Plan change management**: Teams need time to adjust workflows, queries, and dashboards, so migrate for 1-2 teams before championing in the broader org

## Provider-specific guides

- [Migrate from Amplitude](https://docs.statsig.com/guides/migrate-from-amplitude)
- [Migrate from Mixpanel](https://docs.statsig.com/guides/migrate-from-mixpanel)
- [Migrate from LaunchDarkly (Feature Flags)](https://docs.statsig.com/guides/migrate-from-launchdarkly)
- Additional guides coming soon

## Get help

Statsig has helped many customers migrate from other tools. For tailored guidance, reach out to the support team, your sales contact, or through the [Slack community](https://statsig.com/slack).