Cloud Readiness Assessment
Moving something badly designed to the cloud only changes where you pay for the problem. We evaluate which workloads are worth moving, in what order and at what real destination cost, and build the migration roadmap with the business case for each workload.
The assessment inventories the workloads, evaluates the migration path appropriate to each one, estimates the real destination cost —including what usually falls outside the calculation— and orders the sequence. It delivers the roadmap agreed with the areas that own each system. It is not an infrastructure quote: it is an architecture and cost decision.
Know what is worth moving
Which workloads gain from the cloud, which do not and which need redesigning first.
Know the real cost
What it costs at destination, including egress, licensing and operation — not just the instance price.
Order the sequence
What to migrate first to reduce risk and demonstrate value early.
One surveys and maps the route. The other executes it.
These are two different services and it is worth knowing which one you need before contracting. The assessment does the first information-gathering exercise, builds the roadmap and aligns it with the business areas. The consulting practice executes that roadmap.
Cloud Readiness Assessment — this page
Surveys, maps and aligns. It surveys the workload inventory, evaluates each one's migration path, estimates the destination cost and builds the migration roadmap agreed with the areas. It runs two to four weeks depending on the size of the organisation. It does not implement, does not configure and does not operate anything.
Cloud — execution
Executes the roadmap. It takes the roadmap and executes it: destination architecture design, workload migration, cost optimisation and continuous operation of the environment. It works just as well if you already have a roadmap of your own.
Eight fronts that decide the migration.
A migration fails on what was not evaluated. We review each front with the same depth and rate readiness on explicit criteria.
Workload inventory
Which applications and services exist, what each one supports and how coupled they are to each other.
Migration path
For each workload: rehost, replatform, refactor, repurchase, retire or retain. With the reasoning behind it.
Dependencies
What breaks if a workload moves alone, and which groups have to migrate together.
Destination cost
Compute, storage, data egress, licensing and operation. What usually falls outside the initial calculation.
Architecture and design
Whether the workload is designed to take advantage of the cloud or merely to run on it.
Security and compliance
What data moves, what the regulation demands on residency and what changes in the shared responsibility model.
Operation and capabilities
Who is going to operate the destination environment and what the team knows how to do today.
Continuity
How backups, recovery and committed recovery times change when the workload moves.
Six phases, without interrupting your operation.
The assessment rests on interviews, technical inventory and consumption analysis. No workload is migrated and no configuration is modified.
Scope and preparation
We define which workloads and environments are in, and agree read-only access to the inventory and to consumption data.
Interviews
With the owners of each system and with the people operating the infrastructure today.
Inventory and dependencies
Survey of workloads, versions, consumption and relationships between systems.
Path evaluation
For each workload, the appropriate migration path and what it demands, against recognised criteria.
Cost model
Estimate of destination cost with the full set of components, compared against the current cost.
Business alignment
Presentation of the roadmap with leadership and the owning areas, to agree sequence and priorities.
What your maturity is measured against.
The evaluation does not rest on the judgement of whichever consultant shows up, nor on a vendor catalogue, but on public and auditable frameworks your team can consult and your auditor will recognise. The route also depends on where the data may live: we review the cloud regions available for Colombia and Mexico before recommending a destination.
Well-Architected
Evaluation framework. The cloud design pillars: operational excellence, security, reliability, efficiency and cost.
The 6 Rs of migration
Decision guide. Rehost, replatform, refactor, repurchase, retire or retain: the standard classification per workload.
CSA Cloud Controls Matrix
Security guide. Cloud-specific security controls and the split of responsibility with the provider.
ISO/IEC 27017
Security guide. The standard for security controls in cloud services.
FinOps
Cost guide. The discipline of managing cloud spend: who answers for cost and how it is controlled in operation.
ISO 22301
Continuity guide. Reference for evaluating how backup and recovery change when the workload moves.
The frameworks are public and verifiable: anyone on your team can consult them and check the rating we deliver. That is the difference between an auditable evaluation and an opinion.
What it costs to migrate without evaluating.
Migrations rarely fail technically. They fail on the third month's invoice and in the operation nobody prepared.
Cost that runs away
The bill grows every month because egress, licensing and oversizing never entered the calculation.
Workloads that should not have moved
Systems that cost more in the cloud and perform the same, migrated by project inertia.
Unseen dependencies
A workload moves alone, an integration breaks and you have to roll back with the operation stopped.
Redesign postponed
Everything gets rehosted to go fast, and the benefit that justified the migration is lost.
Compliance compromised
Regulated data in the wrong region, discovered after the move.
An unprepared team
Nobody knows how to operate the destination environment and dependency on the provider becomes total.
What it costs you in time, said upfront.
An assessment that does not state the commitment it requires ends up delayed. This is what we need from your side to deliver on time.
Two to four weeks
Two weeks in organisations of up to 50 employees; four between 51 and 300. The timeline is agreed before starting.
Scheduled interviews
Sessions with the owners of each system, with the people operating the infrastructure and with the business areas affected.
Read-only access
Queries against the platforms and existing documentation. At no point is a configuration modified.
A single point of contact
One person coordinating schedules and access. It is the factor that most affects hitting the deadline.
Whatever documentation exists
Server and application inventory, licensing contracts, consumption invoices and existing diagrams.
A closing session
The presentation of findings with leadership and the areas involved, where the roadmap priorities are agreed.
When it makes sense and when it does not.
It makes sense if…
You are evaluating a move to the cloud and need to know what is worth moving; you already migrated partially and the cost was not what you expected; a data centre contract is expiring; or you need to justify the migration investment to leadership.
Probably not if…
You already decided what to move and want the migration executed: go straight to Cloud. Or if the problem is the underlying design of your systems, that is evaluated by the Enterprise Architecture Assessment.
What you gain from the assessment.
A decision per workload
What to move, what to redesign first, what to repurchase and what to leave where it is, with the reason made explicit.
The real cost estimated
The destination cost with all its components, compared against what it costs today.
The lowest-risk sequence
What to migrate first to demonstrate value early without compromising the operation.
Visible dependencies
The groups of workloads that have to move together, identified beforehand rather than during.
Compliance settled
What the regulation demands on residency and processing before a single record moves.
The capability gap
What the team has to learn or hire to operate the destination environment.
Why this evaluation and not a quote.
The difference is not in calculating what an instance costs: it is in saying what is worth moving and what it really costs to sustain.
Evaluation, not quote
A quote assumes the decision to migrate is already made. This evaluates whether it is worth it, workload by workload.
Full cost
The model includes egress, licensing and operation, which is where most business cases break.
Recognised frameworks
The evaluation rests on Well-Architected and on the standard classification of migration paths.
Provider independence
The recommendation is not shaped by whichever cloud provider would suit us to sell.
Nothing gets moved
Inventory, interviews and consumption analysis. No workload is migrated and no configuration is modified.
Continuity into execution
If you decide to proceed, the roadmap connects with Cloud without taking the inventory again.
As-Is, To-Be and the plan to get from one to the other.
Every assessment closes with the same structure, whatever the practice: where you stand today, where you need to be, what separates the two states and in what order that distance gets closed.
Current state — As-Is
The starting point surveyed with evidence, not declared in an interview: what exists, how it operates and how far it sits from what the business needs.
Target state — To-Be
Where the organisation needs to get to, defined with the business areas rather than imposed by the consultant. It is the benchmark everything else is measured against.
Gap analysis
Every difference between the As-Is and the To-Be, with everything required to close it: technology, processes, people, governance and budget. No gap is stated without what it demands.
Risk matrix
Each gap rated by probability and business impact, so priority does not depend on who pushes hardest but on what it costs to leave it open.
Work plan
The concrete sequence to reach the To-Be: what comes first, what it depends on, how much effort it takes and who should answer for each front.
Business alignment
The plan is presented and agreed with the areas involved. A roadmap signed only by IT does not survive the first quarter.
How what you receive is structured.
The central deliverable is a report with a fixed structure, designed so leadership reads the first pages and the technical team works with the rest.
Executive summary
Two pages: what is worth moving, what is not, the estimated destination cost and the expected saving or overrun.
Workload inventory
Each application with its recommended migration path and the reason behind the decision.
Dependency map
Which workloads have to move together and what breaks if any of them travels alone.
Cost model
Current cost against destination cost, with compute, storage, egress, licensing and operation.
Migration roadmap
Sequence by waves, prioritised by risk and by demonstrable early value.
Immediate actions
Optimisations that can be applied today, with or without migrating.
What you receive at the end.
- Current state (As-Is): workload inventory and readiness evaluation across each of the eight fronts.
- Dependency map between systems and groups that have to migrate together.
- Compliance and data residency diagnosis for the workloads evaluated.
- Target state (To-Be): recommended destination per workload and cloud operating model, agreed with the owning areas.
- Gap analysis between the As-Is and the To-Be, with each gap, its evidence and everything required to close it: architecture, compliance, cost and team capabilities.
- Risk matrix: each migration wave rated by probability of failure and impact on the operation.
- Destination cost model, with all components and compared against the current cost.
- Evaluation of the team's capability gap to operate the destination.
- Work plan to reach the To-Be: migration by waves, prioritised by risk and value.
- Optimisation actions applicable without migrating.
- Executive presentation for committee and leadership.
- Alignment session with the areas that own the systems.
About the Cloud Readiness Assessment.
What exactly do you evaluate?+
How does it differ from cloud consulting?+
Do you recommend a particular cloud provider?+
Does the cost estimate include everything?+
What if we already migrated partially?+
Do you migrate anything during the assessment?+
Who should take part on our side?+
How often should we repeat it?+
Know what is worth moving before moving anything.
Book your Cloud Readiness Assessment and get the workload inventory with its migration path, the real estimated destination cost and a roadmap by waves.
Book my assessment → See the Cloud →