When Your Salesforce Admin Leaves (Or Your Partner Relationship Breaks Down)

For many UK charities and SMEs, Salesforce works well — right up until it suddenly doesn’t.

A common trigger is one of these events:

  • Your internal Salesforce admin leaves

  • Your Salesforce partner relationship ends

  • Support costs rise beyond what feels reasonable

What follows is often uncertainty, risk, and a lack of confidence in the system your organisation now depends on.

The Hidden Risk of a Single Salesforce Admin

Relying on one internal Salesforce admin can work — until that knowledge disappears with them. We regularly see organisations left with:

  • Little or no system documentation

  • Unfinished automations and flows

  • No clear understanding of what is custom, what is standard, and what is critical

The result is hesitation. Teams are afraid to make changes in case something breaks.

When a Salesforce Partner Relationship Fails

Sometimes the issue is not an employee, but an external partner. Typical problems include:

  • Poor handover or documentation

  • Custom solutions that only the partner understands

  • High ongoing costs with little transparency

  • Slow response times once the project is “complete”

This often leaves organisations feeling locked in — or worse, unsupported.

Legacy Code You Cannot Safely Change

One of the biggest risks we encounter is old hard-coded customisation, including:

  • Visualforce pages

  • Apex triggers and classes

  • Custom components built years ago

These assets are often:

  • Poorly documented

  • Built to older Salesforce standards

  • Not easily upgradeable

  • Untested or fragile

In many cases, no one is quite sure what they do — only that “everything depends on them”. This creates a real barrier to improvement and increases technical debt over time.

High Costs, Low Confidence

Another common theme is cost. Organisations tell us:

  • They are paying for support they do not fully understand

  • Small changes require expensive development work

  • There is no clear prioritisation or roadmap

Salesforce should support your organisation, not drain it.

What to Look for in a Replacement Salesforce Service

If you are sourcing a new Salesforce support provider, there are a few essentials:

  • Clear ownership and accountability

  • Willingness to audit and document the existing system

  • Sensible handling of legacy code, not blind rewrites

  • Transparent pricing and prioritisation

  • Ongoing admin support, not just project delivery

A good provider helps you stabilise first, then improve.

Salesforce Admin as a Service: Stability Without Lock-In

At Zon Projects, we support UK charities and SMEs who need to regain control of Salesforce after:

  • An admin departure

  • A partner relationship ending

  • Costs becoming unsustainable

Our Salesforce Admin as a Service provides:

  • Safe handover and system assessment

  • Documentation of existing automations and code

  • Pragmatic management of legacy Visualforce and Apex

  • Ongoing optimisation, integration, and reporting

  • Predictable monthly costs without long-term lock-in

We focus on making Salesforce understandable, stable, and adaptable again.

👉 If your Salesforce system feels fragile, expensive, or dependent on knowledge you no longer have, it is time to regain control.
Visit www.zonprojects.com to see how ongoing Salesforce admin support can stabilise and improve your Salesforce platform.

Next
Next

When Salesforce No Longer Fits Your Charity or SME Strategy