We are redesigning our data platform on snowflake and we would like to place tables we sync to mixpanel in mirror mode to a different schema. Is there a way how to move to new database and schema and rebuild stream synces in a way that data on mixpanel is not purged and continue with data synces once tables are moved to new destination?
I’m sorry, but the knowledge sources do not explicitly describe a supported way to “re‑point” an existing Mirror sync from one Snowflake database/schema to another while keeping all existing data in Mixpanel and simply continuing incremental syncs. From what is documented:
Mirror relies on Snowflake Streams that Mixpanel creates and manages in a dedicated schema you grant it, and those Streams are tied to specific underlying tables/views. [Mirror – Snowflake]
There is no mention of a mechanism to change the source table/database/schema of an existing Mirror sync without recreating it.
The Mirror guide explicitly warns that schema changes and large‑scale changes can effectively cause a full resend of data and recommends planning them carefully and consulting your Account Manager for large changes that might impact billing. [Sync with Mirror; When to use Mirror]
Because there is no documented procedure for:
moving Mirror‑tracked tables to a new Snowflake database/schema, and
“rebuilding” the Streams and connector configuration to point at the new location
while preserving existing Mixpanel data and continuing CDC from the new tables
I cannot confidently say this is supported or how to do it without data being purged or re‑ingested. Given the lack of explicit guidance, the safest next steps are:
Contact Mixpanel Support / your Account Manager to confirm whether engineering can assist with a migration of Mirror syncs between Snowflake schemas without deleting or duplicating data, and to understand any billing implications. [Sync with Mirror]
Test in a staging Mixpanel project first (with a copy of your Snowflake tables in the new schema) to see how a new Mirror sync behaves relative to existing data. The Mirror guide recommends staging projects for exactly this kind of change. [Sync with Mirror]
If you’d like, you can share how your current Mirror syncs are configured (event vs profile tables, volumes, etc.), and I can help you frame specific questions to ask Support, but I can’t provide an undocumented migration procedure.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
