An Exchange Public Folder migration is not complete simply because the migration job reports that data has been copied. Before cutover, IT teams need to verify that the destination contains the expected folders, messages, permissions, mail-enabled objects and other important data.
A structured validation process gives administrators an opportunity to identify discrepancies while the source environment is still available. It also reduces the risk of discovering missing content after users have already been moved to the destination.
What Should You Validate Before Cutover?
A useful validation process should cover five areas:
- Folder hierarchy
- Item counts and content
- Permissions
- Mail-enabled Public Folders
- User access and functionality
The goal is not necessarily to compare every individual item manually. Instead, establish measurable checks that demonstrate that the migration is behaving as expected.
1. Compare the Public Folder Hierarchy
Start by comparing the source and destination folder structures. A Public Folder Analyzer can help you capture this baseline before migration begins, giving you a clear record to compare against post-migration.
Check:
- Root folders
- Child folders
- Nested folder depth
- Folder names
- Number of folders
- Special folders
- Calendar and contact folders
Microsoft explains that the Public Folder hierarchy contains organizational information such as the folder tree and permissions.
2. Validate Content
Compare representative folders and high-value repositories.
Look for:
- Message counts
- Calendar items
- Contacts
- Attachments
- Recent content
- Older historical content
- Folder sizes
Do not validate only the largest folders. A small folder containing critical business information can be more important than a large archive.
3. Validate Permissions
Permissions should be checked against the source environment.
Confirm:
- Owners
- Publishing editors
- Editors
- Reviewers
- Custom permissions
- Inherited permissions
- Restricted folders
Microsoft documents Public Folder permissions through Exchange administration and PowerShell.
4. Test Mail Flow
For mail-enabled Public Folders, send test messages to the relevant SMTP addresses.
Confirm:
- The address resolves correctly.
- Messages reach the correct folder.
- Internal users can send messages.
- External delivery works if required.
- Reply behavior is correct.
Mail-enabled Public Folders have additional email properties and settings that should be validated separately.
5. Test Real User Access
Technical validation is not enough.
Select representative users and verify that they can:
- Open Public Folders
- Read content
- Create items where permitted
- Edit items where permitted
- Access restricted folders
- Send mail to mail-enabled folders
Final Pre-Cutover Checklist
Before cutover, document:
- Source folder count
- Destination folder count
- Content validation results
- Permission validation results
- Mail-flow results
- Known exceptions
- User acceptance results
- Final synchronization status
A documented validation record gives the migration team evidence that the environment was tested rather than relying solely on a migration status screen.
FAQs
Q1. How do I know whether a Public Folder migration was successful?
Compare hierarchy, content, permissions, mail-enabled objects and user access between the source and destination.
Q2. Should I validate Public Folder permissions before cutover?
Yes. Incorrect permissions can create access problems immediately after users are switched to the destination.
Q3. Should mail-enabled Public Folders be tested separately?
Yes. Mail flow and SMTP-related properties require specific testing.
