A cloud email and file migration can move messages and documents successfully while still leaving people unable to open the shared resources they rely on. The risk is easy to miss: mailbox delegation, group membership, folder exceptions, and guest access are separate pieces that may not carry over in the same way between platforms.
The safest approach is to treat access as part of the migration, not as a cleanup task afterward. Inventory permissions, map identities, test a representative pilot, and verify everyday work before and after cutover. The exact steps depend on the source, destination, and migration tools, so confirm platform-specific behavior in the relevant documentation.
Start with a permissions inventory
Before transferring data, record who uses each shared mailbox, folder, and shared drive, and what they are allowed to do. Include access that is easy to overlook, such as a person who can send from a shared mailbox, a folder shared with an outside partner, or an exception that grants access to only one subfolder.
- Shared mailboxes: List the people who can open each mailbox and those who can send as it or on behalf of it. These are distinct permissions and should be checked separately.
- Files and folders: Identify owners, groups, inherited access, folder-level exceptions, and any explicit restrictions. Record the location of the data as well as the people who need it.
- External users: Note guests, partner organizations, and shared links. A link that works in the current environment may need to be recreated, or the guest may need to accept a new invitation in the destination.
- Business-critical resources: Mark shared inboxes and folders that support daily work, customer communication, or important operational processes so you can include them in early tests.
This inventory is the working record for the migration. It also gives your team a way to distinguish intentional access from old permissions that should not be carried forward.
Map identities before applying permissions
Identity mapping connects each source account or group to its intended destination identity. Make sure the destination users and groups exist, are named consistently, and are assigned to the right people before you apply access to migrated mailboxes or files. If a source group has no clear counterpart, decide who should own that access rather than assuming the migration tool will resolve it correctly.
Keep a record of changes to names, email addresses, groups, and ownership. Then compare the destination setup with your inventory. This matters because a file permission attached to an identity that is missing or mapped incorrectly may not provide the intended person with access.
Do not treat a successful data copy as proof that permissions transferred. Microsoft’s guidance for moving file shares to OneDrive, Teams, and SharePoint describes a platform-specific migration process. Review the documentation for your own source, destination, and tools to understand what can be retained and what needs separate attention.
Plan mailbox access separately from messages
For every shared mailbox, verify both the mailbox contents and the delegates’ permissions. Include the ability to open the mailbox, send as the shared address, and send on behalf of it where those functions are used. If there are rules, forwarding settings, or other mailbox behaviors your team depends on, include them in the inventory and confirm how they will be handled in the destination.
For a move between Microsoft 365 tenants, consult the relevant cross-tenant mailbox migration guidance. The details differ by migration scenario, so avoid assuming one platform’s process or permission model applies everywhere.
Use a pilot before the full move
A pilot lets you test the process with a representative set of users and shared resources before the larger cutover. Choose a mix that reflects how your organization works: an individual mailbox, a shared mailbox with delegates, a commonly used shared folder, and a resource with guest access or unusual permissions.
Ask pilot users to perform real tasks rather than simply confirm that they can sign in. Have them open and search for expected mail, access shared folders, edit a document where appropriate, and use delegated mailbox functions. Record what works, what fails, and how each issue was resolved. Update the migration plan before moving additional users.
A staged or incremental transfer may help limit the amount of work left for the final move, depending on the tools and platforms involved. Establish which environment is authoritative during each stage. If people edit files in two locations at once, changes can diverge and need to be reconciled.
Set a clear cutover and communication plan
Before cutover, tell users what is changing, when to use the destination, and where to report access problems. Identify who can approve permission changes and who will handle troubleshooting. Agree on how to handle edits or messages that arrive during the transition, and verify the email-routing steps for your chosen platform and migration method.
At cutover, follow the documented sequence for the environment rather than relying on a generic checklist. Confirm that users can reach the new mailboxes and files, and communicate when they should stop using the old locations. A cloud migration preparation plan can help coordinate technical work with the people who depend on those systems.
Verify access after migration
Use a simple test matrix that names the resource, the user or group testing it, the expected permission, and the result. Include at least the following checks:
- Open each important shared mailbox and confirm the expected messages are present.
- Send a test message from the shared address and, where applicable, on behalf of it.
- Open key shared folders and files with users who have different access roles.
- Check that inherited permissions and folder-level exceptions behave as intended.
- Test guest access and any external sharing links that the business still needs.
- Confirm users know which platform to use and where to ask for help.
Test with the actual accounts that need access, not only an administrator account. Administrators may have broader privileges than the people who use the resources day to day. If a test fails, compare the destination permission with the original inventory, correct the identity or access assignment, and test again.
Keep the inventory, decisions, and test results together with the migration records. This makes it easier to resolve questions later and review whether access still matches business needs. For teams handling sensitive information, it can also help to review broader practices for protecting business data.
Frequently asked questions
Will file and folder permissions transfer automatically?
Not necessarily. The result depends on the source and destination platforms, identity mapping, migration tool, and its settings. Check the tool’s documentation, then validate access with the destination accounts that need it.
How do I move a shared mailbox without losing delegate access?
Record delegates and their specific rights before the move, including mailbox access and sending permissions. Map each delegate to the correct destination identity, apply or confirm the permissions, and test the mailbox using those users.
What happens to external sharing links and guest access?
Do not assume existing links or invitations will continue to work. List the external users and resources they need, then test whether access works in the new environment. Recreate links or invitations when required by the destination platform.
How can email keep flowing during a phased migration?
Plan the routing and timing for your specific platform and migration method. Define which system is authoritative at each stage, communicate the change to users, and confirm mail flow during testing and cutover.
What should we test after cutover?
Check mailbox access and delegated sending, shared file access for users with different roles, folder exceptions, guest access, and the expected destination for new work. Record results and resolve failed checks before treating the move as complete.
Make access part of the migration plan
A reliable cloud email and file migration accounts for identities, permissions, mail flow, and user habits, not just copied data. Build the inventory, pilot the process, and verify access with the people who rely on each resource. Zevonix provides cloud services and migration support for organizations planning IT changes. To discuss your migration needs, call (904) 658-0777.