The customer is aware of available features and limitations of the Control-M SaaS Latest Release and qualifies for migration to SaaS.
BMC will assist Customer to run the Control-M SaaS migration tool to export the full migration details
BMC will migrate the jobs and other workload related data using migration tool.
If the on-premises Control-M/Agents aren't using any plugins, the SaaS Control-M/Agents will be installed on the same servers; otherwise, new machines will be required for the SaaS Control-M/Agents.
If the on-prem Control-M/Agent is using any plugins; Each SaaS Control-M/Agent required to be installed on a different application server using the same Agent name as in Control-M.
Existing on-prem Control-M/Agents are running on operating systems and versions which are compatible and supported with the SaaS Control-M/Agents.
If any operating systems are found which are incompatible with the SaaS Control-M/Agent, then the customer will switch to the operating systems and versions which are compatible and supported with the SaaS Control-M/Agent.
For any operational or functional reasons if the customer cannot switch to the compatible operating systems versions, then jobs running on these servers will not be migrated.
If any operating systems are found whose versions are unsupported with the SaaS Control-M/Agent, then the customer will upgrade the operating systems to versions which are supported with the SaaS Control-M/Agent.
For any operational or functional reasons if the customer cannot upgrade the unsupported versions of the operating systems, then jobs running on these servers will not be migrated.
Existing on-prem Agentless (Remote Hosts) are running on operating systems and versions which are compatible and supported with the SaaS Control-M Agentless (Remote Hosts).
Existing on-prem Agentless (Remote Hosts) are running on operating systems and versions which are compatible and supported with SaaS Control-M Agentless (Remote Hosts).
If any operating systems are found which are incompatible with the SaaS Control-M Agentless (Remote Hosts) then the customer will switch to the operating systems and versions which are compatible and supported with the SaaS Control-M Agentless (Remote Hosts).
For any operational or functional reasons if the customer cannot switch to the compatible operating systems versions, then jobs running on these servers will not be migrated.
If any operating systems are found whose versions are unsupported with the SaaS Control-M Agentless (Remote Hosts) then the customer will upgrade the operating systems to versions which are supported with the SaaS Control-M Agentless (Remote Hosts).
For any operational or functional reasons if the customer cannot upgrade the unsupported versions of the operating systems, then jobs running on these servers will not be migrated.
Migration timeline is established based on the assumption that the Customer fulfills all assigned responsibilities within the timelines specified.
Go live will be per tenant - assumption is Control-M/Server in the SaaS tenant will go live at same time.
Post Go live support days are to be used exclusively for environments going live.
Notification destinations other than Alert Window, Mail, or Job Log are not supported in the SaaS Control-M when the destination address is 'Server'.
The tool will automatically update all destinations to Control-M Alerts Window during migration.
The Notification destinations other than Mail, Program, or Terminal are not supported in the SaaS Control-M when the destination address is 'Agent'.
SaaS Control-M supports notification destination 'Program' (Linux and Windows) on an OS job type only.
The customer will provide a script/program to define as destination.
Sending direct alerts/traps to SNMP server is not supported in the SaaS Control-M.
SaaS Control-M supports configuring Alerts monitor on on-premises host.
The customer will provide a script/program to generate SNMP alerts/traps.
Direct integration with ticketing tool is not supported in the SaaS Control-M.
SaaS Control-M supports configuring Alerts monitor on on-premises host.
The customer will provide a script/program to generate tickets in the ticketing tool.
Any functionality or feature not addressed above is out of scope.
Any additional activities that exceed the scope of migration or other material modifications and impact on the project workload will necessitate a schedule adjustment and will be processed according to the Change Management procedure.