Migration planning process

The following table describes the main tasks in setting and implementing your Control-M Migration plan.

Tasks	Description
Plan your migration	Review the following information on Control-M Migration: AMIGO Upgrade program - Knowledge Base solution 000011573 on the Support site http://www.bmc.com/support Open an AMIGO Starter issue with BMC Support to receive the migration plan template and migration considerations. Changes in Control-M versions After reviewing all the above documentation, create a plan that includes the installation, testing, and a migration date.
Install the new environment	Review the following sources to prepare your new environment so that you can work in parallel with the old environment while you prepare your installation: To plan the computers on which to install and check compatibility requirements, see Installation. To find the Control-M installation files, see Product Distribution in the Control-M version 8.0.00 Release Notes. Install the new Control-M solution, as described in Control-M installation. Install the latest fix pack for Control-M/EM, Control-M/Server, and Control-M/Agent. For more information, see the Release Notes for the latest fix pack on the Support site (http://www.bmc.com/support). NOTE:If you are migrating Control-M/EM from version 9.0.00 or higher with installed add-on components such as BIM, Forecast, Self Service, and Workload Archiving in the source environment, you must install these add-ons on the new environment before executing the migration import procedure.
Migration	You can migrate Control-M/EM only and continue working with old Control-M/Servers and later migrate Control-M/Server or migrate both Control-M/EM and Control-M/Server at the same time. Agents can be migrated after the Control-M/Server is migrated to minimize application changes. Select the relevant workflow and schedule the migration for your site: Control-M/EM Migration: Enables you to migrate Control-M/EM. Control-M/Server Migration: Enables you to migrate Control-M/Server after you have already migrated Control-M/EM to version 8.0.00. NOTE: Along with the migration of Control-M/EM, plan for the migration of Control-M Workload Archiving data. Migration of archived job data might take a long time and might necessitate adjustments to retention parameters. For more information, see Migrating Control-M Workload Archiving.
Test the migration process	Export both the (old) EM and Control-M/Server data and import this into the new environments for testing before the Migration cutover date. The export and import process can be repeated as necessary.
Review final migration plan with BMC support	Contact BMC support two weeks before the migration date to open an issue for an AMIGO Review of the migration plan.
Troubleshooting	For more information on troubleshooting your migration, see Troubleshooting Control-M Migration or contact Customer Support http://www.bmc.com/support.
Verify new environment	Verify that the migrated data exists in the new environment. Take into account the changes between Control-M versions, as described in Changes in Control-M versions.