Azure VM Migration Architect Needed
Budget: ₹600 – ₹1,500 INR
I’m preparing to move a sizeable estate—well over ten Windows-based virtual machines—out of our data-centre and an existing AWS tenancy into Microsoft Azure. A portion of these hosts run line-of-business applications that can only afford a very brief outage, while the rest are more tolerant, so the migration plan must distinguish clearly between the two groups.
What I need from you is an end-to-end engagement:
• Assessment & Planning
– Inventory validation, dependency mapping, and sizing using Azure Migrate, Service Map or similar tools.
– A phased schedule that shows which VMs move in which wave, highlighting those with strict downtime limits.
• Landing-zone Preparation
– Subscription, networking, identity and RBAC alignment to our existing Azure tenant.
– Recommendations on storage tiers, availability sets, Azure Backup and monitoring (Log Analytics, Azure Monitor).
• Migration Execution
– Lift-and-shift via Azure Migrate or ASR for the machines that can tolerate brief pauses.
– Near-zero-downtime approaches (replication cut-over, blue/green) for the critical workloads.
– Complete testing and sign-off before each cut-over.
• Post-migration Hardening
– Performance benchmarking versus on-prem/AWS baselines.
– Backup validation, patching strategy, cost-optimisation tips (reserved instances, auto-shutdown, etc.).
Acceptance criteria
1. All targeted VMs boot in Azure with identical functionality and IP reachability.
2. Critical application downtime does not exceed the window defined in the agreed schedule.
3. Handover package delivered: runbook, architecture diagram, and rollback plan.
If you’re an Azure-certified architect with recent hands-on migration projects under your belt and you’re confident juggling on-prem, AWS, and Azure toolsets, I’m ready to start this week.
What I need from you is an end-to-end engagement:
• Assessment & Planning
– Inventory validation, dependency mapping, and sizing using Azure Migrate, Service Map or similar tools.
– A phased schedule that shows which VMs move in which wave, highlighting those with strict downtime limits.
• Landing-zone Preparation
– Subscription, networking, identity and RBAC alignment to our existing Azure tenant.
– Recommendations on storage tiers, availability sets, Azure Backup and monitoring (Log Analytics, Azure Monitor).
• Migration Execution
– Lift-and-shift via Azure Migrate or ASR for the machines that can tolerate brief pauses.
– Near-zero-downtime approaches (replication cut-over, blue/green) for the critical workloads.
– Complete testing and sign-off before each cut-over.
• Post-migration Hardening
– Performance benchmarking versus on-prem/AWS baselines.
– Backup validation, patching strategy, cost-optimisation tips (reserved instances, auto-shutdown, etc.).
Acceptance criteria
1. All targeted VMs boot in Azure with identical functionality and IP reachability.
2. Critical application downtime does not exceed the window defined in the agreed schedule.
3. Handover package delivered: runbook, architecture diagram, and rollback plan.
If you’re an Azure-certified architect with recent hands-on migration projects under your belt and you’re confident juggling on-prem, AWS, and Azure toolsets, I’m ready to start this week.