Scalix to Microsoft 365 Migration

System Requirements (Self-Hosted)


  • 64 bit Operating system: Windows Server 2016+ (Clean build recommended)
  • Microsoft .NET Framework 4.8
  • Recommended system specification - Primary Server:
    • 3GHz 8 Core Processor or better
    • 200+GB Disk space
    • 16+GB Memory
  • Recommended system specification - Secondary Server(s):
    • 3GHz 4 Core Processor or better
    • 100GB Disk space
    • 8+GB Memory

If you are looking to complete a 'large migration' (a migration of more than 25,000 users or 10 million objects), refer to the following articles for additional considerations:

If you are storing Drive document mappings and running a large migration, contact the support team.

Required ports

Primary and Secondary servers will communicate with the source and destination platforms, and the CloudM Migrate licensing platform using HTTP/HTTPS. Therefore ports 80 and 443 will need to be open between these environments

The URLs accessed for the license server are as follows.


There is also the following to consider:

  • SQL server runs on TCP 1433 and UDP 1434 - SQL server needs to be installed and set to TCP or UDP on the Primary/SQL Server. For information on setting the TCP to 1433, refer to this following article.
  • Redis runs on port 6379
  • gRPC on the below TCP ports. Note: It is possible to customise these ports when installing via Command Line using the instructions here: Installing / Upgrading from the Command Line 
    30061 (Primary Service)
    30062 (Secondary Service)
    30063 (Results Logs Service)
  • All of Google's API endpoints are listed here:
  • All Microsoft 365 URLs and IP address ranges are listed here:

CloudM Migrate Hosted

CloudM Migrate Hosted makes migration as simple as possible. There are no system requirements or installation, you can simply access the Hosted migration platform and configurations are pre-provisioned. See here for more information.

Platform prerequisites

Source Platform prerequisites

  • The credentials (username and password) of an administrative user in Scalix
  • The name of a test account in the Scalix system that can be used for testing
  • Scalix server IP address and Server Name

Configuring Scalix

In order to access all data within the Scalix system, data is retrieved using both management and messaging APIs. The permissions required to use each of these are slightly different and may require configuration of a specific user to perform the migration. To read user lists from the system, a full system administrator is required. To set a user as a full system administrator, log into the Scalix Administration Console, select a user, navigate to the ‘Advanced’ tab and ensure that the ‘Is full administrator’ box is selected. The user can be either a standard or advanced user. Alongside being a full administrator, the user must also have mboxadmin rights. To set the user called ‘sxadmin to have mboxadmin rights, from a command line run the following command as root:

/opt/scalix/bin/ommodu -o sxadmin -c +mboxadmin

The path to your Scalix administration binaries may differ, please refer to your Scalix installation or system administrator for details.

The same user should be made a full system administrator and have mboxadmin rights.

It is highly recommended that users are prevented from accessing the system and the Scalix service restarted just before starting a migration. Several problems have been seen with Scalix when users have been accessing the system during migrations that can prevent migrations from completing successfully

In order to export users from Scalix, the Export Name in the tool configuration must match the primary Email address of the users within Scalix. This means that the users primary Email address (the one with which the account was created) must be the top entry in every users information in the Scalix Administration Console. If this is not done, users will fail to migrate (usually with error M0022). Due to limitations of the Scalix API this is a manual process that cannot be automated by the tool Folder names containing backward or forward slashes cannot be migrated by the migration tool due to limitations of the Scalix API. Users should be instructed to rename these folders prior to migration.

Configure Source Platform Settings - Scalix

Choose Scalix as the migration source and enter your Scalix settings into CloudM Migrate and then click next.


  • Server Address - The hostname or IP address of the Scalix server.
  • Server Names - All server names (not IP addresses) that are to be migrated from. Separate each name with a comma.
  • Admin Username - The username of an administrator account with full rights on your Scalix server.
  • Admin Password - The password of the specified administrator account.
  • Test Username - Specify the full email address of a user within the system, this must be a real user and must be the primary email address; not an alias.

Configure Destination Platform Settings - Microsoft 365

Basic Platform Settings

Choose Microsoft Office 365 as the migration source and enter your Microsoft Office 365 settings into CloudM Migrate and then click Next.

  • All Advanced Settings are set to a default value, designed to ensure that your migration will work without additional configuration. You should only edit the Advanced Settings if instructed to by CloudM Support or in a CloudM Knowledge Base article.


Set the following settings:

  • Office / Microsoft 365 Plan - Set to Office 365, Office 365 Germany or Custom, as required.
    • If you want to migrate Shared Calendar Permissions, you will need to set the Plan to Custom, as you need to provide an Autodiscovery Service URL. Direct Exchange EWS URL should not be presented.
  • Authentication Method - Choose the authentication type that will be used with the server. For Microsoft 365, set to Modern.
  • Domain Name - The domain name of the Exchange domain. This should be the internet domain of the Exchange system and not the local domain name.
    • This might be the part after the @ in your administrator email address. 
    • If migrating from several different domains, several migrations will be needed.
  • Admin Username - The email address of a global administrator within your Microsoft 365 environment.
  • Admin Password - The password for the global administrator account specified earlier.
  • Test Username - The email non-admin user who is already present in the system to test connections.
    • Specify a primary SMTP email address (or just the part before the @ symbol and the domain name will be appended). The test user must have an active mailbox.]

Advanced Settings

For Microsoft 365 advanced settings, see here.

Select which items to migrate

It's now time to add which items you'd like to migrate.


To add the items from that you want to migrate from your source platform to your destination platform, select Add items to migrate drop down menu and click on one of the following options:

  • Get Items from source - Get a full list of all items in the source platform.
  • Bulk add / import items - Upload a CSV file to bulk add users.
  • Add User/Resource/ Group/Shared Drive/Team Site/Microsoft Team etc.- Manually add an item of the selected item type.

Selecting a Star next to any specific user or users will prioritize their migration. When a migration starts, threads will be assigned to any starred user first so that their migration can start immediately. 

At this point you can choose what to migrate for each user, you can migrate Mail, Contacts, Calendars, Tasks, Classic Sites, Notes and Channels.

Enter your user's full email address within the Export Name field. If you have already created your Microsoft 365 users, then you will just need to enter their username.

Select how much content to migrate

CloudM Migrate lets you decide how much content to migrate to your domain by specifying required date ranges. 


If you are changing your email address as part of the migration you can verify that the domain names are correct here. You can also specify specific Address Replacements in the respective section of the advanced settings.

Environment Scan

Environment Scan allows you to plan and prepare your migration by performing analysis of your source file and mail environment and reporting important information such as item counts, data volume, permissions, and folder depth.

Reports are produced which can be exported and analysed. Using the information provided you can estimate your migration's duration more accurately, and address any potential issues before your migration even begins.


Selecting Scope of Scan


Depending on your source platform, you can choose to scan files, emails, or both sets of items.


  • Leaving the Report on File Permissions setting unchecked will speed up the Environment Scan process.
  • In order to include Report on File Permissions in the process, you will need to check this setting AND enable Document Sharing (or a setting related to document sharing) in the Source Platform settings. If either is not enabled, the Environment Scan will not scan or report on File Permissions.


Your CloudM Migrate userlist is used to define the scope of the scan. You can choose to scan all accounts from your list, or restrict the scan to users selected for migration.


How to run an Environment Scan

After entering your source and destination server settings, populating your userlist, and configuring your settings, you will be prompted to run an environment scan. It is optional, but recommended for file platforms.

Click Start and then confirm by selecting Start Environment Scan on the pop-up box to begin the scan. CloudM Migrate will connect to your source environment and capture file and / or mail information. This can take up to several hours, depending on the amount of data present.


Once the scan completes, the data is reported on the Environment Scans page and can be exported to file, using the Export Scan Results option.


Start your migration

To begin your migration, select Start.



Review your migration results

During the migration process, CloudM Migrate will report back in real time exactly who is being migrated and the items being processed. All you now need to do is sit back, relax and wait for your migration to complete.

Check the progress of your migration.

Once complete you can download a full report for your migration.

Delta Migrations

CloudM Migrate supports delta migrations of all migration types. To run a delta migration after the first pass, simply start the migration again. Already processed mailbox items will be skipped, and file items will be checked for changes and re-migrated if updated since the previous run. More info:

Was this article helpful?
0 out of 0 found this helpful