CloudM Migrate Service Manager Overview & Configuration

Updated June 17, 2026 10:11

The CloudM Migrate Service Manager lets you monitor, control, and configure the migration services in a CloudM Migrate Self-Hosted environment — starting and stopping services, adjusting performance and concurrency, and viewing service logs — all from the primary server's interface.

What's changed in CloudM Migrate 5.0: The Service Manager is no longer a separate Windows application. It is now built directly into the CloudM Migrate interface as the Service manager item in the left-hand navigation, and you now manage every service — primary and secondary — from the UI on the primary server.

Accessing the Service Manager

In CloudM Migrate 5.0 and later, sign in to CloudM Migrate on your primary server and select Service manager from the left-hand navigation menu.

Previously (4.7.6 and earlier), the Service Manager was a standalone application opened from the Windows Start menu (Start > All Programs > CloudM > CloudM Migrate Service Manager), and secondary services were configured on each secondary machine. In 5.0 the standalone application has been removed and all management is centralised in the primary's UI.

Self-Hosted vs Hosted: The Service Manager is intended for CloudM Migrate Self-Hosted users. If you are a CloudM Migrate Hosted user, server-level management is handled by CloudM, and access is restricted to CloudM Support and Development teams.

The Service Manager screen

The Primary service information panel at the top shows the primary service's machine name, current state, when the state was last updated, and the installed version. From here you can:

Actions — start, stop, or restart the primary migration service.
Settings — open the primary service settings (see below).

Below the panel, every server in your migration network (primary and secondary) is listed with its State (for example, Running, with a Primary or Secondary label), Machine name, Version (shown in green when the server is on the most recent version installed on your primary), and State updated on timestamp. You can search the list by machine name. Each server also has:

View logs — view the event logs for the selected server.
An ellipsis (⋮) menu with Start, Stop, Restart, and Service settings for that individual server, plus Download RDP — which downloads an RDP file you can launch to connect to that secondary server if required.

Starting and stopping services

You can start, stop, and restart the primary service (from the Actions menu) and any secondary service (from its ellipsis menu). These options are state-aware — for example, Start is only available when a service is stopped, and Stop only when it is running — and you'll be asked to confirm, as stopping or restarting a service may interrupt ongoing migrations.

Stopping the primary service does not stop the interface. The CloudM Migrate UI continues to work while the primary migration service is stopped, so you can still manage your environment.

Service settings

Open Settings on the primary panel to edit the Primary service settings. Settings that differ from their defaults are indicated with an orange dot, and you can revert everything with Restore default settings.

Primary service settings

Run secondary service — determines whether the secondary service is run. Many secondary services can run within one migration network, and secondary and primary can run on the same server.
Validate SSL certificates — whether the service should validate SSL certificates of the services it connects to.
Maximum concurrent batches — the maximum number of concurrent configuration batches (1–100).
Maximum migration worker processes — the maximum number of migration worker processes to run per secondary service (1–500).
Allocate migration items busy first — allocate migration items to secondary servers using a busy-first algorithm.
Auto upgrade secondary services — when enabled, secondary services running an older version are automatically upgraded to the primary service's version. This means you only need to apply an upgraded version of Migrate to the primary; eligible secondaries are then upgraded for you.
Redis service location — if the Redis server is not at the same address as the PostgreSQL server, set its address here. Credentials can also be provided, e.g. 8.8.8.8 or 8.8.8.8,password=Password1.

Secondary service settings

Secondary services use a smaller set of settings:

Validate SSL certificates — whether the service should validate SSL certificates of the services it connects to.
Maximum migration worker processes — the maximum number of migration worker processes to run per secondary service (1–500).

You can set default secondary services settings that apply to all secondaries, and you can also configure an individual secondary by choosing Service settings from the ellipsis (⋮) menu next to that server in the list.

Applying configuration changes

After saving any service settings, you need to restart the service for the changes to take effect. Use the Actions menu (primary) or the server's ellipsis menu (secondary) to restart.

Viewing logs

Select View logs on any server in the list to view the event logs for that server, which is useful for diagnosing service or migration issues.