#12🗄️ DataPainful

No Duplicate Rules: 14,000 Duplicate Accounts Later

“Launched an org without duplicate matching rules. Users created duplicates for a year. Cleanup took three months.”

What Happened

Set up a new org for a client. Configured everything — page layouts, profiles, automation. Never set up duplicate matching rules because 'we'll do that in phase 2.' Phase 2 never came. A year later the client had 14,000 Accounts and roughly 4,000 of them were duplicates. Sales reps were calling the same prospect twice. Reports were inflated. We had to buy a third-party dedup tool and spend three months merging records.

The Wrong Way

// Setup → Duplicate Management → "We'll do this later"
//
// Matching Rules: None configured
// Duplicate Rules: None configured
//
// One year later:
// "Acme Corp" — 3 records
// "Acme Corporation" — 2 records
// "ACME CORP." — 1 record
// All different owners. All with activities.
// All in different pipeline reports.

The Right Way

// Setup → Matching Rules:
// Standard Account Matching: ENABLED
//   Match on: Account Name (Fuzzy: Exact + Company Name)
//   + BillingCity + BillingState + Phone
//
// Setup → Duplicate Rules:
// Account Duplicate Rule: ACTIVE
//   Action: Alert (warn user, don't block)
//   Report: Duplicate Record Report (weekly review)
//
// Day ONE of every org setup. Not phase 2.
// Not "later." Day one.

The Lesson

Set up duplicate rules on Day 1. Every single org. The cost of deduplication later is 100x the cost of prevention now.

Share this mistake on X

Don't make this mistake.

Hire someone who already did.

View Consulting →

#11 Mass Update With No Backup: The 'Undo' Button That Doesn't Exist Hard Delete When Soft Delete Would Do #13

Enjoyed this? Get more like it.

Glen's Musings — AI, investing, and building things. Occasional. Free.