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. 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.

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.

The MX Spooler Service helps prevent incoming messages from bouncing or generating non-delivery reports when an email domain is in transition between Microsoft 365 tenants. It does this by redirecting mail flow to a temporary spooler, holding messages during the critical migration window, and then releasing them to the client’s tenant.

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.

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.

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.

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.

The listed price for IT Partner’s MX Spooler Service is $2890,00 per project. The service SKU is ITPWW530MIGOT.

IT Partner analyzes the migration plan, configures the MX Spooler Service, prepares the source tenant to work with the spooler, provides required information for MX record changes, temporarily stops or redirects mail flow during domain transfer, releases held emails, and supports the process of changing MX records back. The goal is to control incoming mail flow during the migration so messages are not lost while the domain is being moved.

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.

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.

Emails that arrive during the affected migration window are redirected to the MX Spooler Service for temporary holding. After the target mail flow is ready, IT Partner releases the held emails so they are delivered to the client’s tenant.

IT Partner is responsible for creating the necessary transport rules and connectors inside the client’s tenant as part of the service scope. These configurations support controlled mail flow redirection and delivery during the Microsoft 365 tenant-to-tenant migration.

The client is responsible for performing the required MX record changes and providing access to the DNS management system if necessary. This client involvement is required because MX records control where incoming email for the domain is delivered.

IT Partner is responsible for setting up comprehensive mail storage, creating required transport rules and connectors, providing MX record change information, checking and confirming mail flow, redirecting email to the MX spooler for temporary holding, and releasing messages to the client’s tenant. These tasks are the core technical scope of the MX Spooler Service.

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.

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.

The source service description does not list specific out-of-scope items or additional-cost items. If you need confirmation about related activities such as broader migration work, DNS administration, or extended service duration, you should confirm those details with IT Partner before purchase.

The listed manager for IT Partner’s MX Spooler Service is Roman Sotnik. The service is sold as a managed project service under SKU ITPWW530MIGOT.