Anonymized engagement summary: Exchange Server 2016 to Exchange Server 2019 migration with hybrid enablement for a community bank (2025)
Contracted — countersigned (EPC-reported; documents private)First-pass editionA community bank (client not named) · 2025 · Project ID EPC-2025-ANON-BANK-EXCH2019
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Opening answer. In September 2025 a community bank's CIO countersigned a fixed-scope statement of work with EPC Group. The work: move the bank from Exchange Server 2016 to Exchange Server 2019 on its own VMware infrastructure, enable Microsoft 365 hybrid, and migrate about 200 active mailboxes (about 2 TB). The work was planned in five phases: environment readiness and hardening, build, migration and hybrid cut-over, documentation and knowledge transfer, and a short hypercare period. Banking regulatory requirements, cybersecurity and data privacy were set as explicit constraints on the delivery.
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 bank's CIO signed the statement of work in September 2025. This summary describes the contracted scope and approach; no cut-over record, acceptance sign-off or outcome measurement is cited or claimed.
Buyer problem and scope
| Item | What the statement of work states |
|---|---|
| Buyer | A community bank (client not named); signed by its CIO |
| Situation | Exchange Server 2016 on premises, an email security gateway, mobile-device management and an existing Microsoft 365 hybrid footprint |
| Objective | Modernize messaging on Exchange Server 2019, strengthen compliance and security, and keep interoperability with Microsoft 365 cloud services |
| Volume | About 200 active mailboxes, about 2 TB |
| Constraints | Banking regulatory requirements, cybersecurity and data privacy standards for the bank's operations and customers; minimal business disruption at cut-over |
Unknowns, not stated in the document cited: the cut-over date, whether every mailbox moved without exception, and any post-migration measurement.
Approach and artifacts
The statement of work sets out the delivery as phases and named tasks.
| Phase | Tasks |
|---|---|
| 0 — Environment readiness and hardening | Full assessment of Exchange 2016, Active Directory, the VMware infrastructure and dependencies (email security gateway, mobile-device management, Microsoft 365 hybrid); review of backup policy against recovery objectives, with a test restore of Exchange and the virtual machines; patch and security baselines; migration accounts and access, SSL, DNS, firewall and permissions validated |
| 1 — Exchange 2019 build | Target architecture and virtual-machine configuration to EPC Group's design (OS, CPU, memory, storage, security); prerequisites installed through EPC Group's scripts and readiness checklist; certificates, connectors and permissions prepared for hybrid connectivity |
| 2 — Migration and hybrid cut-over | Mailbox migration with integrity and performance checks; transport rules, connectors and coexistence services reconfigured; mail flow and device-management integrations validated; scheduled cut-over with user-acceptance and hybrid validation; legacy servers decommissioned only after migration is verified |
| 3 — Documentation and knowledge transfer | Build and migration documentation, architecture diagrams, cut-over logs and support notes; hand-over to the bank's technical team covering patching, support and change control |
| 4 — Hypercare | Seven days of stabilization support — remediation, advisory and compliance-audit support — then a support summary, an ongoing monitoring and change-control checklist, and formal sign-off |
Why the order matters in a bank. Two things happen before any mailbox moves: backups are proven by a test restore, and the hardened baseline is confirmed. Compliance-audit support is written into the hypercare phase, and formal sign-off closes the project.
Results and limitations
| Claim | Basis | Status |
|---|---|---|
| The bank contracted EPC Group for an Exchange 2019 migration with hybrid enablement | Countersigned statement of work, September 2025 | Contracted (EPC-reported; documents private) |
| Cut-over completed, mailboxes migrated, sign-off obtained | No document cited | Not claimed |
Provenance
- Source: the countersigned statement of work (September 2025), held privately. Engagement ID: EPC-2025-ANON-BANK-EXCH2019, an alias unrelated to the client's name.
- Anonymization: industry and organization size only, under EPC Group's anonymized-case rule; the bank's name, location, staff names, third-party products 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, who signed the statement of work for EPC Group.
Revision history
- 2026-10-25: anonymized engagement summary published from the engagement's countersigned statement of work.
Related service
Exchange consulting · Microsoft cloud for financial services · Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-25.