What a cloud migration consultant does
The consultant owns the plan and the execution. That covers the assessment, the choice of migration approach for each application, the build of the target, the cutover and the stabilization afterwards.
The goal is not to move everything. The goal is to move what should move, in the right way, in the right order.
Stralya provides cloud migration consulting for companies moving from on-premises, from a hosting provider or from one cloud to another. This page belongs to our cloud consultant offer.
Choosing the right migration approach
Not every application deserves the same effort. We pick an approach per application, based on its value, its age and its dependencies.
| Approach | What it means | Fits when |
|---|---|---|
| Rehost | Move as is, with minimal change | Speed matters and the application is stable |
| Replatform | Move with targeted improvements, such as a managed database | You want quick gains without a rewrite |
| Refactor | Redesign for cloud-native services | The application is strategic and will live long |
| Replace | Swap for a SaaS product | A commodity function costs more to run than to buy |
| Retire | Switch off | Nobody uses it any more |
| Retain | Leave in place for now | Constraints or low value make the move premature |
Key point: the cheapest migration is often the one you skip. Retiring and retaining some applications shrinks the project and the bill.
Planning a move and unsure about scope?
Our free audit lists your applications, flags the risky ones and proposes a first sequence.
Our cloud migration process
PHASE 01
Assessment
We inventory applications, data, dependencies, licences and constraints. This is where hidden coupling and forgotten systems appear.
PHASE 02
Target design
We define where each workload lands. If the foundations are missing, we work with our <a href="/services/cloud/cloud-architecture">cloud architecture consultant</a> team to build them first.
PHASE 03
Wave planning
We group workloads into waves, starting with low-risk ones to build confidence and a repeatable method.
PHASE 04
Build and rehearse
We prepare the target, migrate data and run a rehearsal of the cutover, with a measured downtime window.
PHASE 05
Cutover
We switch over with a clear checklist, a communication plan and a rollback decision point.
PHASE 06
Stabilize and optimize
We watch the new environment, fix what the real traffic reveals and hand over operations.
Risks we plan for
Hidden dependencies
A system nobody documented stops working after the move.
Data transfer
Large datasets take time, and synchronization must stay consistent until cutover.
Downtime
The window must fit your business, not the project calendar.
Security gaps
Identities, network rules and logging must be in place before data arrives.
Cost surprises
An as-is move can raise the bill if the target is not sized properly. Our <a href="/services/cloud/cloud-cost-optimization">cloud cost optimization consultant</a> work addresses this early.
Common mistake: treating migration as a lift-and-shift project with a fixed date and no assessment. The date then drives the decisions, and the problems show up in production.
How to choose a cloud migration consultant
| Criterion | What to look for |
|---|---|
| Assessment first | A consultant who refuses to quote before looking at your estate |
| Rollback for every wave | A written way back if the cutover fails |
| Experience across approaches | Not only lift-and-shift |
| Team capacity | Enough people to run waves in parallel when needed |
| Handover | Your team can operate the result |
Deliverables
Inventory
A complete inventory with dependencies and a risk rating per application.
Approach and target
A migration approach per application and a target architecture.
Wave plan
A wave plan with owners, prerequisites and rollback steps.
Cutover runbooks
Cutover runbooks and rehearsal results.
Post-migration review
A review with the actions that remain.
Duration and how we work with your team
The length of a migration depends on the number of applications, their complexity, the data volumes and your downtime constraints. The assessment is short and gives you a realistic timeline before you commit. Typical durations are in the pricing table below.
We work with your IT and business owners, with regular checkpoints. Each wave ends with a review before the next one starts.
Cloud migration pricing
Every engagement starts with a diagnosis and ends with a fixed quote. Durations are typical, not promised.
| Format | Duration | Price |
|---|---|---|
| Readiness assessment | 2 to 4 weeks | Fixed quote after diagnosis |
| Migration project | 6 weeks to 6 months | Fixed quote after the assessment |
| Managed optimization after handover | Monthly | Monthly fee quoted at handover |
What changes the price: number of workloads, dependencies between applications, compliance scope and how much of the execution your team keeps.
The quote covers senior consultants only, a defined scope and the deliverables of each phase. Cloud provider costs are separate from our fees and are estimated in the cost model during the assessment.
Start your cloud migration with Stralya
If you are looking for a cloud migration consultant who plans before moving, start with the assessment. Tell us what you run today and where you want to be, and we will outline an approach.
Contact Stralya or request a free audit.
Cloud migration consultant FAQ
What does a cloud migration consultant do?
They plan and run the move of your applications and data to the cloud. That includes the assessment, the approach for each application, the cutover and the stabilization. Their main job is to reduce risk.
How long does a cloud migration take?
It depends on the number of applications, their complexity and your tolerance for downtime. Migrations are run in waves, so the first results come early. The assessment gives a realistic timeline before you commit.
Can we migrate without downtime?
Sometimes, for applications that support replication and a gradual switch. Others need a short window. We tell you which is which during the assessment and rehearse the cutover before it counts.
Should we move everything to the cloud?
Not necessarily. Some applications are better retired, replaced or left where they are. A good assessment shrinks the scope before the work starts.
Do you migrate to both AWS and Azure?
Yes. We recommend the target that fits each workload, and we also help with moves between clouds when there is a clear reason.