Quest is excited to release a new mail sync feature within On Demand Migration that synchronizes mailbox changes from source to target.
This new feature allows migration operators to sync the full mailbox with every migration task to keep source and target synchronized.
- Replicates content changes, moves, and deletions from source to target during each migration task
- Removes the need to filter contents by date during initial migration tasks
- Avoids creating duplicate contents in the target mailbox
- Ensures migrated mailbox matches original mailbox to reduce user impact and keep users productive
What types of changes are synchronized?
On Demand Migration will synchronize the following changes for both the primary mailbox and the archive mailbox.
Messages
- Updates message in target if changed in source, including changes to drafts
- Moves message to different folder in target if moved in source
- Deletes message in target if deleted in source
Folders and Subfolders
- Updates folder and subfolder names in target if renamed in source
- Moves folder to different location in target if moved in source
- Deletes folder in target if deleted in source
Calendars
- Updates calendar entries in target if changed in source
- Deletes calendar item in target if deleted in source
Note: For Contacts and Tasks - If these items are deleted in the source, they will not be deleted on the target.
What is an example mail sync scenario?
Let's imagine that a migration operator performs an initial mail migration task for the following mailbox. On Demand Migration will copy the mailbox contents from source to target.
Initial Migration Task
Source mailbox changes
After the initial mail migration, the user continues working out of their source mailbox. They receive new messages, they mark messages as read, they file messages into folders, they delete some messages, and they delete a personal folder.
Subsequent migration task, without Mail Sync (old behavior)
Without Mail Sync, when the migration operator submits another mail migration task for the mailbox, the task creates duplicate copies in the target mailbox for content that was moved or deleted in the source. This duplication can result in possible mailbox quota issues in the target.
Subsequent migration task, with Mail Sync (new behavior)
With the new Mail Sync feature, the second migration task in this example will synchronize all source changes to the target without creating duplicates.
Why are we introducing this change?
When migrating a mailbox from one tenant to another, users expect their migrated mailbox to look the same as their original mailbox. Since users are constantly updating their active mailbox, this means that contents can change frequently in between migration tasks.
Without Mail Sync, users can end up with outdated and duplicated content in the target when multiple migrations are performed, requiring the users to perform post-migration review and cleanup.
How do I enable mail sync in my project?
You do not need to take any action to enable mail sync. Once mail sync is deployed to your On Demand region, all future mail migration tasks will automatically use the mail sync feature. Existing mail migration tasks will not be impacted and will complete their processing using the previous configuration.
Further information
For more information on this and many other features within On Demand Migration, check out the On Demand Migration User Guide or visit us at Quest.com. We welcome comments and questions, as your feedback helps to improve our products and make them work better for you.
