Control-M SaaS Migration

Control-M SaaS migrations enable you to migrate some or all of your Control-M Self-HostedClosed environment to Control-M SaaS. This eliminates the need to maintain a self-hosted Control-M/Enterprise Manager, one or more self-hosted Control-M/Servers, and their databases. Before you migrate, BMC Services or a BMC certified partner helps you scan Control-M Self-Hosted environment, as described in Scanning a Control-M Self-Hosted Environment, to determine the migration type that best suits your organization.

  • If you are unable to upgrade to self-hosted Control-M/EM 9.0.21.300, you might still be able to perform a full migration, as described in Full Migration.

  • You cannot migrate the following components to Control-M SaaS, but you can connect them to Control-M SaaS Unified ViewClosed: 

    • Control-M for z/OS environments.

    • Self-hosted Control-M/Servers that are connected to Agents that run unsupported plug-ins, or that are installed on unsupported operating systems.

  • If your self-hosted Control-M/Servers or Control-M for z/OS environments execute more than 100,000 jobs daily, you must distribute these jobs on two or more self-hosted Control-M/Servers or Control-M for z/OS environments.

  • You cannot revert a Control-M SaaS migration.

There are three Control-M SaaS migration types, as follows:

Full MigrationLink copied to clipboard

Migrates the data on the following self-hosted components from Self-Hosted Control-MClosed to Control-M SaaS:

  • One Control-M/EM.

  • All Control-M/Servers.

This eliminates the need to maintain these self-hosted components and their associated databases.

The following diagram shows the logical architecture of a typical Full Migration environment:

For more information, see Control-M SaaS Full Migration.

Unified View MigrationLink copied to clipboard

Migrates the data from one Control-M/EM and connects the following self-hosted components to SaaS Control-M Unified ViewClosed:

  • Control-M/Server

  • Control-M for z/OS

This eliminates the need to maintain Control-M/EM and its database.

The following diagram shows the logical architecture of a typical Control-M SaaS Unified View Migration environment:

For more information, see Control-M SaaS Unified View Migration.

Custom MigrationLink copied to clipboard

Migrates the data on one Control-M/EM from Self-Hosted Control-M to SaaS Control-M, and enables you to do the following:

This migration eliminates the need to do one or more of the following:

  • Maintain a self-hosted Control-M/EM and its database.

  • Maintain self-hosted Control-M/Servers and their associated databases.

The following diagram shows the logical architecture of a typical Custom Migration environment:

For more information, see Control-M SaaS Custom Migration.