Installing / Upgrading from the Command Line

Shaun Richards

May 08, 2025 09:53

CloudM Migrate can be installed from the command line, with and without user interaction. To view the help and available options run the installer with the -h switch. For example

C:\Install> CloudM-Migrate-<version>.exe -h

To install CloudM Migrate with no interaction, you can use the -q switch, and you should also specify several installer properties:

Note that elevated permissions or UAC (User Access Control) are required to run the installation command non-interactively with the -q flag.

CONNECTIONSTRING=<value> (Full PostgreSQL Connection string required)
USEEXISTINGSQL=<true/false> (Default false)
INSTALLMASTER=<true/false> (Default true)
INSTALLSLAVE=<true/false> (Default true)
INSTALLWEBAPP=<true/false> (Default true) 
LAUNCHWEBAPP=<true/false> (Default false) 
MAXUSERSPERSLAVE=<value> (Default 10)
PRIMARYSERVICEPORT (default 30061)
SECONDARYSERVICEPORT (default 30062)
RESULTSLOGSSERVICEPORT (default 30063)
ADMINEMAIL=<value> (Email address of user to create as web client admin)
ADMINPASSWORD=<value> (Password to create for the web client admin)

So, the full command line using an existing PostgreSQL Server would look like:

CloudM-Migrate-4.4.exe -q LAUNCHWEBAPP=true USEEXISTINGSQL=true INSTALLMASTER=true INSTALLSLAVE=true CONNECTIONSTRING="Host=server.local;Username=poweredby;Password=password;Database=poweredby;" ADMINEMAIL=admin@domain.io ADMINPASSWORD=password

Where -q will allow it to run in quiet mode.

If a CONNECTIONSTRING value is specified then the USEEXISTINGSQL value is automatically ignored and set as TRUE.

Installing using custom ports

If installing using custom ports, be aware that custom ports need to match on primary and secondary servers in order for them to be able to communicate.

For example, if installing on a primary with the following custom ports

Primary service port (2303)
Secondary service port (2304)
Results logs service port (2305)

Then the full command line using an existing PostgreSQL Server would look like:

CloudM-Migrate-4.4.exe -q CONNECTIONSTRING="Host=server.local;Username=poweredby;Password=password;Database=poweredby;" USEEXISTINGSQL=false INSTALLMASTER=true INSTALLSLAVE=true INSTALLWEBAPP=true INSTALLDESKTOP=false LAUNCHWEBAPP=false MAXUSERSPERSLAVE=20 ADMINEMAIL=admin@domain.io ADMINPASSWORD=password PRIMARYSERVICEPORT=2303 SECONDARYSERVICEPORT=2304 RESULTSLOGSSERVICEPORT=2305

The full command line to then install a secondary server would look like:

CloudM-Migrate-4.4.exe -q LAUNCHWEBAPP=true USEEXISTINGSQL=true INSTALLMASTER=false INSTALLSLAVE=true MAXUSERSPERSLAVE=10 INSTALLWEBAPP=false INSTALLDESKTOP=false ADMINEMAIL=test@youremailaddresshere.com ADMINPASSWORD=MyPassword CONNECTIONSTRING="Data Source=CTS-MASTER\SQLEXPRESS;User Id=PoweredBy;Password=MyPassword;DataBase=PoweredBy;Connection Timeout=60" PRIMARYSERVICEPORT=2303 SECONDARYSERVICEPORT=2304 RESULTSLOGSSERVICEPORT=2305

Upgrading

Upgrading is the same as installing. It just detects that you have an earlier version of the product installed already.

However, if you are upgrading to version 4.4 or higher from a previous version of Migrate, the below variables need to be used.

MIGRATESQLSERVER (true/false) : Used to choose to migrate Microsoft SQL server data to PostgreSQL or not. If this is set to True, a MigrateSqlServerConnectionString value is then mandatory. This value is False by default.
MIGRATESQLSERVERCONNECTIONSTRING: Connection string of the Microsoft SQL server to migrate from.

Examples

Below are some installation scenarios with command line examples.

New installation using an existing PostgreSQL server.

CloudM-Migrate-4.4.exe -q CONNECTIONSTRING="Host=server.local;Username=poweredby;Password=password;Database=poweredby;" USEEXISTINGSQL=false INSTALLMASTER=true INSTALLSLAVE=true INSTALLWEBAPP=true INSTALLDESKTOP=false LAUNCHWEBAPP=false MAXUSERSPERSLAVE=20 PRIMARYSERVICEPORT=30061 SECONDARYSERVICEPORT=30062 RESULTSLOGSSERVICEPORT=30063 ADMINEMAIL=admin@domain.io ADMINPASSWORD=password

Upgrade from a version of Migrate with 4.4 or higher with a separate PostgreSQL server.

CloudM-Migrate-4.4.exe -q CONNECTIONSTRING="Host=server.local;Username=poweredby;Password=password;Database=poweredby;" USEEXISTINGSQL=true INSTALLMASTER=true INSTALLSLAVE=true INSTALLWEBAPP=true LAUNCHWEBAPP=false MAXUSERSPERSLAVE=20 PRIMARYSERVICEPORT=30061 SECONDARYSERVICEPORT=30062 RESULTSLOGSSERVICEPORT=30063 ADMINEMAIL=admin@domain.io ADMINPASSWORD=password

Upgrade from a version of Migrate prior to 4.4 and migrate the data from Microsoft SQL Server to PostgreSQL.

CloudM-Migrate-4.4.exe -q MIGRATESQLSERVER=true MIGRATESQLSERVERCONNECTIONSTRING="Server=server.local\PoweredBy;Database=PoweredBy;User Id=PoweredBy;Password=password;Connection Timeout=60;" INSTALLMASTER=true INSTALLSLAVE=true INSTALLWEBAPP=true LAUNCHWEBAPP=false MAXUSERSPERSLAVE=20 PRIMARYSERVICEPORT=30061 SECONDARYSERVICEPORT=30062 RESULTSLOGSSERVICEPORT=30063 ADMINEMAIL=admin@domain.io ADMINPASSWORD=password

Upgrade from a version of Migrate with 4.4 or higher with PostgreSQL on the primary.

CloudM-Migrate-4.4.exe -q USEEXISTINGSQL=true INSTALLMASTER=true INSTALLSLAVE=true INSTALLWEBAPP=true LAUNCHWEBAPP=false MAXUSERSPERSLAVE=20 PRIMARYSERVICEPORT=30061 SECONDARYSERVICEPORT=30062 RESULTSLOGSSERVICEPORT=30063 ADMINEMAIL=admin@domain.io ADMINPASSWORD=password

Installing a secondary server

CloudM-Migrate-4.4.exe -q LAUNCHWEBAPP=true USEEXISTINGSQL=true INSTALLMASTER=false INSTALLSLAVE=true MAXUSERSPERSLAVE=10 INSTALLWEBAPP=false ADMINEMAIL=test@youremailaddresshere.com ADMINPASSWORD=MyPassword CONNECTIONSTRING="Host=server.local;Username=poweredby;Password=password;Database=poweredby;" PRIMARYSERVICEPORT=30061 SECONDARYSERVICEPORT=30062 RESULTSLOGSSERVICEPORT=30063