Can you keep Salesforce and modernise everything around it?
Yes, whatever your org's configuration looks like underneath. Salesforce can stay your customer and pipeline system of record while a bespoke, real-time interface gets built on top of it — no rip-and-replace, no CRM migration, and nothing lost from the setup your business already runs on. This is what Sysgraft calls a graft: a precise join between a new intelligent layer and the systems you already own.
Should you replace Salesforce, or build around it?
For most £5m–£20m+ UK businesses running Salesforce, the honest answer is: build around it.
Salesforce is usually not the problem. It's a genuinely powerful CRM, built to be configured and extended, and for pipeline and customer management it does that job well. The problem is that even a heavily customised Salesforce org rarely shows leadership margin, delivery risk, or cash position alongside the pipeline — that data lives elsewhere, in the ERP or finance system Salesforce was never meant to replace. The frustration leaders feel isn't a reason to tear out an org that's often had years of configuration invested in it. It's a reason to add a layer that joins it to the rest of the picture.
Ripping out a working Salesforce org to solve a reporting and visibility problem is one of the most expensive mistakes a business can make: Salesforce implementations routinely represent significant sunk configuration and process investment, and unwinding that is rarely proportionate to a problem a graft would fix without touching any of it.
What connecting to Salesforce actually involves
Salesforce exposes several APIs suited to different jobs — REST for everyday record reads and writes, Bulk API 2.0 for large data volumes, and the Composite API for bundling several calls into one round trip. Which combination makes sense depends on the shape of the data being pulled, and that's a discovery-stage decision, not a default.
The number that shapes a build is the daily API limit, and it isn't a flat figure — it scales with your org. A common structure is a base allowance (100,000 calls per 24 hours for Enterprise Edition) plus a fixed number of additional calls per user licence, measured on a rolling 24-hour window rather than resetting at midnight. Bulk API draws from its own separate pool rather than sharing the REST/SOAP daily limit, with its own batch cap — which is usually the right tool once a pull goes beyond a couple of thousand records.
There's a second layer worth knowing about too: Salesforce's governor limits apply per transaction, not per API call, so a single REST request that triggers Apex automation can cascade through queries and operations that have their own ceilings. None of this is exotic — it's simply why "confirm the actual entitlement and automation in play" is a real discovery step for Salesforce, not paperwork.
Common questions about modernising around Salesforce
Can custom software sit on top of Salesforce?
Yes. A bespoke interface can draw live data from Salesforce through its REST, Bulk or Composite APIs and present it alongside data from your ERP and other systems, giving leadership one real-time view without changing how Salesforce itself works.
Can I get a real-time dashboard from Salesforce without replacing it?
Yes. A dashboard can read live from Salesforce — through whichever of its APIs actually fits the data volume — and sit alongside your other systems, whatever your org's automation looks like underneath.
Does Salesforce's API have limits worth knowing before a build?
Yes. Salesforce's daily API limit scales with your licence count — commonly a base allowance plus a fixed number of calls per user licence — on a rolling 24-hour window rather than a calendar day. Bulk operations draw from a separate pool with their own batch cap, which is usually the right tool for anything beyond a couple of thousand records at once. Confirming your org's actual entitlement is a discovery-stage task, not a guess.
Can I connect Salesforce to my ERP and see both in one place?
Yes. Grafting an interface across Salesforce and your ERP lets pipeline, delivery and finance data appear together — the single view that neither system gives you alone.
Does keeping Salesforce limit what AI can do later?
No. What limits AI usefulness is fragmented data, not which CRM you run, however heavily your Salesforce org has been customised. Once that data is joined into one accessible place, AI features have something genuinely coherent to work with — whatever your automation looks like underneath.
Modernising isn't migrating
The software industry has trained businesses to believe that "modernising" means a large, disruptive replacement project. It doesn't have to. Grafting a new layer onto Salesforce is modernisation without the migration — you move forward on visibility and capability while everything that currently works, and everything you've configured, keeps working.
See how the whole process works, step by step →
Get your AI Exposure snapshot Find out where your real constraint is — most often it isn't AI, and it isn't Salesforce