Chat now with support
Chat with Support

Migration Manager for Email Archives 10.0 - From EAS

Migration from EAS

This article explains what the requirements are for migrating away from EAS, and then covers the basic steps that should be followed to start such a migration.



The following is a list of requirements.

The EAS module should be installed on each the 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.

Basic Steps

The following are the basic steps to start this type of migration.

SCREEN: Modules

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 Migration Manager for Email Archives Core has not had contact with the module) and that the module versions are as expected.

SCREEN: Active Directory

Select and enable one or more domains for synchronization.

SCREEN: EAS Environment

Add a new EAS environment, specifying the following:

Assign Post Processing module to EAS Link


Select the newly created link, and map a Shortcut Process Module to it.


Ensure that the link for the migration target is added, and modules associated with it.


Ensure that the Default Staging Area is configured correctly. Depending on the migration, the free space, and the number of document stores being used as the source for the migration, the ‘high water mark’ can be adjusted upwards.

SCREEN: Bulk Mapping

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 EAS as a source.

General Considerations

The following general considerations should be taken into account for this type of migration:

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating