New software should feel like progress. More often, it feels like risk. If your current system does the job, even badly, the thought of replacing it can seem like an upheaval you don’t need.

That caution is reasonable. Most people have lived through at least one implementation project that ran long, cost more, and delivered less. So before we talk about hurdles, it’s worth being honest about what cloud actually is because a lot of what you’ve been told isn’t quite right.

“Cloud is just someone else’s computer.” It’s a good joke, and for some products it’s true. Plenty of vendors have taken old software, moved it into a hosted environment, and called it cloud. Nothing about the system changed except the address. You still face the same upgrade projects, the same specialists, the same waiting.

A true cloud platform is built differently from the ground up. Your configuration is stored separately from the product code. That’s why upgrades arrive without disruption, and why the system can change when your business does. The hosting is the least interesting part. What matters is who gets to change the system, and how quickly.

“Cloud means giving up control.” In practice, the opposite is usually true. With a legacy system, your logic sits inside code you can’t see. When something looks wrong, you raise a ticket and wait. On a configurable cloud platform, every calculation is visible and traceable. Your own domain experts can open it up, check it, and fix it. That’s more control, not less. And the security question has a clear answer, too: an enterprise-grade platform provides the accreditation, resilience, and audit trail that most in-house server rooms can’t match.

“Cloud is a rental trap.” The fear is that subscription costs creep up until you’re paying forever for something you never own. But compare it with what you’re paying now. Infrastructure, licences, consultants for every change, and a major upgrade project every few years. A cloud subscription rolls all of that into one predictable cost, and you only pay for what you use. The money doesn’t disappear. It just stops going on plumbing.

Once you see cloud this way, the three classic implementation hurdles start to look very different.

Your current system is probably heavily customised. Some of it was built in from day one. Some of it grew over years as new assets, partners, and reports were added. And some of it lives in spreadsheets, quietly filling the gaps.

Unpicking all of that and rebuilding it in a new system sounds formidable. On a traditional system, it is. You’d be choosing between the sky-high cost of a bespoke build or forcing a generic product to fit.

A configurable platform removes that choice. Your requirements are built through configuration, using standard spreadsheet functions and formulas your team already knows. No software development. No specialist coding skills. The people who understand the work, your hydrocarbon accountants and production engineers, build the solution that reflects it. And because they built it, they can change it whenever the business needs to.

In our experience, budget is the first objection. It’s hard to make the case for new software when the current system still works.

But “it still works” hides the real cost of staying put. What do you spend on consultants every time something changes? How hard is it to train new people on an ageing system? What will the next upgrade project cost, and how long will it take? Those numbers rarely appear on one invoice, which is exactly why they’re easy to ignore.

A cloud subscription puts them all in one place. Infrastructure, hosting, security, and every upgrade are included, with no separate upgrade projects to fund. Your budget becomes visible and predictable, and your IT team stops firefighting infrastructure and starts adding value. Let the vendor worry about uptime, resilience, and disaster recovery. That’s what you’re paying them for.

In our experience, budget is the first objection. It’s hard to make the case for new software when the current system still works.

But “it still works” hides the real cost of staying put. What do you spend on consultants every time something changes? How hard is it to train new people on an ageing system? What will the next upgrade project cost, and how long will it take? Those numbers rarely appear on one invoice, which is exactly why they’re easy to ignore.

A cloud subscription puts them all in one place. Infrastructure, hosting, security, and every upgrade are included, with no separate upgrade projects to fund. Your budget becomes visible and predictable, and your IT team stops firefighting infrastructure and starts adding value. Let the vendor worry about uptime, resilience, and disaster recovery. That’s what you’re paying them for.

Implementation fear is the biggest barrier to change, and it’s built on an old picture of what implementation involves. Cloud changes that picture. Configuration instead of coding. Small teams instead of armies. One subscription, not a stack of hidden costs.

The real question isn’t whether you can afford the change. It’s what staying put is quietly costing you.

If you want to dig into how the platform model works, start with Why PaaS. And if you’re wondering what an implementation actually looks like in practice, we’ve laid it out on our Implementation page.