Migrating your own account over to v2 is almost as simple as your initial setup. Here’s what’s involved:
Sign up for a new Stitch account here.
If you want to use the same email address that you’re using for your current account, you’ll need to do the following before you sign up for a new account.
Now you’ll be able to sign up for a new Stitch account using the same email address you used when you initially signed up.
Next, you’ll set up your integrations in your new Stitch account and choose where your data will be stored in Redshift.
NetSuite only allows a single user to have one API session open at a time. This means that you can’t use the same credentials in your new and old Stitch accounts at the same time.
If you have a NetSuite integration in your old account, you’ll need to disable it OR create a new NetSuite user for Stitch before connecting it in the new account. Click here for instructions on how to do this.
Keep in mind that where data is stored in Redshift will affect how you can name your integration schemas. Refer to the chart below and proceed with one of the Supported options:
Same Redshift cluster as
|Any different destination
(including a different database
in the same Redshift cluster as
|INTEGRATIONS||SAME schema names
as old account
|DIFFERENT schema names
than old account
This part is easy - once your integrations are set up, simply allow a historical sync to complete. You’ll have two weeks to sync unlimited rows in your new account. During this time, your old Stitch account will continue to sync data.
During that two week period, ensure that:
At the end of your new account’s free trial you’ll need to select the appropriate pricing plan to continue using integrations and syncing data in your new account.
When you’re ready, cancel your old Stitch account:
This will deactivate billing and stop any data from syncing in the old account.