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.
Modules installed on source
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.
Modules installed on appropriate bridgehead to reach target
Office 365 and Post Processing modules are the two which are primarily needed to work with this type of migration.
AD Collector module installed
An AD Collector module should be installed so that it can collect user-level information for the migration project.
Staging Area created
One or more staging areas should be setup, of an appropriate size and should be excluded from virus scanners.
Ingest accounts configured for App Impersonation
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.
Apply appropriate failed item threshold
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 Archive Shuttle 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 Archive Shuttle 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.
Add EV Environment
Screen: EV Environment
Add the Enterprise Vault source environment.
Add Source Links
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).
Add Staging Area
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.
Configure Folder-Less Item Handling
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 Office 365 Link
Create a new link for Office365 and associate the necessary modules.
Set Office 365 Credentials
You have a choice here, either:
Option 1: Service account user name/password
Screen: External Application installed by the O365 module
Run the Archive Shuttle 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).
Option 2: OAuth authentication
Screen: Office 365 module
Run the Archive Shuttle Office365 Module Credentials Editor and add OAuth credentials. Then test the connection. Then, from the Office 365 Module, select the Use modern authentication (OAuth) option.
Synchronize Office 365
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)
Update Shortcut Processing Module Configuration
Screen: System Configuration -> Shortcut Processing
Update the settings so that ‘Use EWS for Processing’ is enabled,.
Consider disabling reminders for appointments in the past
Screen: System Configuration -> Office 365 Module
Consider enabling the option to ‘Disable reminders for appointments in the past’.
Map one or more Containers
Screen: Map Containers
One or more containers can now be mapped and migration started.
The following general considerations should be taken into account for this type of migration:
- A call should be logged with Microsoft to get the throttling limits raised for the duration of the migration, otherwise ingest performance will be reduced.
- When migrating from a pre EV10.0.3 system extraction of data may be slower than expected if Enterprise Vault Collections have been used. Access to the data inside the CAB file is single threaded. This issue does not exist in Enterprise Vault 10.0.3 and later.
- 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 licenseThe following articles may help:
- It is advised to ensure a high level of Mailbox Parallelism and a low level of item/batch parallelism. This gives least chance to hit throttling limits.
- It is advised to have 5 accounts configured with application impersonation rights in Office 365. This gives least chance to hit throttling limits.