Your Customers Are Upgrading Expectations - Are You? A CTO's Perspective on Why SAP Business One Partners Need to Modernise

Partners don’t usually lose customers because SAP Business One 'doesn’t work'. They lose customers because the overall experience starts to feel dated, slow to change, or risky - and someone else shows up with a more modern, confident story.

From a CTO’s point of view, modernisation is fundamentally about three things:

• Reducing operational risk

• Increasing delivery speed and repeatability

• Enabling the experiences and integrations customers now expect by default

And for SAP Business One partners, that combination is no longer optional. It’s what protects your existing customer base and makes your proposition credible to new prospects.

Modernisation is risk management, not technology theatre

The biggest technical threats to partner businesses are gradual rather than dramatic:

• customers staying on older versions because upgrades feel painful

• environments drifting out of standard

• inconsistent backup and patching practices

• undocumented customisations

• ‘hero-based’ support where only one person knows how it works

• security expectations rising faster than internal capability

Modernisation is how you stop that drift. It’s how you turn ‘best effort’ into consistent engineering and operational discipline - so customers trust you with mission-critical systems.

Cloud hosting on a hyperscaler: standardisation, resilience, and control

Let’s address the big one: cloud hosting of SAP Business One on a hyperscaler. The value isn’t the logo. The value is what hyperscaler-hosted platforms make possible when delivered properly:

• consistent infrastructure patterns across customers

• resilience by design (not by luck)

• automation for provisioning and scaling

• centralised monitoring and alerting

• security baselines that can be evidenced, not just claimed

• repeatable backup and DR models that are tested, not assumed

Partners who standardise their hosting approach reduce variance, and variance is the enemy of scale. Standardisation equals fewer surprises, faster delivery, easier growth, and less painful support.

For customers, cloud standardisation typically means fewer outages, faster resolution times, and an overall sense that their ERP platform is ‘professionally run’. For partners, it means you can build a managed service that isn’t held together by late nights, improvisation and luck.

Staying current: upgrades are easier when you do them regularly

In most partner businesses, upgrades become difficult for one reason: they don’t happen often enough.

When customers fall behind on SAP Business One versions, they accumulate:

• more change to absorb in one go

• more compatibility questions

• more test scope

• more fear - because ‘everything might break’

From a technical standpoint, the fix is straightforward: treat upgrades as a lifecycle discipline, not a once-in-a-blue-moon event.

The goal isn’t to chase every patch. It’s to maintain a supported, predictable cadence with:

• clear version policy

• routine testing

• release notes translated into business value

• controlled rollouts

• a rollback plan that actually exists

This is especially important as SAP Business One continues to evolve around modern access and usability, particularly with the SAP Business One web client direction. If customers are stuck on versions that limit access to improvements, the product feels old - even when it isn’t.

Web client interface: ‘browser access’ is now the minimum expectation

Modern customers expect work to happen in browsers. They expect:

• remote-friendly access

• intuitive UI patterns

• smoother onboarding of new users

• less reliance on specific devices or office networks

Even when customers still use the desktop client heavily, the presence of a modern web experience changes perceptions. It also changes what’s possible: lighter workflows, broader access, and a path to more modern ways of working.

Partners who can confidently say, “Yes, you can adopt SAP’s latest web client developments - and here’s how we manage it safely,” immediately sound more future-proof than those who hesitate.

Version control and disciplined release practices are non-negotiable now

If your team builds add-ons, integrations, reports, or customisations, then modernisation must include how you engineer and release software. In ‘partner land’, the difference between “good” and “great” is rarely raw talent - it’s discipline.

Version control is foundational because it enables:

• traceability (who changed what, and why)

• repeatability (deployments that don’t depend on memory)

• collaboration (teams can scale beyond a couple of key people)

• testing and rollback (fail safely, recover quickly)

• auditability (a growing customer requirement, not a luxury)

Without it, you can deliver the work, but you can’t deliver work reliably at scale.

And reliability is what customers interpret as professionalism.

Environment consistency: dev/test/prod drift kills quality

A huge proportion of delivery pain comes from environment inconsistency:

• different patch levels

• slightly different configurations

• missing dependencies

• ‘special’ customer-specific exceptions

• manual steps no one wrote down

Modernisation is about reducing those variables.

When partners standardise environments, especially in cloud-hosted models, they reduce the surface area for defects and reduce the time spent diagnosing issues that shouldn’t exist in the first place.

This isn’t glamorous work, but it’s what turns delivery into a machine instead of a series of one-off miracles.

Security and governance: customers now expect evidence, not reassurance

Security expectations have shifted. Customers want to know:

• how you monitor

• how you patch

• how you handle identity and access

• how backups and disaster recovery are run

• how you isolate environments

• how you log and investigate incidents

Partners who modernise on a hyperscaler and standardise security baselines can answer these questions with confidence and, more importantly, with proof.

That reduces procurement friction and makes it easier to win deals where IT leadership is involved.

Modernisation enables better integrations and better customer outcomes

SAP Business One rarely lives alone anymore. Customers expect integrations with:

• eCommerce

• WMS and logistics

• CRM

• reporting platforms

• banking and payments

• automation tools

A modernised platform with disciplined engineering practices makes integrations easier to build, easier to maintain, and less likely to break during upgrades. That improves the customer experience and reduces support load, which is another underrated win for partner operations.

Closing thought

From a CTO’s perspective, modernisation is how you make SAP Business One feel current, safe, and adaptable, without turning every change into a high-risk event.

Partners who build a standardised cloud platform, keep customers on a sensible lifecycle cadence, and adopt disciplined delivery practices, will be the partners who scale - and the partners customers stick with.

If you’d like to compare notes on what ‘practical modernisation’ looks like in the real world, from hyperscaler hosting patterns to upgrade cadences and release discipline, at Cloud4Partners we’re always open to a peer-to-peer conversation and happy to share what we’ve seen work well.

- Steve Welsh
CTO, Ascarii & Cloud4Partners

CTO Sidebar: The Modernisation Minimum Standard (10 checks)

A practical checklist SAP Business One partners can use to baseline their platform and delivery discipline.

1. Supported version policy is defined (and enforced)
   Every customer is on an agreed supportable SAP Business One version range, with clear timing for updates.

2. Predictable upgrade cadence exists
   Upgrades are planned as smaller, routine releases - not multi-year “events” with high risk.

3. Cloud platform is standardised (preferably on a hyperscaler)
   Environments follow a repeatable reference architecture (networking, compute, storage), not one-off builds.

4. Backups and DR are automated and tested
   Backups aren’t just “configured”. Restore tests and DR drills happen on a schedule with documented outcomes.

5. Monitoring and alerting are centralised
   Performance, availability, disk, and key service health are monitored with actionable alerts (not noisy dashboards).

6. Security baseline is consistent and auditable
   MFA, least-privilege access, patching policy, vulnerability handling, and logging are standard and evidenceable.

7. Dev / test / prod environments are controlled
   Environment drift is minimised; configurations are documented; changes are tracked; “it works in dev” is not accepted.

8. Version control is mandatory for all custom work
   Add-ons, integrations, scripts, and config artefacts live in Git (or equivalent), with review and traceability.

9. Release process is repeatable, with rollback
   Releases have a checklist, a deployment method, a verification step, and a rollback plan that’s been proven.

10. Integration design is upgrade-safe
    Integrations are documented, monitored, and designed to survive platform changes without breaking silently.

If you can’t evidence these 10 checks across your customer base, modernisation isn’t a programme - it’s your next operational priority.