I have created my project in EU data center want to move with US data center creating new project is okay but all mapped events can we transfer this to new project or we need to map it again from the scratch?
When you create a new project in a different data center (in your case, moving from the EU to the US), you will need to migrate your existing data and configurations. This includes your mapped events. For migrating your data, you can find where your data is stored under Project Settings > Data Residency for existing projects. If the wrong Data Residency location was chosen before implementation, you will need to create a new project with the applicable data storage option and migrate all your existing data. Mixpanel cannot assist with migrating an existing project with the wrong residency location. You can find out more about creating a new project here [^1^].For migrating your mapped events and other configurations, you would need to manually recreate cohorts, custom events, and custom properties in the new project. Mixpanel provides a Move Board feature that allows you to directly transfer Boards between projects preserving reports, filters, and text annotations. However, any saved cohorts, custom events, custom properties, lookup tables would need to be created first as they don’t get automatically moved as part of the Move Board [^3^][^4^].For backfilling historical data, you can use Mixpanel APIs, Mixpanel Warehouse Connector, or Customer Data Platform (CDP) depending on where your data resides [^5^][^6^].Please note that the data residency of a project can’t be changed once the project is created [^7^].[^1^]: (https://docs.mixpanel.com/docs/privacy/eu-residency#storing-your-data-in-the-european-union) [^3^]: (https://docs.mixpanel.com/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system#migrating-reports-and-non-data-entities) [^4^]: (https://docs.mixpanel.com/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system#migrating-reports-and-non-data-entities) [^5^]: (https://docs.mixpanel.com/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system#backfilling-historical-data) [^6^]: (https://docs.mixpanel.com/docs/migration#loading-historical-data) [^7^]: (https://docs.mixpanel.com/docs/orgs-and-projects/managing-projects)
kapa.ai is still learning and improving, please let me know how I did by reacting below.
⤵️ Hint: Mention @kapa.ai in the thread for follow-ups.
It's a fresh implementation it's that all my events are mapped in EU env but now plan has changed to move to US env do my dev need to create all customs events from the scratch by mapping individual events or there is any options while moving projects we can transfer the set of events directly without any hassle
Sorry Abhishek s., I'm not sure what you mean. Please try again. 👋
Sorry Abhishek s., I'm not sure what you mean. Please try again. 👋
kapa.ai It's a fresh implementation it's that all my events are mapped in EU env but now plan has changed to move to US env do my dev need to create all customs events from the scratch by mapping individual events or there is any options while moving projects we can transfer the set of events directly without any hassle
Let me check the knowledge base for you again. One moment! 📚
When you create a new project in a different data center (in this case, moving from the EU to the US), you will need to migrate your existing configurations, including your custom events. For migrating your custom events, you would need to manually recreate them in the new project. This involves manually copying and pasting / replicating the logic from the existing project into the new project’s custom events definitions. For example, for custom properties, follow steps to Creating a Custom Property and copy over the definition from the old project [^1^].Mixpanel provides a Move Board feature that allows you to directly transfer Boards between projects preserving reports, filters, and text annotations. However, any saved cohorts, custom events, custom properties, lookup tables would need to be created first as they don’t get automatically moved as part of the Move Board [^1^][^2^].Please note that the data residency of a project can’t be changed once the project is created [^3^].[^1^]: (https://docs.mixpanel.com/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system#migrating-reports-and-non-data-entities) [^2^]: (https://docs.mixpanel.com/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system#migrating-reports-and-non-data-entities) [^3^]: (https://docs.mixpanel.com/docs/orgs-and-projects/managing-projects)
kapa.ai is still learning and improving, please let me know how I did by reacting below.
⤵️ Hint: Mention @kapa.ai in the thread for follow-ups.
