Migration from SourceOne
This article explains what the requirements are for migrating from SourceOne or EmailXtender to another environment, and then covers the basic steps that should be followed to start such a migration.
The following is a list of requirements.
The SourceOne module should be installed on an appropriate source server.
The appropriate modules should be installed on each appropriate target server involved in the migration.
An AD Collector module should be installed so that it can collect user-level information for the migration project.
One or more staging areas should be setup, of an appropriate size and should be excluded from virus scanners.
The Stage 2 workflows should be reviewed, and if necessary, customized to meet the needs of the project.
It is best practice to find an appropriate failed item threshold for the project/customer and apply that at the links level. This way all mappings which are created will inherit this value.
The following are the basic steps to start this type of migration.
All Migration Manager for Email Archives modules must be enabled, and optionally a schedule for them defined. It is important to verify that none of the modules have a red background (indicating that Archive Shuttle Core has not had contact with the module) and that the module versions are as expected.
Select and enable one or more domains for synchronization.
Configuration of EmailXtender is done in the same way as SourceOne.
Add a new SourceOne environment, specifying the following:
A Link Database will be created for this environment. It is possible to override the SQL Server and instance, if required.
The module will scan for organizations and present them in a list. The required organizations should be enabled so that the module can scan for archives.
Ensure that the link for the migration target is added, and modules associated with it.
Ensure that the source links have a Shortcut Processing module assigned to them. This module will scan mailboxes to find shortcuts, this is required before import can begin.
Ensure that the Default Staging Area is configured correctly. Depending on the migration, the free space, and the number of archive foldersbeing used as the source for the migration, the ‘high water mark’ can be adjusted upwards.
SourceOne does not maintain folder information for items. Therefore, a folder will be created to migrate items into. The name of this folder can be specified under ‘Folder name for folder-less items’ on the General System Settings Page.
The module scans for shortcuts in a mailbox and any items which have a shortcut will be migrated to the current folder where that shortcut resides.
One or more containers can now be mapped and migration can begin. It is often easiest to use a filter on the bulk mapping screen to show only SourceOne as a source.
The following general considerations should be taken into account for this type of migration: