Public Folder permissions are often more complicated than they initially appear. A large organization may have hundreds of folders with different owners, editors, reviewers and custom access levels.
Moving the data without correctly preserving the access model can create a serious operational problem, especially during a large-scale public folder migration.
Why Public Folder Permissions Matter
Permissions determine who can:
- Read content
- Create items
- Edit content
- Delete content
- Manage folders
- Access restricted information
Microsoft documents Public Folder permissions through Exchange administration and PowerShell, including predefined and custom permission levels.
Create a Permission Baseline
Before migration, use a public folder analyzer to export or document the permission structure.
Capture:
- Folder path
- User or group
- Permission level
- Custom rights
- Inheritance behavior
- Folder owner
- Restricted folders
This gives administrators something to compare against after migration.
Watch for Custom Permissions
Predefined roles are easier to validate than custom configurations.
A folder may have a customized permission set that does not map neatly to a standard role.
These folders deserve additional review.
Validate the Destination
After data is copied using a reliable public folder migration tool, test representative accounts..
For example:
User A: Read-only
User B: Contributor
User C: Folder owner
User D: No access
Testing different roles is more reliable than testing only an administrator account.
Don’t Assume Administrator Access Proves Success
Administrators often have broad permissions that ordinary users do not.
A migration can appear perfect when tested by an administrator while ordinary users experience:
- Access denied errors
- Missing folders
- Inability to create items
- Inability to edit content
Document Exceptions
If certain permissions cannot be mapped exactly, record them before cutover.
For every exception, document:
- Original permission
- New permission
- Reason
- Business owner
- Required remediation
This prevents undocumented permission changes from becoming post-migration incidents.
FAQs
Can Public Folder permissions be migrated automatically?
Migration capabilities depend on the source, destination and migration method. Permissions should always be validated rather than assumed.
What permissions should be tested?
At minimum, test read-only, contributor/editor and owner-level access.
Why are custom permissions risky?
They may not map cleanly to standard roles and can be overlooked during validation.
