Control-M/Server Manual Migration

The following procedures describe how to perform a manual migration by exporting the old data from the old Control-M/Server, copying the file and importing it into the new Control-M/Server:

Task	Description
Control-M/EM Migration	Before you begin Control-M/Server migration, the Control-M/EM must be migrated to the new environment.
Editing the Control-M/Server migration parameters	Configure the Control-M/Server migration parameters, including whether to prompt for the number of log days to include in the export.
Exporting the Control-M/Server old data	Exports the data from the old environment to a file.
Importing the Control-M/Server exported data to the new environment	Imports the data into the new environment.
Post-Control-M/Server migration procedures	The following procedures describe the post-Control-M/Server migration process: Renaming the Control-M/Server in Control Configuration Manager (CCM): Enables you to rename the Control-M/Server that was migrated. Connecting the gateway to the new Control-M/Server: Describes how to repoint the gateway to the new Control-M/Server, if Control-M/EM was not migrated at the same time as Control-M/Server, and you want to reuse the Control-M/Server component in the CCM. Continuing after Control-M/Server migration: Describes how to continue working with existing agents after you have finished the Control-M/Server migration.

Parent Topic

Control-M/Server Migration