Cross Org migration through Token generation:

  • 23 September 2020
  • 1 reply
  • 74 views

Hi Admins!

Those of you actively working with SFDC Sandboxes may be familiar that Gainsight provides migration a tool to migrate assets from sandbox to production or production to sandbox. 

 

Since the migration process may need the login access/credentials, are you hesitant about sharing Production access to the one who is doing migration? There’s an alternative for this.

Are you aware also that this migration is also possible without using the conventional way of providing username and password?

Won't you be excited to know that Gainsight provides an option of token generation to authenticate source and target environments?Here is how you can do it.

 

Let’s consider a use case where you want to migrate an asset from Sandbox to production.

So first I need to get a token from the Target org. Let’s see how to get it. 

  1. In the Target org navigate to Administration -> X-org migration You will see an option to generate a token in the top right corner as seen in the image below.

_xKfkFfGotghub8xFQHwsnv-ZpLr3uCRqQ4AnxkkKP24cVPyB_15FfQ8A_w0dAQvcSVYK-AQknpd0a3O5jE7cb6hcSYXvlMsBRIEhP1RdrKI67N8WuDhLUaiMf7JzXw9lw0Gi5-j

 

  1. When we click on this, in the next screen it asks org of the source org for where you are trying to migrate the assets.

Note: Make sure you give an 18-digit org id because the migration tool cannot authorize the 15-digit org id’s.

 

04itF-tIldmwtmEUBPiMx6MrSmp8bgxo4LIa_yVb_vIUIh6kywxD6GlULqFIEl3m1MMpHsVEapWT1cHl0LM5vtWl-A-RdsVDT_JRLtLffuqWHKREYQmkidTxdAKHzYkN8XKLHTKp

  1. Copy the token to clipboard and next lets move to Sandbox from where we need to migrate the assets from this.

Note: The token once generated will be useful until the expiry date so we need not generate the token multiples and you can’t generate the token for the same sandbox until it is expired.

6KdCP1dPNpsaDzr-MsIt-BnKvUVefHUN4k6dwZ7PhvWwCG_BhbtpzOvz_2fNwPvnpN7ZCba7BJfykwTpplIpskHVse6ZQSVUnViW3IiX0yVAiBbIFAphn5yfHRn_jQWSuNQ0EyJ_


 

  1. In the Sandbox, navigate to the migration page and select ‘New migration’ when you click on ‘Add Migration’ button.

DmoDQPjhUPz2CRXXskfv0aExK9Up0vvNQUw30QfM182FoAaJMaL-RBWzuQxcQCgaaVS0TogEU6wNeXVRECX4lJd2M5XjDQ9HOMzKLaemTj0pUit5seWOR7S-Ba4SGNH1xk4rkYyi

  1. We have two options to authenticate Target org here, one through the usual method where we need user id and password and other to use the migration token. We select the migration token and paste the token which we copied to clipboard in step2 and click on authenticate.

 

hE27133RON1ZGnWYeuiJgC_I65g7YsQphGooaYSxxBvAA9sNTa-ZuXn4MinCkdQTRPoNqMZlm16ZBK0yBaQhevjUn7vvfNFwLHZAcpr-8YFIC49Cd9BEdfRXwu16s8SaOtne6BZR


 

  1. Once the authenticate is successfully you will be navigated to first page of migration process, and you can start the migration.

 

Hope this hack has helped to you authenticate the target org and perform the migration even when someone don’t have the access to target org. So, Admins you need not worry about giving the Production org access to someone in order to perform migration.


1 reply

Userlevel 7
Badge +1

@Jyothsna Thanks for sharing it here!

Reply