Blogg
Exchange Server End of Support: Migration Choices
Exchange Server end of support upgrade planning is now a practical priority for organisations that still depend on Exchange Server 2013, 2016 or 2019. An unsupported messaging platform may continue to run, but it no longer offers the same lifecycle protection as a supported release. Security updates, vendor assistance and compatibility assurances become more limited, while an unexpected failure can be harder to diagnose and recover from.
The right answer is not always “move everything to the cloud”. Some organisations need local control, integration with internal applications or a specific data-management model. Others will reduce administrative work by moving mailboxes to Microsoft 365. This guide compares both directions and explains how to prepare an Exchange Server migration without treating it as a simple licence purchase.
Start by identifying the current Exchange environment
Before choosing an upgrade path, document what is actually running. Product names alone are not enough: the server version, cumulative update level, operating system, mailbox count and connected systems all affect the migration.
- Confirm the Exchange version: check whether the organisation uses Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 or a mixture of versions.
- Record the deployment: note the number of servers, databases, sites, accepted domains, connectors and mailbox databases.
- Map identity: document Active Directory, domain controllers, synchronisation tools, administrator accounts and any hybrid configuration.
- List clients: include Outlook versions, mobile devices, shared mailboxes, resource mailboxes and webmail users.
- Find application dependencies: line-of-business software, scanners, multifunction printers, monitoring systems, backup products and applications that send email through SMTP.
- Review protection and recovery: record anti-malware filtering, archiving, retention, backup, restore testing and disaster-recovery procedures.
This inventory prevents a common failure: migrating user mailboxes while overlooking an application that still relies on a local receive connector, an old authentication method or a particular SMTP address.
What an Exchange Server end of support upgrade should achieve
An upgrade should provide more than a newer server name. Define the outcome in operational terms:
- users can send and receive messages from supported clients;
- mail flow works for internal and external recipients;
- shared mailboxes, calendars, contacts and resource bookings remain usable;
- business applications can still send alerts and documents;
- administrators can monitor, back up and restore the service;
- the organisation has a documented security and incident-response process; and
- the chosen platform has a lifecycle that fits the organisation’s planning horizon.
Do not assume that purchasing an Exchange licence automatically makes an old environment supported. A licence permits use under its terms; support status also depends on the product version, updates, operating system and Microsoft’s current lifecycle policies. Confirm the current support position before approving a design.
Compare the main migration choices
| Choice | Best fit | Main advantages | Important limitations |
|---|---|---|---|
| Microsoft 365 mailboxes | Organisations willing to use a cloud-hosted messaging service | Less server hardware and fewer Exchange maintenance tasks; suitable for users working across connected devices | Requires tenant, identity, connectivity, security and data-governance planning |
| Newer supported on-premises Exchange path | Organisations with strong local-control, integration or regulatory requirements | Mailboxes and core service remain under the organisation’s infrastructure and administration | Requires server planning, patching, backup, monitoring, high availability and current licence compliance |
| Hybrid or staged migration | Large or complex organisations that cannot move all users at once | Allows phased mailbox moves and transition testing | More components and dependencies; identity, mail flow and coexistence must be managed carefully |
| Temporary coexistence only | Short transition periods during a controlled project | Reduces the need for a single cutover date | Should not become an indefinite architecture with unsupported servers left in production |
Option 1: Move mailboxes to Microsoft 365
For many small and medium-sized organisations, Microsoft 365 is the simplest strategic alternative to maintaining Exchange servers. Microsoft hosts the messaging platform, while the organisation remains responsible for account administration, access control, configuration, security decisions and its own migration planning.
Microsoft 365 Business Standard is designed for a business productivity environment covering document creation, communication, information sharing and work across team members. It supports Windows, macOS, Android and iOS, with one user using the subscription across up to five devices according to the product facts. This can suit an organisation that primarily needs familiar Office workflows and cloud-connected productivity.
Microsoft 365 Business Premium is the more appropriate product to investigate when the organisation needs the Business Premium service rather than Business Standard. Compare the included services, security requirements, account model and Microsoft licensing terms against the actual needs of the business before selecting it. Neither product should be chosen solely because it contains Office applications: the migration must also cover mailbox hosting, identity, access and information governance.
A cloud-oriented Exchange Server migration commonly includes these stages:
- Prepare the Microsoft 365 tenant and verify the organisation’s domains.
- Review identity synchronisation or decide how cloud identities will be administered.
- Assess mailbox sizes, aliases, shared mailboxes, distribution groups, calendars and archive data.
- Check Outlook, mobile and application compatibility.
- Configure security controls, administrator roles, retention requirements and recovery procedures.
- Test a small group of representative mailboxes.
- Move users in batches, monitor mail flow and communicate each batch clearly.
- Remove or isolate the old Exchange environment only after all dependencies have been confirmed.
Microsoft 365 is not a way to avoid every responsibility. Poor identity design, weak administrator protection, incorrect domain records or untested application mail flow can still interrupt business operations.
Option 2: Continue with an on-premises Exchange strategy
On-premises Exchange may remain suitable where local infrastructure is required, internal applications are tightly integrated with the mail system, or the organisation has a dedicated operations team. It can also be appropriate where a phased move to another architecture is not yet practical.
However, an on-premises decision must be based on a currently supported target, not simply on the availability of an older installer. Exchange Server 2019 was a common destination for Exchange Server 2013 upgrade and Exchange Server 2016 upgrade projects, but organisations planning now should verify Microsoft’s current support and product roadmap before treating Exchange Server 2019 as a long-term answer. A move from one unsupported version to another does not solve the lifecycle problem.
On-premises planning normally covers:
- server and operating-system compatibility;
- storage performance, database capacity and network design;
- certificate, DNS and mail-flow configuration;
- high availability and disaster recovery;
- anti-malware, backup and monitoring;
- client and application compatibility;
- administrator skills and patch management; and
- Exchange Server licence and Client Access Licence requirements.
Exchange licensing is not only a server question. Depending on the deployment and licensing terms, access may require the appropriate Exchange Server CALs, commonly assigned on a user or device basis. Confirm the correct edition, CAL type and current Microsoft terms for every user or device that will access the service.
KEYFORREST offers Exchange Server 2019 Standard with 10 Exchange Server 2019 Standard CALs as a bundle. The bundle includes the server licence and ten CALs, with User CALs supplied by default; customers can indicate if Device CALs are required. It is intended for organisations operating their own company email server, but it should not be presented as a substitute for checking current Exchange support status. Genuine licences are available at KEYFORREST with instant electronic delivery. See the current product page for the present offer and licence details.
Option 3: Use a staged or hybrid migration
A staged approach can reduce operational risk when the organisation has many mailboxes, multiple sites or applications that cannot be changed at once. It allows the project team to migrate a small group, validate mail flow and resolve issues before moving the wider user population.
Choose pilot users who represent real complexity rather than only technically confident employees. Include a shared mailbox user, a mobile user, a remote worker, a calendar-heavy team and someone who relies on a business application that sends email. Test internal messages, external messages, attachments, calendar invitations, delegates, shared calendars, address lists and mobile access.
Coexistence requires a clear ownership model. During the transition, administrators must know where each mailbox resides, which system handles inbound and outbound mail, how addresses are synchronised and how support requests are escalated. Write down the rollback decision before the first production batch. A rollback may not reverse every data change, so define what it means and how new messages will be handled.
Check clients and applications before moving users
The mailbox move is often easier than the surrounding compatibility work. Review Outlook builds and operating systems, but also test mobile mail profiles, shared mailboxes, delegates and meeting-room calendars. Users may have automatic rules, local archives or third-party add-ins that require separate attention.
Applications deserve a dedicated workstream. For each scanner, printer, ERP system, alerting service or custom application, record the sending address, SMTP server, port, authentication method, encryption requirement and expected message volume. Test failure handling as well as successful delivery. An alert that silently disappears is more dangerous than one that generates a visible error.
Also review data that is not a normal mailbox: public folders, archives, legal holds, retention settings, transport rules and journaling arrangements. The exact migration method depends on the source, target and Microsoft’s current tools, so validate the design in a test environment before making production changes.

