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)
Anonymized engagement summaryNational title and settlement services company · 2021
Opening answer. In 2021 EPC Group was engaged by a national title and settlement services company 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.
This is an anonymized engagement summary published under EPC Group's anonymized-engagement rule: the client is not named, no commercial terms are published, and every statement is EPC-reported. Named, documented engagements are in the Evidence Center.
Problem and scope
| Item | Scope |
|---|---|
| Organization | A national title and settlement services company |
| 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 |
Not reported: 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.
What EPC Group delivered and what is not claimed
| Claim | Basis | Status |
|---|---|---|
| The company contracted EPC Group to migrate its backup servers to Azure | EPC engagement record | Contracted (EPC-reported) |
| Migration completed, accepted, or measured results | Not reported | Not claimed |
Related services
Azure cloud services · All case studies · Talk to a senior architect
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Related service: Azure Mission-Critical Resilience Consulting
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published October 25, 2026 · Project alias EPC-2021-ANON-TITLE-AZMIG · Published under the anonymized-engagement rule.