Chat now with support
Chat with Support

Migration Manager for Email Archives 10.0 - EV to Exchange Mailboxes

EV to Microsoft Exchange Migration

This article explains what the requirements are for an EV to Exchange migration, and then covers the basic steps that should be followed to start such a migration.



The following is a list of requirements.

The EV-type modules should be installed on each appropriate source Enterprise Vault server involved in the migration. The EV import module is not required on these machines.

Exchange and Post Processing modules are the two which are primarily needed to work with this type of 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.

5 accounts should be configured with Application Impersonation rights, and those accounts should be added to the credentials editor on the machine running the Exchange ingest module.

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 (this indicates 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: EV Environment

Add the Enterprise Vault source environment.


Configure all appropriate source links. Select the links, and then click on ‘Map Modules’, create the item database(s) and enable archive gathering. Ensure there is no import module specified on the links as this may impact the process later on.


Add all appropriate target links. An ingest and post-processing module should be associated with each possible target Exchange Database.


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

SCREEN: System Configuration

Many versions of Enterprise Vault allow archiving of items in a folder-less area called the Top Of Information Store. On the System Configuration, enter a folder name to be used for placing the items in the target archive.

SCREEN: System Configuration

Ensure that the migration providers are listed in the required order and that the AutoDiscoverURL is specified if required. The account which is to be used for ingest needs to have Application Impersonation rights. For more information, contact Quest Support.

SCREEN: System Configuration -> Exchange Import Module

Consider enabling the option to ‘Disable reminders for appointments in the past’ this will prevent pop-ups appearing from Outlook on end-user machines when old appointments are processed.

SCREEN: Map Containers

One or more containers can now be mapped and migration can begin.

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