Below you’ll find a checklist with requirements for an Enterprise Vault to Office 365 migration. It also covers basic steps to start an EV to O365 migration. For more information about these requirements and steps, look here.
Before performing an EV to O365 migration, ensure the following requirements are met:
- Modules are installed on the source.
- Modules are installed on appropriate bridgehead to reach target.
- The AD Collector module is installed.
- The Staging Area is created.
- Ingest accounts are configured for App Impersonation.
- Workflows have been reviewed.
- Apply the appropriate failed item threshold.
Here are the basic steps to start an EV to O365 migration:
- Enable modules on the Modules screen.
- Select and enable one or more domains for synchronization on the Active Directory screen.
- Add the Enterprise Vault source environment using the EV Environment screen.
- Add source links using the Links screen.
- Add the Staging Area using the Links screen.
- Configure folder-less item handling from the System Configuration screen.
- Create a new Office 365 link and associate necessary modules from the Links screen.
- Set Office 365 credentials. This can be done by either entering Service Account credentials or using OAuth when running the Archive Shuttle Office365 Module Credentials Editor.
- Sync mailboxes from the Office 365 environment using the Links screen.
- Make sure Use EWS for Processing is enabled on the System Configuration > Shortcut Processing screen.
- Consider enabling the option to Disable reminders for appointments in the past using the System Configuration > Office 365 Module screen.
- Map one or more containers from the Map Containers screen.
Here are some general considerations you should take 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 an EV 10.0.3 or earlier system, extraction 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 flavors of Office 365 licenses have different size limits, as described here. It is advised to run SQL Queries on the source environment 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. This article may help.
- Ensure a high level of Mailbox Parallelism and a low level of item/batch parallelism. This gives least chance to hit throttling limits.
- Have 5 accounts configured with application impersonation rights in Office 365. This gives the least chance of hitting throttling limits.