Anonymized engagement summary: migrating on-premises backup servers to Microsoft Azure with matching networks and security, for a national title and settlement services company (2021)
Contracted — countersigned (EPC-reported; documents private)First-pass editionA national title and settlement services company (client not named) · 2021 · Project ID EPC-2021-ANON-TITLE-AZMIG
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Opening answer. In February 2021 a national title and settlement services company's IT director countersigned a statement of work with EPC Group to move its on-premises backup servers into Microsoft Azure. The scope runs in three phases:
1. Assessment and discovery: an inventory of servers, software, storage, networking and data flow; connectivity and integration requirements; network performance targets; cloud readiness; and a gap and fit analysis. 2. Design and planning: a per-server migration plan and architecture, with the same IP ranges, subnets and security controls designed in Azure, and a prioritized migration roadmap that names who does what. 3. Migration execution: Azure virtual machines provisioned, server images created and the networking implemented.
Security between the company and Azure, and further network elements, round out the scope.
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 company's IT director signed the statement of work in February 2021. No migration record, acceptance or outcome measurement is cited or claimed.
Buyer problem and scope
| Item | What the statement of work states |
|---|---|
| Buyer | A national title and settlement services company (client not named) |
| Objective | Move on-premises backup servers from the data center to Microsoft Azure, with strong security between the company and Azure and further network elements to meet best practice |
| Assessment and discovery | Requirements and success criteria; inventory of servers, software, storage, networking and data flow; technology layout; connectivity and integration requirements; network performance targets; cloud readiness; gap and fit analysis; issues that could block migration |
| Migration approach | Architecture options chosen by workload, weighed for performance, scalability, reliability, security and cost; a customized migration plan with issues to fix first; findings reviewed with key staff |
| Design and planning | A migration plan and architecture for each backup server; recommendations for compliance, security, privacy and data recovery; the same networking environment (IP ranges, subnets, security controls) designed in Azure; a prioritized roadmap naming who does what before, during and after migration |
| Migration execution | Azure virtual machines provisioned and configured; an image created for each server; the Azure networking implemented as designed |
| Enablement | On-the-job Azure knowledge transfer for the company's IT team, led by EPC Group's certified cloud architects with the founder |
Unknowns, not stated in the document cited: server counts, data volumes, the cut-over date and any measured result.
Approach and artifacts
Mirror the network, then move. The Azure environment reproduces the existing IP ranges, subnets and security controls.
Decide per server. Each backup server gets its own migration plan and deployment architecture.
Name the owners. The roadmap states who is involved in each step and what they will do before, during and after migration.
Document (held privately):
| Document | Date |
|---|---|
| Statement of work, Microsoft Azure migration (countersigned) | February 2021 |
Results and limitations
| Claim | Basis | Status |
|---|---|---|
| The company contracted EPC Group to migrate its backup servers to Azure | Countersigned statement of work, February 2021 | Contracted (EPC-reported; documents private) |
| Migration completed, accepted, or measured results | No document cited | Not claimed |
Provenance
- Source: the countersigned statement of work (February 2021), held privately. Engagement ID: EPC-2021-ANON-TITLE-AZMIG, an alias unrelated to the client's name.
- Anonymization: industry only, under EPC Group's anonymized-case rule; the company's name, data-center 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
Azure mission-critical consulting · Azure cloud migration strategy · Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-25.