Migrate from Exchange Server 2016, 2019 to Exchange SE

Summary – Microsoft’s release of Exchange Server Subscription Edition (Exchange SE) marks a significant shift in the lifecycle, licensing, and servicing model of on-premises Exchange Server. With Exchange Server 2016 and 2019 reaching the end of support on October 14, 2025, organizations must migrate to Exchange SE to remain secure, supported, and compliant.

This blog provides a complete, step-by-step guide to migrating from Exchange Server 2016 or Exchange Server 2019 to Exchange SE. It covers supported upgrade paths, prerequisites, migration steps, common challenges, best practices, and how tools like the Shoviv Exchange Migration Tool can simplify complex migrations while minimizing downtime.

What is Exchange Server SE?

Exchange Server SE (Subscription Edition) is Microsoft’s latest on-premises Exchange Server release, introduced on July 1, 2025. Unlike earlier versions that followed a perpetual licensing model, Exchange SE uses a subscription-based licensing approach and follows Microsoft’s Modern Lifecycle Policy.

Key Highlights of Exchange Server SE:-

  • Subscription-based licensing instead of a one-time purchase
  • Continuous cumulative updates (no major version release)
  • Faster delivery of security patches and feature improvements
  • Long-term alignment with Microsoft 365 and hybrid deployments
  • No fixed end-of-support date (as long as CUs are kept up to date)

Microsoft has clearly stated that Exchange 2016 / 2019 will not receive extended support, making Exchange Server SE migration a necessity, not an option.

Why Migrate from Exchange Server 2016/2019 to Exchange SE?

Migrating to Exchange SE is essential for business continuity and security.

  • End of Support for Legacy Versions – After October 14, 2025, Exchange 2016 and 2019 will no longer receive security updates, leaving organizations exposed to serious risks.
  • Improved Security & Compliance – Exchange SE enables faster patching and modern security standards to counter evolving cyber threats.
  • Modern Lifecycle Management – No more disruptive major upgrades—Exchange SE receives continuous updates.
  • Hybrid & Microsoft 365 Readiness – Exchange SE integrates seamlessly with Microsoft 365 and Hybrid environments.
  • Future-Proof Infrastructure – Migrating now ensures long-term compatibility with Microsoft’s roadmap.

Supported Upgrade Paths to Exchange Server SE

Understanding the correct migration path is critical before you start your upgrade to Exchange Subscription Edition.

Migrate Exchange 2016 to Exchange SE

  1. In-place upgrade is supported (CU14 or CU15 required)
  2. Exchange SE RTM installs as a cumulative update
  3. Minimal disruption and fastest migration path
  4. Recommended by Microsoft

Exchange 2016 to Exchange SE Legacy Upgrade

  1. In-place upgrade is not supported
  2. Requires a side-by-side deployment
  3. Mailboxes must be migrated to Exchange SE
  4. Legacy servers must be decommissioned

It is known as an Exchange 2016 SE legacy upgrade.

Pre-Migration Planning Checklist

Successful Exchange Server SE migration begins with preparation.

Assess Your Environment

  • Current Exchange version and CU level
  • Number of mailboxes and public folders
  • On-premises or hybrid setup
  • Third-party integrations

Infrastructure Requirements

  • Supported OS: Windows Server 2019, 2022, or 2025
  • Healthy Active Directory
  • Proper DNS and networking
  • Valid SSL certificates

Licensing Readiness

  • Exchange SE subscription licenses
  • Server licenses and CALs with active Software Assurance
  • Microsoft 365 E3/E5 licenses (if applicable)

Backup Strategy

  • Full Exchange and AD backup
  • Tested restore procedures

Step-by-Step Guide to Migrate from Exchange Server 2016/2019 to Exchange SE

1. How to Migrate Exchange 2019 to Exchange Server SE

This process involves a legacy upgrade with mailbox migration.

Step 1: Prepare for Exchange SE

  • Upgrade Exchange 2016 to CU23.
  • Ensure Active Directory schema health.
  • Prepare a new server with a supported OS.
  • Document certificates, connectors, and mail flow settings.

Note – Coexistence between Exchange 2016 and Exchange SE is temporary.

Step 2: Install Exchange Server SE

  • Install Exchange SE on the new server.
  • Configure:
  • Mailbox databases
  • Certificates
  • Send and Receive connectors
  • Domains and virtual directories
  • Verify Autodiscover, Outlook, and OWA functionality.

