Find One Assessment That Said Stay On-Premises
Ask any cloud readiness assessment provider for one report that recommended leaving a workload where it was. Many can't: most are a sales pitch wearing a diagnostic's name. Ours works the other way. We catalogue every server and app you run, test what your network can carry, and hand you a verdict per workload before touching our wider cloud services.
Places A Cloud Assessment Can Quietly Cut Corners
Ask to see the report before you commission the work. If a provider cannot show you one that ever named a workload to keep on-premises, here is what else it probably skipped.
A Verdict Decided Before Diagnosis
A pitch dressed as a diagnostic starts from "move everything" and works backward, so the discovery workshop becomes a formality rather than the thing that actually decides anything.
No Dependency Mapping
Skip tracing which applications, databases and integrations depend on each other and you migrate in the wrong order, breaking a system nobody flagged until it is already offline.
No Compliance Or Residency Check
Cost and technical fit get assessed, data residency and access control rules do not, which leaves the one question a regulator actually asks unanswered.
PAID FOR, NEVER ANSWERED FOR
Perpetual licences and hardware under contract get ignored, so the report never says whether it's worth double paying. Where the honest answer is to move, there's its own scoped piece of work.
On their own, these are corners cut. Together they mean a verdict that was decided before the discovery call even happened, a migration order that breaks a system nobody flagged until it's already offline. As your cloud assessment partner in Johannesburg, we map the dependencies and the sunk cost before we recommend anything, so the answer is the honest one, not the one the pitch started with.
What Actually Happens Inside A Cloud Readiness Assessment
Six stages run between the kickoff call and the report landing in your inbox, each one building on what the last one found rather than jumping straight to a recommendation.
Discovery Workshop
We catalogue every workload, server, application and integration currently running, and confirm who inside the business actually owns each one.
Dependency Mapping
We trace which applications, databases and services depend on each other, so migration order gets set by what breaks first, not by convenience.
WORKLOAD SORTING
Every workload is sorted into lift and shift ready, needing re-architecture before it can move (often into a hybrid cloud environment), or staying on-premises for a stated reason.
Network And Bandwidth Check
We test whether your current internet and WAN links can carry the traffic each workload will generate once it sits off-site, not just what it uses today.
Licence And Cost Review
Existing perpetual licences and subscriptions get compared against projected cloud running costs, catching anywhere you would end up paying twice for the same capability.
Compliance And Data Residency Check
Data sets carrying residency, encryption or access control requirements get flagged before classification, not discovered after a workload has already moved.
The Proof Behind Every Cloud Readiness Verdict We Give
A verdict only means something if you can check it against what actually happens on your network. Every assessment we run ends in a written report, not a conversation, so what gets recommended for each workload is something you can hold up and question line by line.
The Verdict Table
Every workload gets its own row: move, re-architect first, or stay on-premises, with the reason written in plain language next to it rather than buried in a technical appendix nobody reads.
THE NUMBERS, NOT A PROJECTION
A real before-and-after cost comparison from a completed assessment, actual monthly figures, not a projected savings percentage, so you can see what “proof” looks like before you commit to the process.
What We Chose To Keep
A real example from a past assessment: a specific workload we recommended keeping on-premises, and the technical or compliance reason behind it, proof the report doesn’t default to “move everything” regardless of what it finds.
Compliance Checked Before Cost
Data residency, encryption and access control requirements get checked against each workload before it’s classified, not assumed away because the technical fit looks good. Where a requirement needs formal sign-off, it’s flagged as its own scoped piece of work.
What Sets The Price Of A Cloud Assessment
There is no flat per-workload fee, because the right scope depends on what is actually running in your environment, not a generic checklist. Four things move the number up or down.
01 Number of workloads, servers and applications in scope
02 How much discovery access the engagement actually needs
03 Compliance and data residency complexity across your data sets
Who This Is For
This suits a Johannesburg business still running on-premises or hybrid infrastructure, undecided about what should move and when, especially with a hardware refresh looming or a Microsoft 365 rollout that never mapped what the core line-of-business apps and file servers would need. If you are already cloud native, or already know exactly what you want built, that decision sits with Private, Public & Hybrid Cloud instead of an assessment.
How It Works
Frequently Asked Questions
Will this just tell us to move everything to cloud?
No. Ask any provider pitching a cloud readiness assessment to show you one report that ever recommended keeping a workload on premises. If they can’t, it was a sales pitch, not a diagnostic. Ours ends in a workload by workload verdict, and some of those verdicts say stay, which is often the start of a hybrid cloud setup rather than a full migration.
What do we actually receive at the end?
A written report: a verdict on every workload we assessed, a cost comparison against what you’re paying now, and a phased roadmap ranked by dependency and risk. You own it outright, whether or not you use us to carry out the migration and implementation work afterward.
How long does it take, and does it disrupt our systems?
Discovery workshops are scheduled around your team’s availability, and dependency mapping works from what your systems already tell us, not by poking around production during business hours.
Do you check compliance and data residency, or only cost?
Both. Every workload is checked against its data residency, encryption and access control requirements before it’s marked ready to move, not just priced against a cloud subscription and called suitable.
Does the assessment fee come off a later migration project?
Either way, the report is yours to act on with or without us.
What happens to the hardware and licences we've already paid for?
The report accounts for what you’re currently licensed and own before it recommends anything, so a move verdict comes with what that move actually costs you against what you’d otherwise be paying twice for.
The Verdict That Decides What Moves And What Stays For Good
Get your verdict, then book.