Blogs

How to Perform Incremental Sync During an Exchange Public Folder Migration

How to Perform Incremental Sync During an Exchange Public Folder Migration

Large Public Folder migrations rarely happen in a single uninterrupted copy operation. Incremental synchronization allows migration teams to copy data while the source environment remains active and then synchronize changes before cutover

Microsoft’s migration documentation describes final synchronization as part of the Exchange Online Public Folder migration process.

What Is Incremental Synchronization?

An incremental sync identifies changes made after an earlier migration pass and copies those changes to the destination.

This reduces the amount of data that must be transferred during the final cutover.

Why Incremental Sync Matters

Without incremental synchronization, teams may need to perform a much larger final migration window.

Incremental processes can help reduce:

  • Downtime
  • Repeated data transfers
  • User disruption
  • Cutover pressure

Recommended Workflow

Phase 1 — Assess
Inventory the source environment.

Phase 2 — Initial copy
Move the majority of the data.

Phase 3 — Validate
Check the destination.

Phase 4 — Incremental synchronization
Copy changes made since the initial migration.

Phase 5 — Lock or restrict source changes
Prepare the source for final cutover.

Phase 6 — Final synchronization
Copy the final changes.

Phase 7 — Validate destination
Confirm the destination is ready for users.

Monitor the Final Sync

Do not start cutover simply because the batch appears to be progressing.

Review:

  • Failed items
  • Migration reports
  • Mail-enabled folders
  • Data discrepancies
  • Permission exceptions
  • Remaining changes

Microsoft notes that final synchronization occurs during the completion stage of its Public Folder migration process. If you’d rather have this monitored for you, our team can walk through the workflow with you.

FAQs

What is incremental synchronization?
It is the process of copying changes made after an earlier migration pass.

Why use incremental sync?
It can reduce the amount of data and change activity required during final cutover.

Is incremental synchronization the same as backup?
No. Synchronization moves changes between environments, backup is designed for recovery and data protection.