The short answer
- PostHog's official migration guide moves 3 partly; 2 things stay behind. What moves
- 2 public accounts of making this switch: 1 switched, 1 evaluated. Read them
- Switching help: PostHog publishes a free, self-serve migration guide for Amplitude users: a documented Python script that reads Amplitude's gzipped JSON exports (Export API or S3) and replays them into PostHog with historical_migration=True, with event and property mappings. No sales contact needed. posthog.com
Moving from Amplitude to PostHog
What PostHog's importer carries over, what it leaves behind, and any help it offers switchers.
To PostHog
Official guide posthog.com · Tools: PostHog Python SDK, Amplitude Export API / S3 export (.json.gz files)
Moves: Raw events with properties (partial); Pageviews and autocapture events (partial); Initial attribution (referrer, UTM) user properties (partial). posthog.com
Doesn't move: Amplitude dashboards, cohorts and saved analyses; Amplitude session replay and Experiment data. posthog.com
Watch out for:
- The PostHog sample script contains 'if count >= 6: break' - a demo cap that must be removed for a real migration posthog.com
- Events are replayed with the client initialized with historical_migration=True, as in PostHog's sample posthog.com
- User identity merges (Amplitude amplitude_id) are not carried over; distinct_id is built from user_id or device_id posthog.com
Switching help: PostHog publishes a free, self-serve migration guide for Amplitude users: a documented Python script that reads Amplitude's gzipped JSON exports (Export API or S3) and replays them into PostHog with historical_migration=True, with event and property mappings. No sales contact needed. posthog.com
From each destination's own migration docs and switching pages, plus community write-ups where no official guide exists, each checked against its page. Confirm terms on the linked page before you rely on an offer.
People who moved from Amplitude to PostHog
2 public accounts of leaving Amplitude: 1 evaluated, 1 switched. Summaries are ours; each links the original, and each was checked against its page before it appeared here.
A consultant recounts a client that ran PostHog and Amplitude in parallel for over a year. PostHog was ~30% cheaper and preferred by engineers; Amplitude won on taxonomy governance and non-technical self-serve. After evaluating consolidation they deliberately kept both, with clear ownership per team. Cotera
Zealot's CTO installed Amplitude (the enterprise default) and PostHog (a personal recommendation) side-by-side. PostHog won on data completeness, support quality and bundled error tracking; the team removed Amplitude (and BugSnag) from their codebase entirely. PostHog
FAQ
Can I move my Amplitude data to PostHog?
PostHog's official guide moves: Raw events with properties; Pageviews and autocapture events; Initial attribution (referrer, UTM) user properties. It doesn't move: Amplitude dashboards, cohorts and saved analyses; Amplitude session replay and Experiment data. posthog.com
Does PostHog help people switch from Amplitude?
PostHog publishes a free, self-serve migration guide for Amplitude users: a documented Python script that reads Amplitude's gzipped JSON exports (Export API or S3) and replays them into PostHog with historical_migration=True, with event and property mappings. No sales contact needed. posthog.com
Keep reading
Check your own stack
Get your free stack audit
Stackcut finds every software subscription in your inbox and shows what to cancel, what to pay per use, and what AI can replace, with a spec and a cost for each. Your stack audit is free and takes about 2 minutes.
Or ask your agent
Connect the Stackcut MCP server (https://stackcut.io/mcp, no API key) and ask: “We pay for Amplitude. Should we move to PostHog?”
find_alternatives({"vendor": "Amplitude"})