Performing migrations

This section describes how to migrate objects, fields, and data. It also includes procedures on how to run and clear migrations, and how to perform Copy/Prefix migrations. Topics include:

Some tips to remember are:

•  is fully Unicode capable and allows migration of objects and data between non-Unicode and Unicode servers. Additionally, you do not have to run  on the same locale as a non-Unicode server.
• You can migrate definition (.def ) files with multiple character encoding as long as each block within the .def file contains the character encoding used at the beginning of the block. If that line is missing, the migration must be executed on a server of the same locale that was used to create the .def file.

Before you begin

Before you begin a migration, verify the following information:

• Are you licensed and logged on to all of the servers you want to migrate to and from? See Licensing-and-starting-Migrator for more information.
• Do you want to restrict users from accessing a destination server that is involved in a migration? (In , Administrator mode is on by default.) If yes:
  • Select the production server window and select the Migrate menu.
  • Select Set Admin Mode on Destination Server to turn it on (check) and select it again to turn it off (uncheck). If Set Admin Mode on the destination server is selected,  enables the Administrator-Only mode on the destination server (if your server supports it) during a migration, and turns it off when the migration is complete.
• Did you set up your migration and report options in the Tools menu? See Setting-Migrator-options for setting up migration options and Chapters 8 through 10 for setting up report options.
• If Enforced mode is enabled on the destination server, are all the objects on the destination server checked into Source Control?  does not change objects on a destination server if Enforced mode is enabled in  and the object is checked out by another user. For more information about the use of source control in , see Setting-version-control-options.
• Do you want to review object dependencies or view object differences before you start migrating? See Migrator-overview
• Have you verified or added any prefixes for workflow items that should be ignored during the migration process? See Setting-Migrator-options.