
Read Time: 5 Minutes
Your CRM looks messy.
So someone cleans it.
And in one night, years of work are gone... with no way to get it back.
Short answer: A CRM cleanup deletes good data when one person can bulk-change records with no rules. Before any mass update, ask 5 questions: what problem it fixes, who uses the field, is there a backup, did you test it on 10 records, and who signed off. If any answer is "I don't know," wait.
This one comes from my podcast with Leslie Venetz. She spent 15 years in sales as a rep and a first, second, and third line sales leader. She now runs a sales-led go-to-market agency and wrote the USA Today bestseller Profit Generating Pipeline.
How does a CRM cleanup wipe out years of data?
It happens when someone means well, sees data that looks wrong, and fixes all of it at once. Nobody asked why the data looked that way. Nobody made a backup. Nobody had to approve it. One bulk update runs overnight, and the work is gone before anyone in sales even notices it changed.
That's exactly what happened to Leslie's team.
They spent years saving real addresses for each contact. Where people actually lived and worked. They used it for handwritten mail during COVID and small in-person exec dinners after.
Then a new Salesforce admin saw the contact addresses didn't match the account addresses. In Leslie's words:
"he took it upon himself to update every single contact field to match the account level headquarter address and deleted like three years worth of work overnight and then couldn't bring it back."
And she was clear he was a good guy. "Sweetest guy, so nice."
The admin wasn't the problem. The missing rule was.
What should we check before anyone bulk-updates the CRM?
Use a 5-question check before any mass update, import, or "cleanup." It takes 10 minutes. It forces someone to ask the people who use the data, make a backup, and test small first. If any answer is "I don't know," the change waits. That one rule would have saved Leslie's team 3 years of work.
- What problem does this fix, and who asked for it?
- Who uses this field today? Ask sales, CS, and marketing first.
- Did we export a backup of every record we're about to touch?
- Did we test it on 10 records first?
- Who signed off? One person from sales, one from ops.
Then make it stick:
- Paste the 5 questions into your ops Slack channel.
- Name one owner who signs off on every bulk change.
- Set a weekly export of contacts and accounts.
- Ask your ops person today: "If someone bulk-changed our CRM tonight, could we undo it?"
Why does sales data look "wrong" to ops?
Because reps track things for reasons ops can't see from the data alone. A field that looks like junk is often a rep's workaround for something the system doesn't support. The fix is a conversation, not a cleanup. Reps explain their logic. Ops asks before they change it. Both sides assume the other one has a reason.
Leslie put it this way:
"Sales people do usually have a method to their madness"
But she puts the job on both sides. Sellers have to say what they're trying to do. "it behooves sellers to explain their logic. Like instead of just demanding, I need another field."
And ops has to ask first. Before you wipe all the contact addresses and replace them with account addresses, "like have that conversation."
One thing I've seen work: have ops people shadow other teams once a quarter. You see why reps skip a field that takes 20 clicks to reach. You see which fields nobody uses in a report. It's hard to break something when you've watched someone use it.
How do you get reps to actually update the CRM?
Tell them it's part of the job they're paid for. Reps often treat the CRM as something for them, so if they don't need a note, they skip it. But their pay includes building knowledge the company keeps. That data drives better segments, better messages, and better service for the next rep and the next customer.
Leslie's line to her own teams:
"a part of what they are being paid to do is create an institutional knowledge repository."
And the short version:
"it's not all about you. Update your CRM."
She also said "Data hygiene is everybody's responsibility." That cuts both ways. Reps fill it in. Ops protects it.
Can AI fix our messy CRM and pipeline for us?
Not by itself. AI makes you faster at whatever you already do. If your data is a mess and your process is unclear, AI just makes more mess, faster. Get your strategy, process, and clean data in place first. Then add AI on top, where it can actually help.
Leslie sees teams use AI to just do more. More emails. More calls. More reps.
Her rule: "more is not a strategy."
She says "too often founders and sales leaders are trying to just use a new piece of AI as a band-aid." The order that works:
- Build the strategy.
- Build repeatable processes that support it.
- Get the team bought in and trained.
- Then add AI.
Same goes for outbound. She says "without segmentation, your outbound is always going to fail, period." Use AI to find real signals and better segments first. Not to send more.
When should sales get creative, and when should they stick to the process?
Get the baseline first. Reps need a repeatable process and clean data so you know what "good" looks like. Once you have that, creative ideas become safe tests. You can see what worked, what didn't, and keep going in the right direction. Without the baseline, creativity is just guessing.
Leslie's version: "you have to have clean and clear data". Then you can be creative and actually tell if it worked.
This is why the CRM matters to sales, not just ops. It's how you know your baseline.
More on this: Sarah left. Now 3 things broke., How do I add Salesforce validation rules without blocking my reps?, and How do I know if my Salesforce org is Agentforce-ready?
Bottom line
Clean data is good. Clean data with no backup is risk.
Ask the 5 questions. Name one owner. Back it up weekly. And make reps and ops talk before anyone "fixes" anything.
Frequently asked questions
Can you undo a bulk update in Salesforce?
Usually not. Salesforce has no built-in undo for a mass update. If field history tracking was on for that field, you may be able to piece old values back together, but it's slow and often incomplete. That's why a backup export of every record you plan to touch is step 3 of the check.
Who should approve bulk changes to the CRM?
Name one owner who signs off on every bulk change, plus one person from sales and one from ops. The point isn't red tape. It's making sure someone who uses the data sees the change before it runs.
How often should we back up our CRM?
At least weekly for contacts and accounts, plus a one-time export right before any mass update. A weekly export is cheap insurance against a cleanup gone wrong.
Should our new admin clean up the CRM in their first month?
Let them find the mess, but not fix it alone. A new admin doesn't know why data looks the way it does yet. Have them list what looks wrong, ask the teams who use it, and run the 5-question check before changing anything.
Is a messy CRM a people problem or a process problem?
Usually process. In Leslie's story, a well-meaning admin deleted 3 years of work because there was no rule to stop him. Fix the rule, and the same people make better calls.
Want more of this? The Simply Scale newsletter drops every week: Subscribe here
Need help with Salesforce? Book a call: https://calendly.com/jordan-gosimplyscale/30min?utm_source=blog&utm_campaign=stop-crm-cleanup-deleting-years-of-sales-data
