Cutover Email Migration — Single-Event Move to Microsoft 365 or Exchange Online

IT Partner’s Cutover email migration service moves an organization from an existing email system to a new target email system in a single, well-defined cutover event. It includes assessing the current environment, preparing the migration, migrating user email data, and testing that the target email system functions as expected.

This service can support migration from Microsoft Exchange, Google Workspace, IBM Notes, or another email platform or provider. The exact approach depends on the source system, target system, and current email environment, so IT Partner assesses the existing system before migration.

The service is aligned with Exchange Online, Microsoft 365, and Office 365 migration scenarios. A Microsoft 365 or Exchange Server environment is listed as a prerequisite, so the target environment should be confirmed with IT Partner before the engagement begins.

The service is intended to migrate user mailboxes, email messages, folders, contacts, calendars, and other relevant email data. IT Partner also verifies that migrated data retains original formatting, metadata, and permissions where applicable and is accessible by the appropriate users.

Included deliverables are assessment of the current email system, requirements review for the new system, security settings configuration, distribution lists, necessary integrations, data prioritization, source data backup, user data migration, and post-migration email functionality testing. These items are included because the service is designed to complete a controlled cutover from the old email system to the new one.

Informing users about upcoming changes is not provided by the project; the client remains responsible for informing users about upcoming changes and providing the necessary information unless a separate service is agreed. Customer team training is not included and can be added as an additional service if needed.

The listed service duration is 7 days. The actual cutover is typically performed over a short period, such as a few hours or days, because cutover migration is a definitive switch from the old email system to the new one.

The listed price is $500 plus $50 per mailbox. Because pricing is mailbox-based after the base fee, the total cost depends on the number of mailboxes included in the migration scope.

Cutover email migration is best suited for smaller to medium-sized organizations with relatively simpler email environments. Larger organizations, complex mail systems, or environments with significant data volume may require staged or hybrid migration methods instead, because those approaches can reduce business disruption in more complex scenarios.

The engagement includes a kickoff meeting, assessment of the source and target systems, provisioning of required infrastructure, source data cleanup and optimization, migration execution, DNS configuration if needed, verification of migrated data, and follow-up or closure conversations. This sequence is used to prepare the environment, perform the cutover, and validate that the new email system is functioning correctly.

A cutover migration involves a definitive switch from the old system to the new system, so some business impact is possible during the cutover window. The service description does not specify a guaranteed downtime duration, so the expected timing and user impact should be confirmed with IT Partner based on the source system, target system, and DNS plan.

Mail flow is handled by configuring the necessary MX records and DNS settings so incoming emails route correctly to the target system. One of the success criteria is that all incoming emails are routed correctly to the target email system after migration.

The client is responsible for performing required internal and external DNS changes, while the project plan also includes configuring DNS settings if needed during migration execution. Because DNS ownership often depends on customer access and domain management, responsibilities should be aligned during kickoff.

IT Partner assesses the current email system, identifies requirements for the new system, configures security settings and distribution lists, identifies and prioritizes migration data, backs up source data, migrates user data, and tests email functionality. These responsibilities are part of the defined scope for completing the cutover migration.

The client must provide a dedicated point of contact, coordinate any outside vendor resources, provide temporary access to the existing environment or IT infrastructure, configure network equipment, perform DNS changes as required, and inform users about upcoming changes. These responsibilities are important because IT Partner needs access, coordination, and customer-side infrastructure changes to complete the migration.

Prerequisites include having a Microsoft 365 or Exchange Server environment, identifying any needed infrastructure upgrades or modifications, and configuring the necessary MX records for proper mail routing. These items help ensure the target environment is ready for the cutover and that email can route correctly after the switch.

Yes, the service includes backing up source system data to help ensure its safety and provide a contingency plan. The backup is part of the migration preparation deliverables, but any specific backup retention or restore procedures should be confirmed with IT Partner.

IT Partner verifies that data has been migrated correctly, including metadata and permissions, and tests email functionality in the new system. The stated success criteria are successful data migration, correct incoming mail routing to the target system, and access to migrated data by the appropriate users.

After migration, IT Partner performs verification and conducts follow-up or closure conversations. The service does not define ongoing managed support or user training after completion, so any post-migration support needs should be discussed as an additional scope item.