Public Folder contact repositories can become critical business resources over time. Sales teams, support departments and shared-service teams may rely on them as organizational address books.
Moving the folders without validating the contact data can create operational gaps — Public Folder Migrator moves contacts, calendars, and permissions together, but each still needs its own validation pass.
Inventory Contact Folders
Before migration, identify:
- Contact folder paths
- Number of contacts
- Business owners
- Permissions
- Frequently used contact folders
- Duplicate or obsolete folders
Clean Before You Move
Migration is an opportunity to identify:
- Duplicate contacts
- Outdated records
- Empty folders
- Obsolete departments
- Incorrect information
Not every piece of historical data necessarily needs to be moved.
Validate Contact Data
After migration, sample records and compare:
- Contact names
- Email addresses
- Phone numbers
- Company names
- Notes
- Additional fields
Test Access
Use representative accounts and check permissions to confirm that users can access the contact folders they previously used.
Protect Business-Critical Contacts
Some Public Folder contacts may be used by:
- Sales teams
- Customer support
- Procurement
- Operations
- Shared-service teams
Prioritize these repositories during validation.
Create a Migration Sign-Off
For each important contact folder, record:
- Source location
- Destination location
- Item count
- Validation status
- Business owner approval
This creates an auditable record of the migration, get started with our team if you want this sign-off process handled for you.
FAQs
Can Public Folder contacts be migrated between Exchange environments?
The available migration path depends on the source, destination and migration technology used.
Should old contacts be migrated?
Not automatically. Review business value and retention requirements first.
How should contact migration be validated?
Compare representative records, item counts, folder structure and user access.
