Exchange Server is some of the most complex infrastructure in a Microsoft environment. It touches email, calendars, mobile devices, federation, Active Directory, and — in hybrid configurations — Microsoft 365 at the same time. Inspizer has been supporting Exchange environments since Exchange 2003, and has migrated organisations from every version since.
Every version. Every scenario. Including a 40,000-mailbox Parliamentary migration completed with zero downtime.
Most IT infrastructure can be supported by a generalist with a manual and enough time. Exchange Server is different. The organisations that come to us usually have one of three situations.
Their IT team handles everything else but Exchange is a specialism that sits outside their depth. Updates, certificate renewals, transport rule management, and mailbox migrations are happening slowly or not at all because nobody on the team is confident enough to make changes to something this critical.
The easy mailboxes moved to Exchange Online months ago. The complex ones — executive mailboxes, distribution groups with hundreds of members, mailboxes with years of PST archives, resource mailboxes used by every meeting room — are still on-premises. The migration has stalled.
A hybrid deployment was set up to enable mailbox migration and never fully decommissioned. Now there is an on-premises Exchange server running to maintain the hybrid configuration, costing licence, hardware, and maintenance overhead for a role it no longer needs to play.
Inspizer's Exchange practice covers on-premises support, hybrid deployment management, Exchange to Exchange Online migration, legacy decommissioning, and public folder migration — across every Exchange version from 2010 to 2019.
Health monitoring, certificate management, transport rule and connector management, database management, Cumulative Update installation, and Active Directory integration. Exchange support as it should be — proactive, not reactive.
Classic hybrid and minimal hybrid configuration, hybrid health monitoring and troubleshooting, and — crucially — hybrid decommissioning done correctly after migration completes. Most Exchange support engagements eventually get here.
Pre-migration assessment, hybrid deployment, mailbox migration waves, distribution group and resource mailbox migration, mail flow cutover, and post-migration validation. We have run this from Exchange 2010, 2013, 2016, and 2019.
Recipient attribute verification, licence deactivation, server decommissioning in the correct sequence, Active Directory cleanup, and DNS record updates. Removing Exchange incorrectly breaks things. We do it correctly.
Public folder assessment, migration to Exchange Online public folders, migration to SharePoint or Teams, or decommissioning of unused public folder trees. We've migrated public folders of every size — including a large Parliamentary estate with zero downtime.
SSL/TLS certificate renewals on Exchange, installation, and the Autodiscover/OWA/ActiveSync/EWS binding updates that go with them. Certificate renewals are a common cause of email outages — we plan them well in advance, not as emergencies.
We have migrated from every on-premises Exchange version since 2003. The failure modes are different at each version — the knowledge transfers directly.
End of extended support October 2020. No longer receiving security patches. Migration is urgent — not optional. The migration path requires an intermediate Exchange version and specific handling.
End of extended support April 2023. Also no longer receiving patches. Migration paths from Exchange 2013 to Exchange Online are simpler than from 2010 but still require a hybrid deployment for staged migration.
Extended support ends October 2025. If your organisation is still running Exchange 2016, the decommissioning clock is running. We support 2016 environments and plan migrations from them.
The last on-premises version of Exchange Server. Extended support runs to October 2025. Microsoft has confirmed there will be no Exchange Server 2022 — the roadmap is Exchange Online. We support 2019 environments and plan long-term migration timelines.
Understanding the current Exchange environment before planning anything. Version, database count and size, mailbox count and distribution, public folders, distribution groups, connectors, third-party dependencies. Problems found before migration start are remediation tasks — problems found mid-migration are incidents.
For staged and cutover migrations above a certain size, hybrid is the correct approach — enabling mailbox moves without a hard cutover that affects all users simultaneously. We deploy the hybrid configuration as the first phase of the migration.
Migrating a pilot group first — typically IT staff and willing early adopters — to test the process end-to-end, validate Outlook profile reconfiguration, and identify any environment-specific issues before the full migration begins.
Migrating mailboxes in planned waves, at a pace that suits your organisation and manages helpdesk demand at each stage. Complex mailboxes — executives, shared mailboxes with many delegates, resource mailboxes — receive additional preparation and post-migration support.
MX record changes, inbound connector configuration, and anti-spam routing at the point of cutover — with rollback capability planned in advance and tested. We are on hand throughout to respond to issues in real time.
Correct Exchange decommissioning once all mailboxes are on Exchange Online — recipient attribute verification, AD cleanup, DNS updates, licence retirement, and full documentation of the completed migration and environment state.
Yes. We support on-premises Exchange environments on a project basis or as an ongoing support arrangement — not just for organisations that have already decided to migrate. If you need someone to manage your Exchange environment while you evaluate the migration options and timeline, that is a standard engagement for us. We document the environment, handle routine maintenance, and provide the technical input you need to make an informed migration decision without feeling rushed into it.
An Exchange hybrid deployment connects your on-premises Exchange organisation to Exchange Online, enabling coexistence — shared free/busy information, cross-premises mailbox moves, and a unified Global Address List across both environments. Whether you need one depends on how you plan to migrate. For organisations with fewer than 150 mailboxes and a simple environment, a cutover migration may be the simpler and faster approach. For larger or more complex organisations, hybrid enables a phased migration that reduces risk and manages helpdesk demand. We assess the right approach for your specific situation during the discovery call.
It is not too late, but it is urgent. Exchange 2010 and 2013 are both out of extended support, which means they are no longer receiving security patches. Every day they remain in production is a day your email infrastructure is running with unpatched vulnerabilities. The migration path from Exchange 2010 is more involved than from later versions — you typically need to introduce an intermediate Exchange 2016 or 2019 server to facilitate the hybrid configuration — but it is a well-understood process we have run many times.
Decommissioning Exchange Server is not simply a matter of removing the servers. Exchange writes attributes to Active Directory throughout its lifecycle, and the recipient objects in AD need to be prepared before the last Exchange server is removed — otherwise mail routing breaks for shared mailboxes, contacts, and distribution groups. The correct decommissioning sequence involves verifying that all mail-enabled objects have the correct attributes in AD, removing servers in the correct role order, cleaning up AD objects, updating DNS records, and retiring licences. We follow this sequence precisely, verify at each step, and document the completed decommissioning.
Yes — we migrate Exchange public folders either to Exchange Online public folders (a like-for-like move that preserves mail-enabled public folder functionality) or to SharePoint and Teams (where the organisation wants to move off public folders entirely). The right approach depends on how the public folders are actually being used. For organisations using public folders primarily as shared email inboxes, migration to mail-enabled shared mailboxes in Exchange Online is often a better outcome. We assess usage patterns first and recommend the migration path that creates the least disruption and the most usable end state.
No sales pitch. Just an honest conversation about what your Microsoft 365 environment needs and how we can help.