Chat now with support
Chat with Support

Migration Manager for Email Archives 10.0 - EV to Office 365 Mailboxes

EV to Microsoft Office 365

This article explains what the requirements are for an EV to Office 365 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.

Office 365 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 Office 365 module. One account should also be configured as a Global Administrator in Office 365, and be marked as that in the credentials editor.

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 for more than 10 minutes) 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 (this will only confuse things later).


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.


Create a new link for Office365 and associate the necessary modules.

SCREEN: External Application installed by the O365 module

Run the “Migration Manager for Email Archives Office365 Module Credentials Editor” and supply multiple service account credentials. When running the credentials editor, it is important to make sure the account that is logged in is the account used to run the Office 365 service.

We recommend that you add at least as many service accounts as the number of mailboxes that will be handled in parallel (Configured on the System Configuration screen)


Sync the mailboxes from the Office365 environment by clicking the Sync Mailboxes button. Wait a few minutes for this to succeed (the value displayed in the Links page for the number of containers will still show zero)

SCREEN: System Configuration -> Shortcut Processing

Update the settings so that ‘Use EWS for Processing’ is enabled, and that the ‘Config to Use’ is set to Office365

SCREEN: System Configuration ->-> Office 365 Module

Consider enabling the option to ‘Disable reminders for appointments in the past’.

SCREEN: Map Containers

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

General Considerations

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

Different flavours of Office 365 license have different size limits, as described here.  It is advised to run SQL Queries on the source environment in order to determine if any archives are likely to have:- Many large items- Many archives have more data in them than is allowed by the Office license. For more information, contact Quest Support.
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