Staged Office 365 Migration
A staged Office 365 migration moves mailbox data in planned phases instead of transferring everything in one migration window. With EdbMails, administrators can use date filters, mailbox selection, mapping, and repeat migration passes to move part of the data first and complete the remaining transfer around the planned cutover.
This approach is useful when mailbox volumes, network capacity, or the available cutover window make a single-pass migration difficult. The migration plan can prioritize recent data first for users who need current items immediately, or move older data in advance so that less data remains for the final pass.
EdbMails provides these staged migration options as part of its Office 365 Migration Tool.
What Staged Office 365 Migration Means in EdbMails
On this page, staged migration refers to an EdbMails multi-pass migration strategy for Microsoft 365 mailbox data. It should not be confused with Microsoft's native staged Exchange migration method, which is a separate legacy migration approach documented for specific older Exchange Server environments.
In EdbMails, administrators can divide the migration by date range, mailbox, folder, or other supported filters, run an initial pass, review the migration results, and then complete the remaining data in subsequent passes.
Staged vs. Cutover Migration
Cutover migration moves the planned mailbox data within one migration window. A staged migration divides the transfer into multiple passes so that part of the data can be moved before the final cutover. The suitable approach depends on mailbox volume, network conditions, the available migration window, and how the organization plans to transition users.
If your organization can complete the required transfer within a single migration window, see Cutover Office 365 Migration. For larger data sets or tighter cutover windows, a phased approach can reduce the amount of data left for the final migration pass.
First Migration Phase:
In the first phase, administrators can migrate data older or newer than a selected date, depending on the migration plan. This pass is often scheduled before the final cutover so that a substantial portion of mailbox data is already present in the target environment.
Final Migration Phase:
After the initial pass is reviewed, the remaining mailbox data can be migrated in one or more subsequent passes. This helps reduce the amount of data that must be transferred during the final cutover window. Users can then begin working in the target environment according to the organization's cutover plan while administrators verify the remaining migration results.
Is Staged Migration Right for You?
Not every migration needs to be split into phases. Staged migration makes the most sense when data volume, downtime tolerance, or connectivity constraints make a single-pass migration impractical. The table below offers a quick way to check if your situation matches, before reading through the full scenarios that follow.
Your situation Why staged migration fits Operating continuously with a large volume of data Allows selected data to be moved first, reducing the volume left for the final cutover Merging with another company's Office 365 environment Allows a large portion of mailbox data to be moved before the planned consolidation date Working with slow or unreliable internet connectivity Splits the transfer into smaller phases so each pass can be monitored and validated Staged Migration Scenarios
- Phased migration for a busy organization:
An organization with a large mailbox estate may choose to migrate selected recent data first so users have access to current messages after cutover. Older mailbox data can be moved in an earlier or later pass, depending on the migration plan. EdbMails date filters, mailbox selection, and folder filters help administrators define what is included in each stage.
- Company merger or tenant consolidation:
When two Microsoft 365 environments are being consolidated, administrators can move a large portion of mailbox data before the planned transition date and then run a later pass for remaining or newly changed items. For a complete consolidation workflow, see the Office 365 Tenant to Tenant Migration guide.
- Migration over limited network bandwidth:
Where bandwidth is limited, splitting the migration into smaller passes can make the workload easier to manage. Administrators can migrate a defined date range first, review the migration logs, and then continue with the remaining data in later passes instead of relying on one long transfer window.
- Phased migration for a busy organization:
Steps to perform staged migration using EdbMails
Step 1: Download and Install EdbMails
- DownloadEdbMailsSetup.exe and complete the installation.
- Launch the application and click ‘Login’ or ‘Start Your Free Trial’.
- Ensure your EdbMails system requirements for Office 365 migration.
Step 2: Select migration option
- Select ‘Office 365 Migration’ from the dashboard.
- Choose ‘Office 365 to Office 365 Migration’.
- Optionally, set a custom job name for the migration task.
Step 3: Connect to source Office 365 server
- Click ‘Add New Connection’ to set up a new connection to the source tenant. If a connection was previously established, you can select it from the list and click ‘Connect to Existing’ to continue.
- Use OAuth 2.0 modern authentication to connect the configured Microsoft 365 source tenant.
- Load source mailboxes manually or import them using a CSV file.
- Select the mailboxes you wish to migrate and click ‘Next’.
Step 4: Connect to target Office 365 server
- Click ‘Add New Connection’ to configure the destination tenant. To reuse an existing connection, select it from the list and click ‘Connect to Existing’ to move forward.
- Authenticate the target tenant using the configured Microsoft 365 modern authentication connection.
- Load the target mailboxes or use a CSV file for bulk import.
- Click ‘Add New Connection’ to configure the destination tenant. To reuse an existing connection, select it from the list and click ‘Connect to Existing’ to move forward.
Step 5: Source and target servers mapping
- EdbMails performs automatic mapping of source and target mailboxes.
- You can also map mailboxes and folders manually for granular control.
- Use the 'Include Filter' option to define the date range for each migration stage. You can move older data in advance to reduce the final cutover workload, or migrate recent data first when users need current mailbox items available in the target environment.
- If you prefer to exclude certain folders from the first stage, click on the ‘Exclude Standard / Custom folders’ button and specify the folders you wish to exclude.
Step 6: Start the Office 365 migration
- Click ‘Start Migration’ to begin transferring the data.
- Monitor the migration progress and use the ‘View Logs’ option to review the migration report. Before starting the next stage, check the completed, skipped, and failed items and address any issues that require attention.
Validate Before the Final Migration Pass
Before the final migration pass, review the migration report and confirm that the expected mailboxes, folders, and date ranges were processed in the earlier stage. Check any skipped or failed items, verify mailbox mapping, and confirm that the target mailboxes contain the expected data.
Run the next migration pass with the same source and target mapping so that remaining or newly available items can be transferred according to the configured filters. Complete the final cutover only after the migration results have been reviewed and the target environment is ready for users.
Post migration steps
Step 1: Complete the planned mail-flow and DNS cutover
MX, Autodiscover, and other DNS changes depend on the migration topology and the domain transition plan. Make these changes only when the target tenant is ready to receive mail and after confirming the required domain configuration. Microsoft provides guidance for creating Microsoft 365 DNS records and configuring Autodiscover.
Step 2: Validate migrated mailboxes and mail flow
Review the EdbMails migration report, verify a representative set of migrated mailboxes, and test inbound and outbound mail after the cutover. Confirm that mailbox folders and recent items are available as expected before closing the migration project.
Step 3: Update Outlook profiles where required
- Keep supported Outlook versions updated before users connect to the target Microsoft 365 environment.
- If Outlook does not connect correctly after the tenant or domain change, create a new Outlook profile and allow Autodiscover to configure the account.
- Send test messages from selected accounts to confirm that sending and receiving work as expected.
Step 4: Decommission source resources only after validation
Do not remove source licenses, subscriptions, or domains immediately after the data transfer. First confirm migrated data, mail flow, DNS changes, user access, and any remaining source dependencies. Decommission the source environment only according to the organization's migration plan and retention requirements.
Frequently asked questions:
What is a staged Office 365 migration?
In EdbMails, staged migration means moving Microsoft 365 mailbox data in two or more planned passes. Administrators can use date filters, mailbox selection, and folder filters to control what is migrated in each stage.
How is staged migration different from cutover migration?
Cutover migration completes the planned transfer within one migration window, while staged migration divides the transfer into multiple passes. The suitable approach depends on data volume, network capacity, and the available cutover window.
Can I migrate recent data first?
Yes. EdbMails date filters can be used to migrate recent data first or to move older data in advance, depending on how the migration is planned.
What should I check before the final migration pass?
Review migration reports, confirm mailbox mapping, check skipped or failed items, and verify that the expected data is available in the target mailboxes before completing the final cutover.