Build a practical migration plan
- Assign ownership. Name the project lead, technical administrator, business representatives and communications owner.
- Freeze the inventory. Export or document users, aliases, groups, shared resources, connectors and applications.
- Choose the target. Compare Microsoft 365 with the current supported on-premises route using cost, control, skills, integration and lifecycle criteria.
- Prepare a test environment. Use representative accounts and data without disrupting production mail flow.
- Run a pilot. Measure login, send, receive, calendar, mobile and application results.
- Schedule batches. Avoid critical business periods and communicate user actions in advance.
- Monitor after each batch. Check delivery queues, help-desk tickets, authentication events, application alerts and user reports.
- Decommission carefully. Remove old servers only after confirming that no mailbox, connector, relay, archive or recovery process depends on them.
Which path should you choose?
| Organisation profile | Recommended direction | Orsak |
|---|---|---|
| Small business with limited Exchange administration | Evaluate Microsoft 365 first | It can reduce local server maintenance and provide familiar productivity tools across connected devices. |
| Business with many internal applications or strong local infrastructure | Compare a supported on-premises design with a staged cloud migration | The decision depends on integration, skills, security design and the cost of operating the service. |
| Organisation already planning a wider cloud transition | Use a phased Microsoft 365 migration | Email can move in controlled groups while identity and application dependencies are addressed. |
| Organisation considering Exchange Server 2019 only because it is newer than 2013 or 2016 | Pause and verify current support status | A version upgrade is not enough if the selected target is no longer the appropriate long-term platform. |
Vanliga frågor
What does Exchange Server end of support mean?
It means the version has passed the vendor’s supported lifecycle stage. The software may continue to operate, but organisations should not assume ongoing security updates, technical assistance or compatibility for an unsupported deployment.
Is an Exchange Server 2013 upgrade still worthwhile?
Leaving Exchange Server 2013 in production is not a sound long-term plan. Assess Microsoft 365 and the currently supported on-premises alternatives rather than moving automatically to an older target that may also have lifecycle limitations.
What about an Exchange Server 2016 upgrade?
Start with an inventory and support-status review. A direct version move may not be the best answer in 2026; mailbox migration to Microsoft 365 or another supported architecture may provide a more durable result.
Is Exchange Server 2019 a safe destination?
Do not decide from the version number alone. Verify Microsoft’s current lifecycle, deployment requirements and available update path. Exchange Server 2019 Standard with CALs may fit a specific on-premises requirement, but the licence does not remove the need for lifecycle planning.
Do Microsoft 365 subscriptions replace all Exchange CALs?
Cloud subscriptions and on-premises CALs are different licensing arrangements. Determine which users, services and servers will remain on-premises, then confirm the applicable Microsoft licensing terms for the selected design.
Make the decision before the next incident
An Exchange Server end of support upgrade is an architecture and operations project, not just a product purchase. Begin with dependencies, identify the target platform, test representative users and applications, and plan coexistence or cutover in measurable stages. For many organisations, Microsoft 365 reduces the burden of running mail servers; for others, a supported on-premises strategy remains valid when local control and integration justify the operational work.
We offer genuine Microsoft licences and Microsoft 365 products at KEYFORREST with instant electronic delivery. Review the current product page and select the option that matches your target architecture, users and licensing requirements.