Return
-
Title
Checklist: EV to Office 365 Migration -
Description
Checklist: EV to Office 365 Migration -
Resolution
The following is a checklist comprising questions that should be raised and considered to aid the successful completion of a migration from EV to Office 365. The questions are in no particular order:
Question/Comment Why is this important? Outcome All source Links need to have an Item Database created The Item Database is where item-related metadata is stored along with the export/import progress of each item. It is required to have one database per source link that migration is happening from.
The customer might have some links which are not the source of migration, these do not need an Item Database.All source Links need to have Archive Gathering enabled Without this mappings will not go into Stage 1 All source links need to have modules mapped Without these mappings will get stuck at various points of the Stage 1 or Stage 2 of the migration All target links need to have import modules mapped The Office 365 link needs to have the modules mapped Staging Area should not be virus scanned More information is available in this article. Staging Area should be sized appropriately It is suggested to have approximately 50-100 Gb x number of source links Multiple Office 365 service accounts have been configured. Office 365 currently throttles connections. More information is available in this article. Review all steps in the workflows which will be used to ensure they are appropriate for the migration/customer It is advised to ensure that the workflow steps are correct, before proceeding with the migration, otherwise changes will need to be made later in the project Any default failed item threshold is set per link If there is known data integrity issues affecting the source environment a default failed item threshold can be put on the source links. This will mean that the mappings can proceed through stage 2 more easily, if it is set correctly Staging Area for Source & Target match If the source and target staging areas do not match, then exports or imports will not be able to take place Filter added to handle oversize messages The following article will show items / archives which contain large items.
Office 365 has a hard size limit of 25 Mb per item, there is little point in extracting this out of the source to try to ingest them in to the target.
Article: Finding Items Sizes in Enterprise VaultModules are scheduled appropriately For example the export modules are configured to avoid the source environment backup window (if that is a requirement of the customer). Likewise the import modules are scheduled in order to give least impact on the new environment (again this if the customer requires it) Verify if Top of Information Store handling is required The following article will show items / archives which contain items which were archived at the TOIS (Top of Information Store) in the source environment. If there are archives which have this, then the System Configuration setting for folder-less items need to be configured. If this is not configured some items will not import, and there will be no error.
Article: Handling Folder Less itemsAre source containers going to be deleted at the end of the stage 2 part of the migration? If no, then remove the workflows which contain the Delete Archive command. This will save the wrong workflow being chosen inadvertently.