Asynchronous Migration Using Siebel Migration

You can use Siebel Migration to plan and carry out an asynchronous migration. An asynchronous migration essentially involves creating an asynchronous migration plan for the source environment and another (separate) asynchronous migration plan for the target environment. Migration activities that must be completed on the source environment can then be carried out independently of the migration activities that must be completed on the target environment. For asynchronous migration to work, both source and target environments must be in a Repository Upgraded state, otherwise migration execution will be performed in synchronous mode.

According to the source and target environment state, the following table outlines the supported migration scenarios. These migration scenarios are supported, using either the Siebel Migration Application or REST API, in Siebel CRM 18.11 Update and later releases.

Source and Target State	Export Only Migration	Import Only Migration	Export and Import Migration
Source is Repository Upgraded, Target is not.	Supported	Not Supported	Supported
Both Source and Target are Repository Upgraded.	Supported	Supported	Supported
Source is not Repository Upgraded, Target is Upgraded	Not Supported	Not Applicable	Supported

Note: A Repository Upgraded state means that the environment (repository and schema) has been upgraded to Siebel 18.8 Update or later release of Siebel CRM.

Caution: It is recommended that you back up your target database before starting to migrate repository or data using Siebel Migration.

The steps to perform an asynchronous migration using Siebel Migration are outlined in the following procedure and involve the following:

Generating a watermark if required.
Creating and executing an export only migration plan to export resources from the source environment.
Creating and executing an import only migration plan to import (exported) resources to the target environment.

To perform an asynchronous migration using Siebel Migration

Generate a watermark if required. To export an Incremental Runtime Repository, you must get the Watermark file from the target environment where you are planning to import the exported data.

Note: You must ensure that the watermark you use is the latest watermark. If you export the repository using an old watermark, then the import will fail with an error message similar to the following: Watermark does not match the exported resources watermark.
1. Navigate to the Connections tab in Siebel Migration.
2. Click Watermark (the waves icon) next to the target connection (that is, the target environment where you want to import the exported data).
3. In the dialog that appears, enter the Watermark file name and click OK.
  
  If the Migration Package Location is configured in the Migration Profile in Siebel Management Console, then the Watermark file is generated in the Migration Package Location path. Otherwise the Watermark file is generated in the <File System>\migration folder on the selected connection.
Create an export only migration plan on the source environment.
1. Navigate to the Migration Plan tab in Siebel Migration.
2. Click New Migration and then enter the Name of the migration plan and a Description.
3. Select and move the connection, where you want to export data from, to the Source field.
4. Select the resources that you want to export.
5. Save the source migration plan.
Create an import only migration plan on the target environment.
1. Navigate to the Migration Plan tab in Siebel Migration.
2. Click New Migration and then enter the Name of the migration plan and a Description.
3. Select and move the connection, where you want to import data to, to the Destination field.
4. Select the resources you want to import.
5. Save the target migration plan.
Execute the export only migration plan on the source environment.
1. Navigate to the Execute tab in Siebel Migration.
2. Go to and select the migration plan that you created in Step 2 and want to export, and then click Run (the play icon) in the Action column.
3. Complete the fields in the Execution Details Window that appears as required, and then click OK. For information on how to complete the fields in the Execution Details Window, see Executing a Siebel Migration Plan.
  
  Siebel Migration starts to export all the resource data simultaneously. After all data has been exported, it is then packaged into a package file. If the Migration Package Location is configured in the Migration Profile in Siebel Management Console, then the package file will be created in the Migration Package Location path. Otherwise, the package file will be created in the <File System>\migration folder on the source machine.
  
  The package file contains a list of all the resources that were exported. It also contains the Watermark information if you have chosen the Incremental Runtime Repository or Incremental Workspace Data resource in the migration plan.
Execute the import only migration plan on the target environment:
1. Navigate to the Execute tab in Siebel Migration.
2. Go to and select the migration plan that you created in Step 3 and want to import, and then click Run (the play icon) in the Action column.
3. Complete the fields in the Execution Details Window that appears as required, and then click OK. For information about how to complete the fields in the Execution Details Window, see Executing a Siebel Migration Plan.
Before executing the import only migration plan, you must ensure and do the following:
- Ensure that the package file (created in Step 4) is accessible to the target connection where you want to import the exported data. If the Migration Package Location is configured in the Migration Profile in Siebel Management Console, then the package file must be in the Migration Package Location path.
- If the Migration Package Location is not configured, then you must copy the package file (created in Step 4) from the source to the target environment’s <File System>\migration folder.
Note: Before the import starts, Siebel Migration ensures that the resources selected in the import only migration plan match the resources selected in the export only migration plan. If the resources do not match, then an error message appears and the import will not start. Similarly, if the Incremental Runtime Repository or Incremental Workspace Data is part of the migration plan, then the watermark used during the export must match the watermark in the target environment. Otherwise , an error message appears and the import will not start.

Note: The File System path must be accessible by all Siebel Servers and application interface machines.