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:
- Large Migration Infrastructure
- Running SQL Server or Redis on an Independent Server
- Existing SQL Server Database Configuration
If you are storing Drive document mappings and running a large migration, contact the support team.
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: https://support.google.com/a/answer/60764
- All Microsoft 365 URLs and IP address ranges are listed here: https://docs.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide
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.
Configure Source Platform - Oracle Communications
- Server Address – The hostname or IP address the Oracle Communications server
- Server Port – The port number for the Oracle Communications server
- Admin Name – The full login name of an admin user if using ‘Admin Credentials’ as the authentication type.
- Admin Password – The password of the admin user is using ‘Admin Credentials’.
- Test Username - Specify a test email address or username to test connections to the Oracle Communications server when using Admin Credentials as the Authentication Type.
- Test Password - Specify the password for the test user to test connections to the Oracle Communications server if user passwords are to be used.
- Start TLS – Set to true to use Start TLS/SSL
Authentication Type - Choose whether to use admin or user credentials to authenticate to the Oracle Communications server.
- This is set to User Credentials by default, where the users individual credentials are used to connect to the Oracle Communications accounts.
- If your server supports delegated access for administrative users then this can be set to Admin Credentials and the credentials provided for the admin user will be used to authenticate for all accounts. CloudM Migrate uses PLAIN authentication with Authzid.
- We also support Proxy Auth if the server supports it.
- Special Folder Names - Specify the full name (case sensitive) of the Oracle Communications special folders. You can specify a folder name for Inbox, Sent Items, Drafts and Deleted Items. These may differ depending on the Oracle Communications server in use and should be specified as required for your Oracle Communications server. If your Oracle Communications server does not support one of the available special folders, leave it empty.
- Remove Label Prefix - Remove the specified value from the beginning of any Oracle Communications folders/labels. This can be useful if your Oracle Communications server prefixes all folders with [INBOX] or similar.
- Replace Folder Strings - Specify any replacements that will be performed within folder/label names. Sometimes, Oracle Communications uses a . (dot) to separate folders and to replace this with a forward slash (as normally required to separate folders) specify a dot and a forward slash in this option.
- Auto Generate Missing Message IDs - If messages are found with no ‘Message-ID’ header, automatically generate one. Note that the ID is generated using a hash of the message header contents to enable messages with no ID to work with migration history.
- Ignore Search Date Range - Ignore the configured mail date range and search for ALL messages. This can help with retrieving messages on restricted Oracle Communications servers.
- Contact Server Address - The URL for the contact server.
- Contact Server Username - The Username credentials for the contact server.
- Batch Size - The number of address book contacts to process per batch.
- Contact Server Password - The Password Credentials for the contact server.
- Calendar Server Address - The URL for the calendar server.
- Calendar Server Username - The Username credentials for the calendar server.
- Calendar Exclusions - List of excluded internal calendar URLs that will not be exported.
- Calendar Server Password - The Password Credentials for the calendar server.
- Connect Timeout - The server connect timeout in seconds.
- Read Timeout - The server connect timeout in seconds.
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.]
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 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.
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: