Migrating to Simplified ID Merge API: Insights & Advice Needed

Yaron L. · 2025-05-26T11:42:27.136Z

Hi everyone :wave: We're considering migrating one of our existing Mixpanel projects (currently using the *Original ID Merge API*) to the *Simplified ID Merge API*. I’ve reviewed the docs, but I’d love to hear from others who have actually gone through this: • What are the *implications for existing user data and event histories*? Do user profiles or past merges remain intact after switching? • Are there any *gotchas or caveats* we should be aware of around how identities are handled post-migration? • How *disruptive is the transition* from a development standpoint (e.g., SDK changes, alias → identify logic updates)? • Is it recommended to do this in a production project, or should we consider spinning up a new one under the new identity model? Any lessons learned or advice from your own migration experience would be greatly appreciated :pray:

Yaron L.

·May 26, 2025 11:42 AM·

Hi everyone 👋 We're considering migrating one of our existing Mixpanel projects (currently using the Original ID Merge API) to the Simplified ID Merge API. I’ve reviewed the docs, but I’d love to hear from others who have actually gone through this:

What are the implications for existing user data and event histories? Do user profiles or past merges remain intact after switching?
Are there any gotchas or caveats we should be aware of around how identities are handled post-migration?
How disruptive is the transition from a development standpoint (e.g., SDK changes, alias → identify logic updates)?
Is it recommended to do this in a production project, or should we consider spinning up a new one under the new identity model?

Any lessons learned or advice from your own migration experience would be greatly appreciated 🙏