Cutover is the point where the destination becomes the production environment. It is one of the most important stages of an Exchange Public Folder migration cutover because mistakes can immediately affect users.
Before Cutover
Complete this pre-cutover checklist:
- Final validation
- Permission checks
- Mail-flow testing
- Calendar tests
- Contact validation
- User acceptance
- Backup or rollback planning
- Stakeholder communication
Freeze Changes
The final migration phase requires control over changes in the source environment.
Users should know:
- When changes stop
- When access may be temporarily unavailable
- When the destination becomes authoritative
Perform Final Synchronization
The final sync should capture changes made since the previous migration pass, keeping the Exchange Online Public Folder migration as close to zero-downtime as possible.
Microsoft’s current migration guidance includes a final synchronization during the completion stage.
Test Before Opening Access
Do not immediately announce that migration is complete.
First test:
- Public Folder access
- Permissions
- Mail delivery
- Important folders
- Calendar content
- Contact content
Communicate Clearly
A good cutover message tells users:
- When the change happens
- What they need to do
- Where to access Public Folders
- What behavior has changed
- Who to contact for issues
If you’d rather not draft this yourself, our team can help plan the cutover communication with you.
Prepare for Rollback
A documented rollback plan should exist before the migration begins.
Microsoft documents that rolling back a Public Folder migration can result in loss of content added to the Exchange Online Public Folders after migration unless that content is preserved separately.
That makes rollback planning especially important.
FAQs
How long does Public Folder cutover take?
It depends on environment size, migration method and validation requirements.
Should users be notified before cutover?
Yes. Communication reduces confusion and helps support teams prepare.
Should rollback be planned?
Yes. A rollback strategy should be documented before production cutover.
