About Migrating with Siebel Migration

Environments: All environments

Platforms: All platforms.

Siebel Migration is a Web-based tool for end-to-end repository and data migration. Migrating repository or data using Siebel Migration is not the same as performing a database upgrade where you migrate your custom repository and schema from one release of Siebel CRM to a higher release level. Migrating repository or data using Siebel Migration is a tool that allows you to replicate the setup (including repository, Runtime Repository, application Workspace data, application data, application interface Web artifacts, and file system artifacts) that exists on one environment (known as the source) to another environment (known as the target).

Source. The source environment is the Design Time Repository (DR), also known as the development environment.
Target. The target environment is the Runtime Repository (RR), also known as the test environment (system integration testing or user acceptance testing) or production (live environment) or pre-production environment that internal and external users access.

Note: Siebel Migration does not support migration of repository or Workspace data from RR (non-development) environments to other RR environments. Migrating from Test to Production or UAT to Production is not permitted.

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

Siebel Migration uses the RESTful services to export the data on the source environment, transfer the exported data to the target environment, and then import the data to the target environment. Siebel Migration orchestrates all the resources chosen in the migration plan that is being executed.

Siebel Migration is capable of synchronous and asynchronous migration of database artifacts. For example:

Synchronous migration. You can use Siebel Migration for the synchronous migration of your repository, Runtime Repository, application Workspace data, application data, application interface Web artifacts and file system artifacts from a source environment to a target environment.
Asynchronous migration. You can also use Siebel Migration for asynchronous migration plans, where all activities that must be completed on the source environment can be done independently of all the migration activities to be completed on the target environment. This is beneficial if you have firewall restrictions or situations where source environments and target environments are managed by different teams. Creating asynchronous migration plans on the source and target environments allows customers to separate responsibilities by assigning a team to activities on the source environment and assigning another team to activities on the target environment.

Siebel Migration provides the following tools to prepare your data for migration:

Database Utilities.
Application Deployment Manager (ADM).

Using Siebel Migration, you can to do the following:

Add connections to your migration. For more information about creating connections, see Creating a Connection.
Create migration plans. For more information about creating Migration Plans, see Creating a Migration Plan. Migration plans are segregated into two separate plans:
- Source Only Environment migration plan. This migration plan exports all the required artifacts based on the resources selected as a package. If you create a Migration Plan for the Source Only environment, the plan can be used for Export only.
- Destination Only Environment migration plan. This migration plan is on the target environment that imports all the required artifacts based on the same resources selected for the export migration plan on the source environment. If you create a Migration Plan for Destination Only target environment, the Migration Plan can be used for Import only.
View the historical data of the migration execution and log history for migration tasks. For more information about viewing historical data of the migration execution, see Viewing Migration History and Log Files.
Execute Migration Plans. The migration plan execution list includes the Package Filename field. This field is populated with the package filename provided by the user. Depending on the action selected and the resources or services selected when you execute the migration plan, you will be prompted to enter additional information. For more information about executing migration plans, see Executing a Siebel Migration Plan.
- Export Only. When you execute an Export Only Migration Plan on a source, Siebel Migration exports the data for all the selected resources and creates a package ZIP file. The package ZIP file will be created in the Migration Package Location provided the location is set in the migration profile, otherwise the package ZIP file will be created in the <File System>\migration folder on the source environment.
  
  You use this package to import data to a destination environment. You must take the package ZIP file from the source environment and place it on the destination environment (in the Migration Package Location or <File System>\migration folder). Once the exported package is placed on the destination environment, you can run the migration plan as Destination Only and the Siebel Migration Application imports the package file.
  
  Note: If the Siebel Migration Application that connects to the source environment and the Siebel Migration Application that connects to the target environment are both using the same Migration Package Location, then you do not need to copy the package ZIP file in the migration folder under the file system on the destination environment.
  
  Note: The Siebel service owner account must have read-write access to Siebel File System and the Migration Package Location. For more information about creating the Siebel service owner account, see Siebel Installation Guide.
  
  When you execute an Export Only Migration Plan, Siebel Migration creates a manifest file and exports the data for the selected resources. The manifest file contains the list of resources that were exported as part of this execution and the watermark filename.
- Import Only. When you execute an Import Only Migration Plan using the package filename, Siebel Migration verifies that the resources selected in the migration plan matches the resources written in the manifest file. Siebel Migration also verifies that the watermark present in the watermark file and the manifest file matches the watermark on the connection where the user is importing. The execution proceeds only if both the resource and watermark matches.
  
  Note: Watermarks are only matched for Incremental Runtime Repository and File Prepare and Deploy resources.
Use Rest APIs. You can also use REST APIs to interact with the Siebel Migration Application. You must run the repository upgrade before you use REST APIs with the Siebel Migration Application. For more information about using REST APIs with the Siebel Migration Application, see Using REST API with Siebel Migration Application.

The following chapters deal with Siebel Migration: