A landing zone before a lift and shift
Most Azure estates we inherit were built one resource group at a time: flat networks, subscriptions named after whoever created them, and a bill nobody can attribute. We start with the boring layer that makes everything after it cheap to change.
Foundation first, workloads second
Identity, subscription topology, naming, tagging, policy and network hub come first — usually inside the first fortnight. Once that exists, moving a workload is a small, reversible piece of work instead of a negotiation.
Everything is delivered as Bicep or Terraform you keep, in a repository you own, documented in language your next engineer can read without ringing us.
What moves, when, and what it costs
| Wave | Scope | Typical duration |
|---|---|---|
| Foundation | Tenant, identity, subscriptions, policy, hub network | 2 weeks |
| File & print | File servers to SharePoint or Azure Files, print to Universal Print | 2–3 weeks |
| Servers | Azure Migrate assessment, rehost, right‑size, decommission on‑premises | 3–6 weeks |
| Data | SQL to Managed Instance or Azure SQL, backup and retention set | 3–5 weeks |
| Optimise | Reservations, savings plans, Hybrid Benefit, monthly cost review | Ongoing |
Durations are indicative for a 10–100 seat estate. Each wave is quoted and approved on its own, so you can stop after any one of them.