MX Spooler Service — Avoid NDRs During Microsoft 365 Tenant Migrations
IT Partner’s MX Spooler Service is a managed service for Microsoft 365 tenant-to-tenant migration projects where an email domain is moved between tenants and incoming mail must be held and released to avoid NDRs, bounced emails, and lost incoming messages during the migration process.
What this engagement is
During mergers, acquisitions, or other tenant-to-tenant migration projects, organizations may need to move mailboxes and service settings from one Microsoft 365 tenant to another. When an email domain is moved between tenants, incoming messages can generate NDRs or bounce if mail flow is not handled correctly. IT Partner uses MX Spooler Service to temporarily hold incoming email during the migration, redirect mail flow when needed, and release messages so they are delivered to the client’s tenant.
Success criteria
What you receive
How the work unfolds
Review the tenant-to-tenant migration plan, affected email domains, cutover timing, and the point at which incoming mail must be held.
Provision spooler mail storage for the affected domains and prepare the hold-and-release configuration for the migration window.
Create the required transport rules and connectors in the client's tenant so mail flow can be redirected and later released correctly.
Provide the exact MX record values and coordinate the client's DNS change that points incoming mail to the spooler.
Hold incoming messages in the spooler while the email domain is removed from the source tenant and attached to the target tenant.
Release held messages to the client's tenant once the domain and mail flow are ready, and confirm delivery.
Provide the final MX record values so the client can point mail flow at the target tenant, then verify email flow end to end.
Prerequisites
Who does what
IT Partner
- Set up comprehensive mail storage.
- Create necessary transport rules and connectors inside the client's tenant.
- Provide the required information about the changes to the MX record.
- Check and confirm the email flow works fine.
- Perform necessary steps to redirect the email flow to MX spooler service for temporary email hold.
- Release emails and ensure they are delivered to the client’s tenant.
Your team
- Perform the required MX changes.
- Provide access to DNS management system if necessary.
What's not included
Limitations & technical notes
Frequently asked questions
What is IT Partner’s MX Spooler Service?
IT Partner’s MX Spooler Service is a managed service for Microsoft 365 tenant-to-tenant migration projects where an email domain is moved between tenants. It temporarily holds incoming email, redirects mail flow when needed, and releases messages to the client’s tenant to help avoid NDRs, bounced emails, and lost incoming messages during the migration process.
When should we use the MX Spooler Service?
You should use the MX Spooler Service when a Microsoft 365 email domain is being moved between tenants and incoming mail flow may be interrupted during cutover. This commonly applies to mergers, acquisitions, divestitures, or other tenant-to-tenant migration projects where mailboxes and service settings are being moved.
What is included in IT Partner’s MX Spooler Service?
IT Partner’s MX Spooler Service includes comprehensive mail storage setup for the migration process, required transport rules and connectors inside the client’s tenant, guidance on required MX record changes, mail flow validation, temporary redirection of email to the MX spooler, and release of held emails to the client’s tenant. These deliverables are designed specifically to support mail flow continuity during a Microsoft 365 tenant-to-tenant migration.
Does the service include changing our DNS or MX records for us?
The client is responsible for performing the required MX record changes, because DNS control typically remains with the organization or its DNS provider. IT Partner provides the required information about the MX record changes. If DNS management access is necessary for the agreed work, the client provides that access.
What are the prerequisites for the MX Spooler Service?
The service requires a Microsoft 365 tenant-to-tenant migration project and access to DNS management for all required email domains. These prerequisites are important because the service depends on coordinating domain mail flow and MX record changes during the migration.
How long does the MX Spooler Service last?
IT Partner’s MX Spooler Service has a stated duration of 14 days per project. If a migration scenario requires a different coverage window or special handling, the specifics should be confirmed with IT Partner before the engagement.
How much does the MX Spooler Service cost?
The service is $2,890 per project, quoted fixed-price in writing before work begins — you pay after you approve delivery. The fee covers the stated 14-day engagement; extended spooling or additional migration work is quoted separately.
Will incoming emails be lost during the migration?
The stated success criterion for the service is that no incoming emails are lost during the migration process. The service is designed to support this by using the MX Spooler Service to temporarily hold incoming mail and then release it to the client’s tenant after mail flow is ready.
Will users experience email downtime during the migration?
The service is designed to manage incoming mail flow during the domain transfer, including temporarily holding messages while the migration is in progress. Users may not receive held incoming messages immediately during the hold period, because emails are accumulated in the spooler and released after the cutover steps are completed.
Does the MX Spooler Service migrate mailboxes or tenant data?
The provided service scope is focused on mail flow protection during a Microsoft 365 tenant-to-tenant migration, not on performing the full mailbox or tenant migration itself. A tenant-to-tenant migration project is listed as a prerequisite, so mailbox migration scope should be confirmed separately with IT Partner if needed.
What happens after the held emails are released?
After held emails are released and delivered to the client’s tenant, the implementation plan includes changing MX records back. The client is responsible for performing required MX changes, while IT Partner provides the required MX record change information and checks and confirms that email flow works correctly as part of the engagement deliverables.
Are there any listed out-of-scope items or additional-cost items?
Yes — the service does not include the tenant-to-tenant migration itself (mailbox, OneDrive, SharePoint, or Teams data migration is contracted separately), DNS hosting or registrar management, licensing or third-party service costs, remediation of pre-existing mail flow or DNS issues, spooling beyond the stated 14-day project duration, or end-user communications. Delivery guarantees for external sender behavior and internet DNS propagation timing are also excluded because those factors are outside IT Partner's direct control.