Blueprint in hand. Migration / modernization plan out.
One day with your IT leaders and architects to turn an agreed direction into a specific, costed Azure plan: named workloads, build-ready landing zone designs, and a dated roadmap. The “Day Two” step of the journey.
Prerequisite · Arrive with a direction
MICROSOFT HOSTED
Migration Innovation Hub
Microsoft-hosted event on migration / modernization scenarios.
ARCHITECTNOW HOSTED
Migration Day
ArchitectNow “Day One” session: objectives, dispositions, blueprint.
CUSTOMER LED
Your internal exercise
You already know why Azure and which workloads are candidates.
“Day Two” is the next step, not the next day; we schedule it once the estate audit is done and the right people can be in the room. Before the session, the estate audit grounds the day: optional Azure Migrate discovery (servers, VMware, SQL, apps: inventory, dependencies, sizing), CMDB exports and owner interviews where tooling can’t reach, your existing Azure footprint captured, and first-wave candidates agreed with owners, so the room plans, not discovers.
1 day
On site or virtual
2nd
Step of the migration / modernization journey
6
Working blocks, audit to start date
6
Artifacts: designs, specs, and costs
What you get
Six artifacts, ready to execute.
01Scoped Migration / Modernization Assessment
Every in-scope workload with a confirmed disposition, right-sized target, and readiness blockers named.
02Landing Zone Design · Tenant & Subscriptions
Management groups, subscription model, naming and tagging, and platform-as-code, at build-ready depth.
03Landing Zone Design · Network & Services
Hub-and-spoke or Virtual WAN, address plan, hybrid connectivity, firewall, private endpoints and DNS, and system placement.
04Governance & Operations Specification
Identity and RBAC, Azure Policy, Defender, Backup and Site Recovery, monitoring, and cost guardrails, by role, against the Well-Architected pillars.
05Wave Plan & Detailed Roadmap
Waves sequenced by dependency and value, method and owner per wave, cutover and rollback, and Wave 1 dated.
06Run-Cost, TCO & Funding
Azure run-rate with Hybrid Benefit and reservations applied, a roadmap TCO, and Microsoft funding arranged for qualified accounts.
How it works
Six blocks. Roughly 9 to 4, with a working lunch.
01 · MORNING
Audit Review & Scope
Walk the estate audit, confirm each disposition, lock the scope.
02 · LATE MORNING
Tenant & Subscription Design
Management groups, subscriptions, naming, platform-as-code: new, or your existing zone hardened.
03 · MIDDAY
Network & Service Design
Topology, address space, hybrid connectivity, firewall, private endpoints, and where each system lands.
04 · EARLY AFTERNOON
Governance & Operations
Identity, Policy, Defender, HA / BC / DR, monitoring, and cost controls, by role.
05 · MID AFTERNOON
Waves & Methods
Group workloads into waves; pick the method per wave: Azure Migrate, AVS, database migration, AKS or PaaS.
06 · LATE AFTERNOON
Roadmap, Sizing & Funding
Dated roadmap, effort sizing, run-cost and TCO, funding path, and the Wave 1 start date agreed.
Why ArchitectNow
●4 Solutions Partner Designations
Infrastructure Azure · Digital and App Innovation · Data and AI · Support Services.
●Migration / Modernization Delivery, End to End
Windows, Linux, SQL Server, PostgreSQL, VMware, and containers moved to Azure.
●Certified Azure Architects on Staff
Solutions Architect Expert and DevOps Engineer Expert practitioners lead every engagement.
●Microsoft Migration Funding (qualified accounts)
Microsoft co-invests through Azure Accelerate. Subject to eligibility.