Performing migrations
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.
Migrator is fully Unicode capable and allows migration of objects and data between non-Unicode and Unicode servers. Additionally, you do not have to run Migrator on the same locale as a non-Unicode server.
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 Migrator, 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, Migrator 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? Migrator does not change objects on a destination server if Enforced mode is enabled in AR System and the object is checked out by another user. For more information about the use of source control in AR System, 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.
The following topics describe how to migrate objects, fields, and data, procedures on how to run and clear migrations, and how to perform Copy-Prefix migrations:
Action | Reference |
|---|---|
Use the migration status pane to view information about active, completed, and scripted migrations, and manage them. | |
Use the Migrator to migrate objects between servers, between a server and a file, or between files. | |
Migrate applications between files by using the following two methods:
| |
Migrate only a specific form view and its related fields and display properties to migrate, instead of migrating all the fields and form views. | |
Learn how to migrate fields from one AR System form to another by using Migrator. | |
Migrate data entries associated with a form from one server to another, between a server and a file, or between files by using Migrator. | |
Learn about Copy-Prefix migration and how to migrate objects on the same server by using Copy-Prefix migration. | |
Learn how to migrate only those objects that differ between the source and the destination, or that are missing on the destination, are migrated. | |
Learn how to migrate dependent objects from a Dependency report. | |
Learn how to migrate customizations with overlays and custom objects and generate multiple reports to compare the differences between these customizations on the source and destination servers. | |
Learn how to leverage the command-line interface (CLI) to perform migrations. | |
Learn how to create specific search criteria for your data records for a customized migration by using Migrator. | |
Use Migrator to delete objects and run a check to determine the impact of the deletion before deleting them. |