Step3: Migrate Mailboxes

  • Test mailbox creation on Exchange SE.
  • Move mailboxes using PowerShell move requests.
  • Perform batch migrations to reduce impact.
  • Monitor migration status and validate access.

Step 4: Migrate Public Folders

  • Create public folder mailboxes.
  • Export folder statistics.
  • Map folders to target mailboxes.
  • Complete migration and validate access.

Step 5: Post-Migration Tasks

  • Verify mail flow (internal and external).
  • Update firewall and DNS routing.
  • Ensure backups are active.
  • Safety decommission Exchange 2016.

2. How to Migrate Exchange 2019 to Exchange Server SE

It is the simplest upgrade scenario.

In-Place Upgrade Process

  1. Upgrade Exchange 2019 to CU14 or CU15.
  2. Run Exchange SE setup.
  3. Complete readiness checks.
  4. Install and reboot.
  5. Validate services, mail flow, and databases.

This method allows organizations to migrate Exchange 2019 to Exchange SE.

Common Challenges During Exchange SE Migration

Migrating to Exchange Server Subscription Edition using Microsoft’s manual methods can be complex, especially in environments with a large number of mailboxes or legacy configurations. Administrators often face challenges such as stalled or suspended mailbox maintenance requests, performance issues during large mailbox or archive migrations, and quota limitations during public folder migrations. Inconsistent configurations, outdated certificates, or undocumented send and receive connectors can further complicate the migration process.

Additionally, manual migrations rely heavily on PowerShell scripting, which increases the risk of human error and requires significant administrative time and expertise. Another major limitation of the native approach is that it supports migrations only within the same Active Directory domain or forest, making cross-domain or cross-forest migrations difficult or impossible without additional effort.

Simplifying Migration via Professional Migration Tool

To overcome these manual migration challenges and reduce operational complexity, many organizations choose third-party migration tools, such as the Shoviv Exchange Migration Tool. This tool simplifies Exchange Server SE migration by automating mailbox and public folder transfers without the need for complex scripts. It supports both same-domain and cross-domain migrations and allows administrators to migrate multiple mailboxes simultaneously, with no mailbox-size limit.

With its user-friendly interface, built-in filtering options, and detailed migration reporting, Shoviv helps minimize downtime, reduce manual errors, and accelerate the overall migration process. For organizations performing an Exchange 2016/2019 to Exchange SE upgrade or managing large-scale migrations, using a specialized migration tool can significantly improve reliability and efficiency.

Best Practice for a Successful Exchange SE Migration

  • Always use the latest cumulative updates
  • Migrate mailboxes in small batches
  • Test in a staging environment
  • Monitor logs continuously
  • Document every configuration change

Conclusion

Migrating from Exchange Server 2016 or 2019 to Exchange Server Subscription Edition (SE) is a critical step toward a secure, supported, and future-ready messaging environment. Whether you plan to migrate Exchange 2019 to Exchange SE or perform an Exchange 2016 to Exchange SE, success depends on careful planning, correct execution, and proper validation.

With Exchange SE’s subscription model lifecycle, organizations can finally eliminate end-of-life stress. For complex environments, tools like Shoviv Exchange Migration Tool provide a reliable and efficient alternative to manual migration methods.


Frequently Asked Questions:-

Is Exchange SE a one-time purchase?

No. Exchange SE uses a subscription-based licensing model.

Can Exchange Server 2019 be upgraded directly to Exchange SE?

Yes. Exchange Server 2019 CU14 or CU15 supports an in-place upgrade to Exchange SE.

Is an in-place upgrade from Exchange Server 2016 to Exchange SE supported?

No. Exchange Server 2016 requires a side-by-side migration before moving to Exchange SE.

Does Shoviv support cross-domain Exchange migration?

Yes. Shoviv Exchange Migration Tool supports both same-domain and cross-domain migrations.

Can Shoviv migrate large Exchange mailboxes?

Yes. Shoviv supports large and archived mailboxes without size limits.

Is Shoviv suitable for Exchange 2016 to Exchange SE legacy upgrade?

Yes. It simplifies mailbox and public folder migration during legacy upgrades.

Scroll to Top
Trust Badge