You need to change the destination that Fivetran syncs your data to. This could be because you are switching providers (for example, from Snowflake to BigQuery) or because you are changing the region that your destination is in. Changing destinations requires a complete data migration from one destination to another.
We recommend a phased approach that allows you to migrate your data without any downtime to reporting or analytics that are powered by Fivetran data. You cannot move a connector from one destination to another without doing a historical re-sync.
To migrate to a new destination, do the following:
NOTE: If you need to migrate more than 20 connectors to a new destination, our Support team may be able to help you do that on the backend.
Create a new Fivetran destination. For help, see our destination setup instructions.
Re-create all active connectors in the new destination. You can use Fivetran’s REST API to clone your existing connectors.
NOTE: If you need to copy many connectors to a new destination or if you are unfamiliar with using our API, contact our Support team for help.
Initiate historical syncs for the new connectors.
TIP: Prioritize database connectors and other application connectors that sync large amounts of data, because their historical syncs take longer to complete.
Validate data in the new destination.
- Compare counts by date between the old and the new destination.
- Check the relevant Release Notes to ensure that no connectors have had version upgrades since you created the original connectors in the old destination.
Update your production reporting and analytics to use data from the new destination.
Disable the connectors in the old destination.