This quick start guide provides you with the basic information to configure CloudM Migrate for a migration from MBOX and EML Archives. It is highly recommended that you read the application documentation in full for your platforms in order to understand all of the options available to you during a migration.
The workstation running CloudM Migrate must have access to the file paths where the archives files are stored. If using multi-server you map the location of the files to the secondary machines.
Create a Mapped Network Drive using SysInternals PSTools
- Download PSExec in the migration server and extract the zip file from https://docs.microsoft.com/en-gb/sysinternals/downloads/psexec
- Open an elevated (run as administrator) Command Prompt and navigate to the unzipped PSExec folder
- Run
psexec -i -s cmd.exe
-
Whoami
will confirm that you're logged in as SYSTEM - Run
net use z: \\servername\sharedfolder /persistent:yes
to connect to the shared drive as the SYSTEM User. Optionally add/user:username
to map the drive as a different user.
Service Access to Mapped Drives
If you are using the web version of CloudM Migrate, or secondary servers then you should make sure that the CloudM Migrate service has access to mapped drives if the files are located there. Please see the article on making mapped drives available for more information.
Step-by-step guide
Select 'Mail Archive' in the platform selector
Enter your license key. Please click Help > Licence Key to apply the licence. Paste in the license key and click Apply.
Setup your destination platform. Instructions are available for G Suite, Google Vault, Microsoft Exchange or Office 365 and Exchange Online Archives.
Test the configuration using the configuration test tool, available at ‘Tools->Check Connections’. See this article for more information about the connection test tool. You will also need to complete the settings for the destination platform before running this test. If any problems are encountered with the connection test, please examine the error and make the adjustments to your configuration settings.
Generate your user list and select the users and items you would like to migrate in the ‘Users/Resources’ tab. When migrating archive files you must specify the path to the archive for each user you want to migrate in the 'Archive Path' setting
Start your migration
If you have any specialized needs, or would like to learn more about the migration options and how they can be used to make sure your migration is performed in an appropriate way for your organization, please refer to the advanced settings.
The table below shows the supported features for Email messages from Mail Archive (MBOX and EML) to another destination system.
Mail Archive |
Google Workspace for Business/Education |
Google Vault |
Microsoft Office 365, Exchange 2007/2010/2013/2016 |
---|---|---|---|
User Provisioning and Migration |
|
|
|
Email Messages |
|
|
|
Folders |
|
|
|
Date Ranges |
|
|
|
Attachments |
|
|
|
Attachments to File Storage |
|
|
|
Sticky Notes |
|
|
|
Supported MBOX formats
CloudM Migrate supports all MBOX file formats:
- mboxrd
- mboxo
- mboxcl
- mboxcl2
Migrating Mail Archives (MBOX/EML)
Mbox and EML Archives can be migrated to any supported destination platform.
In order to migrate archives successfully, several things need to be done:
-
Ensure that archives are available from the workstation running the tool. In order for the migration tool to be able to migrate archives the files and folders that comprise archives must be available for the migration tool to access. Often, what needs to be done is to copy all of the archives to a central location which can be accessed through the file system by the tool.
Service Access to Mapped Drives
If you are using the web version of CloudM Migrate, or secondary servers then you should make sure that the CloudM Migrate service has access to mapped drives if the files are located there. Please see the article on making mapped drives available for more information.
- Specify the correct path to the archives. Provide either the folder path or the full path to a specific MBOX file, or provide the folder path for EML files. The tool will process all sub-folders if a folder path is provided. If you have multiple MBOX files to process for a user, place them inside a folder and specify the path to the folder.
Take care to ensure you provide the correct path and file for each user.