About the Migration Package Location

You can optionally specify a single shared migration package location that supports both synchronous and asynchronous migrations in your source and target environments. This network file share path must be accessible to all of the connections that are registered in the Siebel Migration application. This topic is part of Configuring the Siebel Migration Application.

The Migration Package Location setting functions as follows:

  • Synchronous migration. The Siebel Migration application exports source environment data into a file, copies the file into the specified migration package location, and then imports data from this file into the target environment.

    If you do not use this setting, then the Siebel Migration application uses the Migration File Transfer REST service to transfer the file automatically from the Siebel File System on the source environment into the corresponding location on the target.

  • Asynchronous migration. The Siebel Migration application exports source environment data into a file and copies the file into the specified migration package location. The customer must start the import process to import data from this file into the target environment.

    If you do not use this setting, then you must copy the file manually from the Siebel File System on the source environment into the corresponding location on the target before you can import the data.

In some environments, restrictions might prevent you from using the Migration Package Location setting to specify a shared migration package location. In such cases, you might be required to use asynchronous migration and to copy the export file manually.

Because the Siebel Migration application uses the Siebel File System (migration subdirectory), it is strongly recommended to use different file system locations for the source and target environments, to avoid any file conflicts. For more information, see Creating the Siebel File System.

The Siebel service owner account and the Siebel Application Interface owner account must have read-write access to the Siebel File System and the Migration Package Location. See also Creating the Siebel Service Owner Account.