Migrations
Plan the move for your email,
files, tenants or servers.
Choose the work you need, from Microsoft 365 and specialist content migrations to server migration planning. Each path defines the work, the checks and what your team receives.
Not sure which path? Describe the moveWhat needs to move?
Each path has its own scope. A project can combine several.
Email migration
Move the mail. Check that people can use it.
Move the agreed user and shared mailboxes, coordinate the email switchover, and check sign-in and mail flow before handover.
Illustrative migration path
- User mailboxes
- Shared mailboxes
- Mail routing
What AZ does
Inventory mailboxes and the data included in the move.
Test a pilot, run the agreed batches and coordinate mail routing.
Check the destination, user access and incoming and outgoing mail.
Start with the source, destination and deadline. Scope and fees are agreed before work begins.
The handover you receive
- Mailbox and destination list
- Cutover and test records
- Exceptions and handover instructions
What we need to scope
- Source platform, mailbox count and data volume
- Archives, shared mailboxes and holds
- Domains, mail routing and the change window
Archives, public folders and a full tenant move have different scopes. Include those requirements before the quote is agreed.
More than one path?
Scope the whole move before committing to a date.
Archives, public folders, hybrid systems, holds or unclear ownership can change the sequence. We first confirm whether the move can be scoped directly or needs a separate planning engagement.
See the migration planning engagementPlanning produces
- A source and destination inventory
- Dependencies, migration groups and stop conditions
- Acceptance checks and a basis for the implementation quote
The plan is a deliverable. Execution is agreed separately.
Related delivered work
A move needs more than a success message.
See how sync and file-path problems were investigated after a SharePoint move. The handover included a system guide, file comparisons and unresolved issues. Some exceptions remained.
See the project detailsOther types of move
Moving collaboration platforms?
These have their own dependencies and destinations. Review the additional routes before including them in a Microsoft 365 move.
Explore collaboration migration coverageHow access, checks and handover are agreed