Planning a cloud migration in waves: the first 90 days
A month-by-month plan for the first 90 days of a cloud migration, from discovery and the landing zone to the first production waves.
Cloud migration planned in waves and run with discipline
We assess, migrate and modernize workloads on AWS, Microsoft Azure and Google Cloud, then run them with automation, security and cost controls built in.
What you can expect
- A landing zone with guardrails before the first workload moves
- Migration runbooks with rollback steps
- Infrastructure defined as code
- Monthly cost and performance reviews
Overview
Cloud migration, modernization, DevOps and FinOps across AWS, Microsoft Azure and Google Cloud.
A good migration is mostly planning. We map applications and dependencies, choose a path for each workload and group them into waves that the business can live with. The first workload only moves once the landing zone, identity and monitoring are in place.
After the move, we keep the platform healthy: infrastructure as code, pipelines, backups, patching and a monthly look at cost and performance.
Our team works from Pune. We can work onsite in and around the city, and remotely for organizations across India and abroad.
Capabilities
What our cloud services team does
- 01
Cloud strategy and assessment
Decisions based on your portfolio, not a generic template.
- Application portfolio review using the 7 Rs
- Landing zone and account design
- Total cost of ownership and business case
- Migration wave planning
- 02
Migration
Servers, databases and applications moved with minimal disruption.
- Rehost, replatform and refactor
- Windows, Linux, SAP and Oracle workloads
- Database migration with short cutover windows
- VMware to cloud moves
- 03
Application modernization
Architectures that scale and are cheaper to change.
- Monolith to microservices
- Containers on EKS, AKS and GKE
- Serverless and event-driven designs
- APIs in front of legacy systems
- 04
DevOps and platform engineering
Delivery pipelines that make releases routine.
- CI/CD pipelines
- Infrastructure as code with Terraform and Bicep
- Observability with logs, metrics and traces
- Internal developer platforms
- 05
FinOps and optimization
Spend that is visible, owned and kept in check.
- Cost visibility and tagging standards
- Rightsizing and commitment planning
- Budget alerts and anomaly detection
- Unit cost reporting
- 06
Cloud operations
Day-two operations with clear service levels.
- Monitoring and incident response, with 24x7 cover by agreement
- Backup and disaster recovery
- Patching and compliance baselines
- Virtual desktops on Azure Virtual Desktop and Amazon WorkSpaces
Approach
How the work runs, step by step
Each step ends with something you can review, so decisions are made on evidence rather than status updates.
Step 01
Assess
Discovery of servers, applications, dependencies and costs.
You get Assessment report
Step 02
Plan
Target architecture, migration paths and wave plan.
You get Wave plan with dates
Step 03
Prepare
Landing zone, identity, networking and guardrails.
You get Ready landing zone
Step 04
Migrate
Wave-by-wave moves with testing and sign-off.
You get Validated workloads
Step 05
Optimize
Rightsizing, automation and cost reviews.
You get Savings log
Step 06
Operate
Monitoring, patching, backups and support.
You get Monthly service report
Platforms and tools
Technology we work with
Names are trademarks of their respective owners, used only to describe technologies our teams use. No partnership or endorsement is implied. See the main platforms we work with.
- Amazon Web Services
- Microsoft Azure
- Google Cloud
- Oracle Cloud Infrastructure
- VMware
- Kubernetes
- Docker
- Terraform
- Ansible
- GitHub Actions
- GitLab CI
- Azure DevOps
- Jenkins
- Prometheus
- Grafana
Industries
Where this work matters most
- Hi-Tech & SoftwareProduct engineering, SaaS platforms, quality engineering and sustenance.
- Banking, Financial Services & InsuranceDigital journeys, core integration, risk analytics and security for BFSI.
- Retail & E-commerceCommerce platforms, personalization, store systems and workforce management.
- Healthcare & Life SciencesPatient and clinician apps, interoperability, clinical data and secure cloud.
- EducationStudent systems, learning platforms, campus networks and analytics.
Questions
Cloud Services: frequently asked questions
Which cloud should we choose?
It depends on your applications, licensing, skills and data residency needs. We compare the options against your actual workloads and usually recommend one primary platform, adding a second only where it earns the extra complexity.
How long does a migration take?
A focused migration of a few dozen servers can typically run in eight to twelve weeks after assessment. Larger estates move in waves over several months. The assessment gives you a plan with dates before you commit.
How do you keep cloud costs under control?
We tag every resource, set budgets and alerts, rightsize regularly, and review commitments such as reserved instances and savings plans with you each month.
Can you support hybrid environments?
Yes. Many businesses keep some systems on premises or in a colocation facility. We design connectivity, identity and monitoring that work across both.
Often combined with
Related services
- 06Data Center & HardwareDesign, supply, build and operate data center infrastructure, servers, storage and end-user hardware.
- 05CybersecuritySecurity testing, zero trust, identity, detection and response, and compliance programs you can measure.
- 09Managed IT ServicesService desk, monitoring, patching and application support under clear service levels.
Further reading
Talk to our cloud services team.
Tell us about your systems, timelines and constraints. We will come back with questions, options and a suggested first step.