6.2. Delta Migrations
Any modifications to source items after discovery has completed will not be captured unless Discovery is run again. A Delta Discovery/Deta Migration is the term used for additional ‘top up/incremental’ migrations after the main migration have occurred and may be required when the source system is still active and there is a period between completion of the migration and switch over to the new target.
For example, a migration may take 1 week to run and during that time users are still actively altering the source and so these new documents and edits need to be detected and migrated before switching over.
A Delta discovery run will typically take longer than the original discovery due to the need to gather all information and compare discovery results.
To start a Delta run, select the Discovery option on the Migration Dashboard and select the Start Incremental Discovery from the Discovery screen.
The steps for a Delta migration are the same as for the initial migration.
Discovery will identify new/changed/deleted items and pre-check should be run in case any new data fails these checks. In most cases it may simply require a ‘review’ of the existing settings to review structure mapping, content types and security information.
Finally run the Data Migration and if relevant the Shortcut Links Migration
The table below explains the different delta scenarios and expected results.
Note: It is not recommended to move or rename or reparent folders and files while migration is underway, as it could lead to lots of duplicate content in target and it will consume additional license utilization.
Delta Scenario | Expected Result |
New Folder is added |
|
Folder is modified/renamed |
|
Folder is moved/re-parented to different location |
|
Folder is deleted |
|
New File is added |
|
File is modified |
|
File is renamed |
|
File is moved/re-parented to different location |
|
File is deleted |
|
New version is created |
|
Version is deleted |
|
Comments