Skip to main content

Anonymized engagement summary: Exchange Server 2010 to Exchange Server 2019 migration for a municipal government (2023)

Contracted — countersigned (EPC-reported; documents private)First-pass editionA municipal government (client not named) · 2023 · Project ID EPC-2023-ANON-MUNI-EXCH2019

Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group

Opening answer. In April 2023 a municipal government countersigned a statement of work with EPC Group to move all email services from Exchange Server 2010 on premises to a new Exchange Server 2019 system. The work runs in order:

1. discovery with EPC Group's own tools 2. Active Directory clean-up for Exchange 2019 and Azure AD Connect 3. design, hardware sizing and build of Exchange 2019 4. a pilot with the new system running in parallel with the old 5. migration with EPC Group's migration tool 6. training for technical staff and end users

Disclosure. This is an EPC-reported anonymized engagement summary. The client is not named. The countersigned statement of work is retained privately and is not published in the Evidence Center, so this account is outside the Evidence Center's documented-engagement counts. Every engagement fact below is taken from that document.

Verification class

Contracted — countersigned (EPC-reported; documents private). The municipality's administrator and law director signed the statement of work in April 2023. No migration record, acceptance or outcome measurement is cited or claimed.

Buyer problem and scope

ItemWhat the statement of work states
BuyerA municipal government (client not named)
SourceExchange Server 2010 on premises
TargetA new Exchange Server 2019 system on premises, set up for the municipality's needs
DiscoveryEvaluation of the 2010 system; exact mailbox sizes and item counts; current DNS and MX records and SMTP relays; a documented, trackable plan with end-user communication
Source preparationClean-up of Exchange misconfigurations; Active Directory clean-up and optimization for Exchange 2019 and Azure AD Connect
Target buildTechnical design; hardware sizing and server requirements for Exchange 2019 and its hosts; host servers provisioned; prerequisites and Exchange 2019 installed; mailboxes, accounts and roles; advanced email security; mailbox quotas and archiving and retention policies
PilotExchange 2019 runs in parallel with Exchange 2010, with pilot users onboarded before migration
Migration and enablementEPC Group's migration tool moves users, mailboxes and their data items unchanged; training and knowledge transfer for technical staff and end users

Unknowns, not stated in the document cited: mailbox counts and volume, the cut-over date and any measured result.

Approach and artifacts

Measure the mail before moving it. Mailbox sizes and item counts are measured before the move. DNS, MX records and SMTP relays are recorded during discovery.

Run old and new side by side. Exchange 2019 goes into a pilot alongside Exchange 2010 before migration, with pilot users onboarded first.

Prepare the directory for what comes next. The Active Directory clean-up targets readiness for both Exchange 2019 and Azure AD Connect.

Document (held privately):

DocumentDate
Statement of work, Exchange Server 2010 to Exchange Server 2019 migration (countersigned)April 2023

Results and limitations

ClaimBasisStatus
The municipality contracted EPC Group to migrate Exchange 2010 to Exchange 2019Countersigned statement of work, April 2023Contracted (EPC-reported; documents private)
Migration completed, accepted, or measured resultsNo document citedNot claimed

Provenance

  • Source: the countersigned statement of work (April 2023), held privately. Engagement ID: EPC-2023-ANON-MUNI-EXCH2019, an alias unrelated to the client's name.
  • Anonymization: sector and organization type only, under EPC Group's anonymized-case rule; the municipality's name, location, staff names and commercial terms are not published.
  • Not claimed: client endorsement, completion, or any measured result.
  • Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group, named in the statement of work as leading the initiative.

Revision history

  • 2026-10-25: anonymized engagement summary published from the engagement's countersigned statement of work.

Related service

Exchange consulting · Talk to a senior architect

Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-25.

AI assistant — not a human