Scenario Migration Tool


The Migration Tool allows users to migrate Overcast integration scenarios and related data to other Salesforce organizations.

Use the Migration Tool when:


Scope of migration

Settings and records that can be migrated from one environment to another includes Integration Scenarios and related: 

Migrating Apex code, triggers, and anything else should be managed using Change Sets, ANT or SFDX, because they are metadata, not data.


Remote Site Settings Setup

Add the two domains URL to the source organization's remote site settings. Follow the steps in the section Access Remote Site Settings in the Source Organization.


Get My Domain for the Target Organization

  1. In the organization's Target organization Setup, type "my domain" in the search field.
  2. Select My Domain (highlighted).
  3. Copy the domain.  

 


Access Remote Site Settings in the Source Organization

  1. In the organization's Source organization Setup, type "remote site" in the search field.
  2. Select Remote Site Settings (highlighted).
  3. Select New Remote Site.
  4. Enter the remote site name.
  5. Paste the URL from the Remote Site.
  6. Select Save.


Navigate to Remote Site Settings.

Add a new remote site.


Tutorial

Prerequisites

Before using this tool, the following conditions are required: 

 

Step 1. Open the Migration Tool Page

  1. Navigate to the Integration Scenarios tab.
  2. Expand the list by selecting the dropdown.
  3. Select Scenario.
  4. Select Migrate Scenarios.


Step 2. Login

Enter the credentials for a system administrator (Overcast Design-Time User) in the target organization. 

  1. Enter the Salesforce username.
  2. Enter the password. (Note: There may be a requirement to append the security token to the password "password+token")
  3. Select the type of environment for the target organization.
  4. Select Login.

 

Step 3. Connection String Selection

Select the Source Connection String (1). Upon selection, the target connection string picklist is updated with the target connection strings. Only connection strings of matching type are displayed (2).

Step 4. Scenario Selection

Select the scenarios to migrate (1).

Step 5. Execute Migration

Select Execute migration (2).

Please be patient. For larger migrations or slower organizations, the migration can take a few seconds. 

A success message should be displayed upon completion.


Step 6. Generate Mapping Code for Data Synchronization Scenarios

This step generates Overcast object mapping code for the selected data synchronization scenarios. If there are modifications to the generated mapping code, create a Change Set and add the apex classes that have been modified. All custom code should be migrated using Salesforce Change Sets.

This step only needs to be performed once for each scenario. 

Your existing selection from the scenario migration should still be selected. In the target organization, wait for all of the scenarios to complete the activation operations. Then, click Migrate mapping code.

Real-time scenarios do not need to be de-selected; they will be skipped.

 

A success message should be displayed upon completion.

 

Migrating mapping code may fail if not all of the scenarios completed the activation operation successfully in the target organization.

The migration is now complete. Test the scenarios in the target organization.
 

Troubleshooting

 

Failed to log in. Are you missing your security token? [HttpError=400:Bad Request Error=invalid_grant Message=authentication failure]

 

This can be a general error message. Check the login history of the user in the target org for more details.

 

Cause

The login history log reports "Username-Password Flow Disabled". Overcast Scenario Migration supports login using the Username-Password login flow.

 

Solution

Enable the Username-Password OAuth flow on the target org. OAuth and OpenID Connect Settings -> Allow OAuth Username-Password Flows.