Whilst it's not possible to easily switch the data centre that your Gearset account/team resides in, it is possible for you to start a brand new team in a different data centre, and transition your Gearset team over to using that one instead. Please bear in mind these considerations before attempting to do so:
YOU LOSE EVERYTHING, and need to set up the new Gearset team from scratch. This mean no history, all automation jobs and pipeline configurations need to be set up again
Should this still be something you'd like to do (i.e. to keep using Gearset for compliance purposes), please feel free to chat your Customer Success Manager to clarify any questions you might have.
This guide is written for teams that started with the EU data centre, our oldest one, and want to move to either US, AU or CA (Canada) centers. Below is a step-by-step guide on how to get set up in a new data center.
Setting up your new account with a US/AU/ CA data center
First of all, you’ll need to go to app.gearset.com. From there, you’ll have the option to select
Create your Gearset account’Only one user will need to create a new account.This link will take you to the
Welcome to Gearsetpage, from where you can choose a data storage location. Choose US/AU/CA and continue to thechoose account loginpage.We suggest you use a Prod or Dev account/GSuite as your account login (if you're the one user who needs to create a new account, do not use your old login).
Once you’ve selected your data center and account login, you can access your new Gearset account.
Reconfiguring your new account
First of all, you’ll need to invite the team members from the EU account to the US/AU/CA account through the team management section of the app.
Please leave at least ONE team member on the EU team until you’ve completed steps 3 and 4. Your CSM / Account Owner will transfer your licenses from Gearset's side and you'll then be able to assign these within the new account.
The user who created the new account can also decide to invite their old login to join.
If you’d prefer to keep using that old login, then you can then delete the newer one from the account, as it was only needed to create the new account. However, you must make sure that you’ve made at least one team member an ‘owner’ before deleting this, or else no one will be able to manage the team.
To maintain the team’s access to the EU account history, we suggest creating a generic "history" user.
The same login cannot exist on two accounts, so the use of a generic history user (that multiple team members can log into to see the history of the EU team) is much easier than one or two team members needing to create a whole new login for the US/AU/CA team.
In step 1, we asked you to leave at least ONE team member in the EU team for now. This team member will invite the new generic "history" user. Once that’s been accepted and is set up, the final team member can be invited to the new US/AU/CA instance and the transition will be completed.
We generally don't allow the use of generic licenses, but, in this instance, it will be much simpler. The generic user name can be shared with multiple team members who can log in and see the EU team’s history without needing a license.
Getting ready to work with your new account
Once all the team members are on the new team and have their licenses assigned, you can start setting everything up to get up and running with Gearset.
Get everyone on the team to reconnect their orgs using the
My connectionspart of the app.Make sure that any change monitoring or automation jobs are re-added.
Recreate any custom filters you previously had on the old EU team.