How to Migrate to a New Destination

If you're switching data platforms (for example, from Snowflake to BigQuery) or moving to a different region, you may need to change the destination where Fivetran syncs your data. This migration may require transferring all data from the the current destination to the new one.

Learn about our recommended phased approach that helps you avoid downtime for reporting or analytics that depend on Fivetran data.

Recommended approach for migrating to a new destination

You cannot move a connection from one destination to another without doing a historical re-sync. To migrate to a new destination, do the following:

1. Create a new Fivetran destination. For help, see our destination setup instructions.

2. Re-create all active connections in the new destination. You can use Fivetran's REST API to re-create existing connections or manually re-create them in Fivetran.

3. Initiate historical syncs for the new connections.

   TIP: Prioritize database connections and other application connections that sync large amounts of data, because their historical syncs take longer to complete.

4. 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 connections have had version upgrades since you created the original connections in the old destination.

5. Update your production reporting and analytics to use data from the new destination.

6. Disable the connections in the old destination.

Custom Requirements

If you can't follow the recommended approach because you need to migrate connection state or automate connection creation, our Solution Architecture team may be able to help. However, this service may involve additional costs. To learn more, contact your Fivetran representative.