The Question
Should we fix Salesforce vs start over?
Your org is messy. People are frustrated. Reports don’t line up. The UI looks like it was built during a caffeine binge and never revisited.
So now you’re staring at the screen thinking:
“Is it easier to just start over?”
The Short Answer
In the fix Salesforce vs start over decision, 99% of companies should fix what they already have.
Rebuilds usually hide behind a few false positives that don’t hold up:
-
It’s too messy → lack of prioritization
-
No one uses it → adoption and design issues
-
It was built wrong → true, but not a reason to scrap everything
Why This Happens
This doesn’t happen overnight.
It builds slowly:
-
Requests get added without filters
-
Admins don’t have authority to say no
-
The system gets shaped around opinions instead of work
Eventually, the org drifts so far from reality that “starting over” feels like the clean answer.
It’s not.
3 Reasons to Actually Fix Your Instance
1. “Starting Fresh” Is Not Realistic for Most Businesses
What it is
A clean slate sounds amazing.
No clutter. No baggage. No bad decisions.
But that’s not how this works.
You don’t leave your problems behind, the come with you in the overhead compartment.
What’s actually happening
A rebuild assumes your business will:
-
Stop what it’s doing
-
Define perfect requirements
-
Clean all data
-
Retrain every user
All while continuing to operate.
That’s a massive ask that never lands cleanly.
Rebuilds get pushed for two reasons:
-
They generate more revenue for consultants
-
They look “correct” from a technical perspective
But business isn’t a textbook.
What this looks like in real life
You start a rebuild thinking:
“This time we’ll do it right.”
Three months later:
-
Requirements are incomplete
-
People are missing sessions
-
The same voices are driving decisions
And guess what?
You rebuild the same problems.
Why it matters
In the fix Salesforce vs start over decision, this is the biggest trap.
Rebuilds don’t eliminate problems.
They recreate them with a fresh coat of paint because people are rarely aligned with the time and energy it takes to pull them off correctly.
2. Clean Ups Can Change Your Culture
What it is
Fixing Salesforce isn’t just technical.
It’s cultural. If you do it right it has a second order impact on everything working there.
Leadership actually has to listen and make the right changes for a clean up to work.
Salesforce is not a toy. It’s a tool.
What’s actually happening
When you clean up your system, you’re doing something powerful:
You’re making people’s jobs easier.
Instead of dragging everyone into a rebuild, you’re removing friction from the work they already do.
That lands differently.
Real examples
I worked in an org where Salesforce was wildly overbuilt:
-
Too much of everything
-
Fields
-
Automations
-
Dynamic Page Layouts
- Multi-select Lists
-
Every week the good idea fairy was coming around to sprinkle more ideas and complexity into our work.
Leadership decided to rebuild.
Same people made the decisions.
Same mindset.
Same outcome.
The new org had worse adoption than the original, but the banner at the top switched from a shade of red to blue.
I’ve also seen the opposite play out.
Same type of org:
- Too much of everything
- Fields
- Automations
- Layouts that made no sense
But instead of rebuilding, leadership made a different decision.
They stopped adding.
They started removing.
They got honest about what actually mattered and what didn’t.
Within a few weeks a pattern emerged.
There were really only 3–4 major issues causing 80% of the frustration.
Most of them were self-inflicted:
-
Over-required fields
-
Automations stepping on each other
-
Page layouts trying to do too much
They stripped those out.
Simplified the flows.
Made the system easier to use instead of more “complete.”
What happened next was predictable.
People stopped complaining.
Usage went up without forcing it.
Reports started making sense again.
And most importantly people went back to doing their jobs instead of fighting the system.
No rebuild.
No 6-month project.
No “this time we’ll get it right.”
Just removing what never should’ve been there in the first place.
Why it matters
When you choose fix Salesforce vs start over, you’re choosing between 2 outcomes.
Fixing the system – improve daily work, builds trust, show that you’re listening, and getting the business more of what it wants.
Rebuilding the system – disrupting everything, burning time, and risk repeating history.
If you want adoption, cleaning up wins every time.
3. It’s Functionally Easier
What it is
Fixing removes.
Rebuilding adds.
One is inherently simple.
One is extremely complex.
What’s actually happening
Rebuilds turn into endless requirements meetings, future state diagrams, and cross-functional debates.
Fixing aligns with classic lean thinking principles by removing unnecessary fields, simplifying layouts, and cleaning up automation.
Why it matters
This is where the fix Salesforce vs start over decision becomes practical.
Fixing:
-
Faster impact
-
Lower cost
-
Immediate usability improvements
Rebuilding:
-
Long timelines
-
Expensive
-
Delayed results
Also fixing gives you immediate feedback.
Rebuilding delays feedback until everything is already built.
That’s a dangerous and expensive place to be.
The Pattern Behind It
Here’s how this usually plays out over time.
Year 1:
Salesforce gets implemented. Everyone is optimistic.
Year 2:
-
New managers come in
-
New requests pile up
-
Fields and automations expand
Year 3:
-
People leave
-
Knowledge disappears
-
New admins inherit the mess
They don’t push back.
Why?
Because they like eating.
And sparring with the VP of Sales isn’t a good way to continue eating.
Year 4:
Now you have:
-
Overlapping logic
-
Broken automation
-
Confusing UI
And starting over begins to look very appetizing.
That’s how the fix Salesforce vs start over conversation begins every single time.
The Common Mistake
Companies treat this like a technical decision, but it’s not.
It’s a work design decision.
Salesforce reflects how your business operates.
If your processes are unclear or inconsistent, a new org won’t fix that.
Starting over without fixing the underlying work just moves the problem somewhere else.
What To Do Next
If you’re leaning toward fixing (which you should be), do this:
1. Check Utility Rates on Fields
If a field is used less than 10% of the time:
Remove it.
No debate.
It may sting a little, but it’s the first step in moving forward.
2. Run a Gemba Walk
Gemba walks are amazing for seeing work in action.
Watch people use Salesforce.
Don’t explain it.
Don’t defend it.
Just observe:
-
Where they struggle
-
Where they hesitate
-
Where they work around the system
Then remove those issues.
3. Reinforcement Analysis
Compare:
-
What’s in Salesforce
vs
-
What leadership actually cares about
I don’t mean care about in the emotional “I made this so do it” sense. I mean in the consistently reinforced in meetings, reviews, and compensation structure sense.
Salesforce should match that tightly.
Remove everything else.
These three steps outperform rebuilds consistently.
They’re simple.
They’re effective.
They just require honesty.
Frankly, you can do them without anyone’s help (unless you need technical muscle for changes).
Closing Thought
Rebuilds aren’t bad.
They’re just unnecessary for most businesses.
They require:
-
Full requirements gathering
-
Data cleanup
-
Retraining entire teams
-
Perfect execution
That all makes sense in fantasy land. Unfortunately, we live in the real world.
Fixing your system:
-
Removes friction
-
Improves usability
-
Aligns Salesforce with real work
Remember that Salesforce is a tool, not a toy.
It shouldn’t be endlessly rebuilt every time the good idea fairy wakes up and starts making suggestions.
If you’re stuck in the fix Salesforce vs start over decision and want to simplify what you already have instead of starting from scratch, reach out.
We’ll help you clean it up and make it actually usable.