This section will guide you through specific type of migration where source or target is a flat file folder. Once your source and target connections have been successfully configured, you can start the migration, the general process being very simple:
1. right-click the source node/mailbox(es) >>
2. select Copy ... >>
3. right-click the target >>
4. select Paste ...
"Folder" connection can read MSG, PST and also EML files.
Our Email Migrator allows you to migrate items from supported archive systems to ordinary folder . After migration the target folder copies the structure of the source mailbox and contains the migrated msg/PST files.
A. Migrating from archive
You have copied the archive system mailbox(es) and selected Paste command on the desired folder in Email Migrator console. Now the configuration dialog appears. It features three tabs with the following configuration options:
Create missing mailbox - check to create subfolder with the migrated mailbox name; this subfolder will be the root folder of the migration. If this option is not checked and such subfolder does not exist in the target folder, nothing will be migrated
Verify items migration (slow) - visible only in advanced mode (Settings/Enable Advanced Mode) - when selected the function checks if the subject and body of the migrated item are the same on source and target; However, it slows down the migration. The verification can run also after migration as a standalone process. To run it after migration, use the context menu. To do so:
1. Right-click the source mailbox and from the context menu select Compare Mailbox option
2. Right-click the target mailbox and from the context menu select Compare with Mailbox option
3. The progress dialog appears and you can check the log
Delete original shortcuts - when checked, source system shortcuts will be deleted from the user mailbox
Here you can configure notification emails that inform the defined users when the migration task is finished.
Send to - email account or group that the email should be sent to
Send from - email account that the email should be sent from
CC - email account(s) or group(s) that should be CC'd
BCC - email account(s) or group(s) that should be BCC'd
Subject - subject line of the email
Server (smtp) - network name or IP address of the server that the email will be sent from
User & Password - user account credentials to connect to the specified server
This tab contains these subtabs:
Folders - use this tab to define folders which should be excluded from migration. It may not be desired to migrate certain types of folders, e.g. Deleted items, Trash, Spam etc. Click the Add button to specify such folders. In the pop-up dialog enter the FULL PATH to the desired folder preceded by forward slash " / ". Be aware that only the specified folder will be excluded, folders with the same name but occurring elsewhere in the folder structure will be migrated. For instance, if you specify folder path "/Private", it will be excluded from the migration. However, any other folder with identical name but in different location (e.g. Inbox/Private) will be migrated.
Item Classes - applicable only for some connections - two boxes on this tab allows you to fine-tune the migration in respect to Exchange defined message classes (e.g. Calendar, Contacts, Post, various shortcuts etc.). By default only shortcuts of supported archiving systems are excluded from migration. To configure your desired settings, add/remove items in the Included Item Classes and Exclude Item Classes boxes.
Example: To migrate calendar items enter IPM.Appointment*
To migrate contacts items enter IPM.Contact*
To migrate journal items enter IPM.Activity*
Shortcuts for the following archive systems can be migrated:
oPamMessage - shortcuts created by Metalogix Archive Manager
oEnterpriseVault - shortcuts created by Symantec Enterprise Vault
oExShortcut - shortcuts created by EMC EmailXtender
oMimosaStub - shortcuts created by Mimosa NearPoint
oPERSISTMailItem - shortcuts created by HP IAP
oEAS - shortcuts created by Zantaz EAS
oAfterMail - shortcuts created by Quest Archive Manager
oBMA.Stub - shortcuts created by Barracuda Message Archiver
oTJ.KAI.Archive - shortcuts created by iQ.Suite Store
Other - time and size filtering options are activated by checking the respective check-boxes and configuring required settings
Once your desired settings are defined, click Run to start the migration.
After clicking the Save button a migration job with the specified settings will be created and saved in the Job list. However, it will not run immediately. You can run it manually later or create a PowerShell script for it. For more information, see the Job List section.
As the migration job runs, job log is being created as visible in the job list (opened from View / Show Job List). Open the detailed log e.g. by double-clicking the specific job. You will be able to view the logs for the action, even while it is still running. By clicking the Target link the target destination with newly migrated items is opened. Job can also be paused. When restarted again, already processed items are skipped and the job starts at the point where it was stopped.
Items marked with green check-mark were processed successfully. If any issue occurs (red mark), double-click it to see further details.
Finally verify the migration results in your target system by opening specific email(s) and checking that all data were migrated well (email body, attachments etc.).
Email Migrator can significantly improve the time it takes to complete migration jobs by leveraging a distributed migration model. This model essentially comprises a Email Migrator Controller (Host), a central jobs repository or queue, and one or more loosely-coupled Email Migrator agents. By automatically selecting the jobs from a central repository, Email Migrator agents are able to distribute the workload efficiently across the resource pool. The distributed model enables parallel processing of migration jobs that reduces migration time, and enables higher utilization, better workload throughput and higher end-user productivity from deployed resources.
Distributed Migration is typically used for large migration projects and relies on four main components as follows:
An SQL Server database that contains migration metadata.
Controller (or Host)
This is the primary Email Migrator Console that manages agents, the agent database and the migration jobs.
A SQL Server database that contains the repository or queue of migration job definitions which the agents can execute
This is a physical or virtual machine that is remote from the Controller machine. It is connected to through the Controller to run jobs remotely. Once connected, the Controller will push an installation of the Email Migrator onto the Agent machine, which is then configured to execute the migration jobs that are sent from the Controller. Any logging information would then be sent to the Agent Database. When an agent is executing a migration job, any interaction with the agent such as changing a configuration setting is not recommended.
Email Migrator can facilitate large migration efforts by distributing workloads across multiple machines (called "Agents") in a method referred to as "Distributed Migration".
A "Controller" machine can be configured to distribute jobs to agents manually, or through the Email Migrator Distributed Migration Wizard which is designed to streamline this setup and configuration.
When using the Distributed Migration feature, a "Controller" machine can be configured to distribute migration jobs to Agent machines in a hub-and-spoke model to help run migration jobs in parallel, to help maximize overall performance. There is the Email Migrator Distributed Migration Wizard that is designed to help streamline and configure the setup for both the Controller and Agent machines.
To start the Distributed Migration Wizard, click the Configure Distributed Migration button located in the'Connection tab of the Email Migrator ribbon.
The Wizard contains eight steps, each of which are described below.
1.The Wizard begins the configuration process with a Getting Started section. Review the information presented on this screen before proceeding to the next step.
2.Agent machines use a SQL database to share information with each other. This database must reside in a location that all Agent machines, as well as the Controller, are able to access. Please see the Agent Databases page for more details.
Enter the address of the SQL server where the database is located, or use the Browse button by the SQL Server field to browse for servers on the local system and on the network.
3.Now enter the name of an existing SQL database in the SQL Database field, or click Browse to view the databases located on the chosen SQL server. To create a new database, select the New Database button in the Browse window, and enter a name for it.
4.If specific authentication credentials are required in order to log in to the SQL server, enter them in the appropriate fields. It is recommended that SQL Server Authentication is used to connect to the Agent Database.
5. The Wizard will now enable you to copy application, environment, and user mapping settings files from the Controller machine to the Agent database to be used in place of the default settings on the Agent machines. Please see the Updating Agents section for more details.
Select Copy Settings to copy UserSettings.xml, EnvironmentSettings.xml, and ApplicationSettings.xml from the local system to the Agent database. A confirmation will appear after the settings have been successfully copied.
Note that after these settings have been copied to the Agent database and the console has been restarted, Email Migrator will no longer look in local settings files for configuration information. This means that changing local settings files will have no effect on the console's operations.
6.To make changes to settings after copying them over to the Agent database, changes need to be done directly in the Agent database.
7.Email Migrator utilizes security certificates in distributed migrations to maintain secure communication between the Controller and Agent machines. Please see the Installing a Certificate for use with Remote Agents page for more details.
Select an existing certificate to use, or create a new one through the Generate New Certificate button. When creating a new certificate, make sure to use a certificate name that does not contain any spaces. Also use a robust password that you will remember, and export the certificate to a folder where it can be found again in the future.
This certificate will automatically be used for the Controller machine where the Wizard is currently running from, whether or not it was generated now or at a previous time.
8.The Email Migrator Installation package is needed during the setup of distributed migration to ensure that all the Agents are configured properly. Select the Download Installer button to download a new copy of the installer to that system. Please see the Requirements, Configuration and Installation for Distributed Migration page for more details.
An indicator will appear at the bottom of the Wizard indicating that the download is in progress, and the Next > button will become available when the operation is complete.
9.Agents are configured and deployed at this stage. It is recommended that the Agent should be in the same network as the Controller. Enter the name of the Agent computer in the Agent Name field to find it by name, or select Browse... to browse for it in the network. The IP address of the system can also be used to locate and connect to it.
Make sure to enter the correct user name and password for the system before proceeding.
10.Email Migrator will perform a check of the specified Agent system to ensure that it meets with the required prerequisites.
If the Wizard finds that any of the services are not running, click the Enable Missing Services button to have the Wizard attempt to enable those services remotely.
Windows Server 2008 R2 or later is the recommended minimum Operating System to be used for Agent machines in Distributed Migration. If the Agent does not meet this requirement, the Wizard will throw a warning message, but it will allow you to proceed so long as the above services are available.
11.Click Next > when all services are enabled and you are ready to proceed. Then click Deploy Certificate to deploy the certificate configured above to the Agent system.
A confirmation message will appear confirming successful deployment.
12.Now select the Deploy Application button to begin the deployment procedure. An indicator will appear at the bottom of the Wizard indicating that the deployment is in progress.
13.The Summary windows shows the configuration options that have been selected for deployment, and the status of the deployment to the specified Agent(s).
To add additional Agents to the distributed migration, select the Deploy New button. The Wizard will then return to the Configure Agents screen (shown above) where the last step can be repeated for the additional Agent.
14.Click Finish at the bottom of the Summary screen to close the Distributed Migration Wizard. Then close the console and start it up again to make use of the new settings.