CRM CLEANUP PASS · FIXED SCOPE
Years of other people's imports. Duplicates everywhere, fields nobody defined, lifecycle stages that were never set up. We take the mess off your plate — every change logged and reversible, counts reconciled to ±0 — so you can show exactly what was done, row by row, if anyone asks.
New role, super admin access, and years of hands that didn't know the platform. Every contact marked as a lead. Properties nobody uses. Everyone expects you to fix it — nobody can tell you where to start.
You spent hours last week merging contacts by hand. This week there are more. Two reps called the same lead. Attribution doesn't add up.
Warming up since May, performance barely moves. A dirty base isn't the only cause of bad deliverability — but it's the one you can fix this week.
Acceptance criteria are agreed before work starts — and never softened afterwards.
Shape of a real change log entry (dummy data):
# changelog.csv — cleanup pass, demo dataset row_id,field,before,after,action 00412,email," bob@acme.com ",bob@acme.com,trimmed_whitespace 01033,[whole row],dup_of:00412,,merged 02177,email,bob+crm@acme.com,EXCEPTION,plus-tag vs base address → your decision 03402,email,,EXCEPTION,null-key → excluded # scripted identity, ±0: input(1821) = clean(1183) + merged(10) + exc(628)
Numbers above are from a demo run on synthetic data — labeled as such, because inventing client cases is how this industry got its reputation.
Small sample checks can be turned around quickly when the file fits. Larger cleanup work is quoted as a fixed-scope batch after we see the file, declared key and acceptance criteria.
We prepare the data so those decisions become safe: staged values, documented rules, flagged conflicts. Platform configuration itself stays on your side — we don't touch production systems.
≤10k per batch is a pricing/turnaround boundary, not a technical ceiling — bigger bases run as a series of scoped batches, or a larger fixed-scope engagement, after a paid pilot proves the rule set on a real slice of your data.
Anonymize it if you like — the method shows either way. We reply with either a small sample-proof path or a fixed-scope cleanup quote. Agencies with migration work should use the $750 migration-data QA pilot.
Reply within 24h · prefer email? hello@amessystems.com
Clean and map before the import — whatever gets imported now, you live with for years.