System Requirements (Self-Hosted)
Environment
- 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.
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.
- portal.thecloudmigrator.com
- tracker.cloudm.io
- migratortracker-hrd.appspot.com
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.
Destination Platform - Exchange
Prerequisites
- PowerShell, bundled with Windows Server 2008 R2 or Windows 7 and higher. If Powershell is not installed on your workstation, you can download it (as part of WMF) from Microsoft.
- The credentials (username and password) of an administrative user in Exchange 2010 SP1+.
- The name of any mail enabled account within Exchange 2010 SP1+.
- The URL for Autodiscovery, or the Direct Exchange Web Services URL for your Exchange 2010 SP1+ installation. Something like https://yourserver/autodiscover/autodiscover.xml.
- Setup application impersonation for Exchange 2010 SP1+.
For information about migrating Exchange Public Folders please see the knowledgebase article.
Source Platform Prerequisites
Installing Powershell
If you're running Windows Server 2008 R2 and above, or Windows 7 and above then Powershell is installed and you dont need to do anything! If not then you will need to download it from Microsoft.
Installation is easy, just follow the steps of the installer.
Setting up Application Impersonation for Exchange
When migrating from Exchange 2010 or above, you will need to set up application impersonation in order for CloudM Migrate to access and migrate your users.
To do this, you need to open a powershell session within your Exchange server and use the following command:
New-ManagementRoleAssignment –Name "CloudMigratorImpersonation" –Role "ApplicationImpersonation" –User ADMIN
Replacing ADMIN with the email address of an administrator user on your Exchange server.
Select your configuration
Select the Exchange 2010 SP1+ configuration item.
Source Platform - Exchange 2010 SP1+
Choose Exchange 2010 SP1+ as the migration source and enter your Exchange 2010 SP1+ settings into CloudM Migrate and then click next.
- Autodiscovery Service URL – In order to connect to the correct server, autodiscovery is used to obtain the server information. Input the URL to the autodiscovery service for your domain. The value for your Microsoft Exchange server is like https://yourserver/autodiscover/autodiscover.xml.
- Admin Username – Enter the full email address of your Microsoft Exchange admin user.
- Admin Password – Enter the password of the admin user.
- Domain Name – Enter the domain name you will be migrating from. This should be the Internet domain name, not the local domain name.
- Test User Name – Enter an email address of an active user within your Microsoft Exchange system. This account is used to test connections as in most cases the admin account will not be mailbox enabled.
CloudM Migrate will now perform a small connection test to verify that the details you have entered are correct. If this fails you may have entered something incorrectly. If you are failing to resolve the issue please contact CloudM Support via the chat icon.
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
Items
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.
Users
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: