Audit and clean the CRM
Finds duplicates, missing fields, stale deals, wrong stages and orphan contacts, and returns a fix list by risk. Writes nothing without approval.
crm-hygiene-audit/SKILL.mdDownload- name
crm-hygiene-audit- description
- Use this skill when the CRM feels unreliable. It reads deals, contacts and companies and returns a fix list grouped by risk: duplicates, missing fields, stale deals, deals in the wrong stage and contacts without an account. Each fix shows the record, the evidence and the proposed change. Nothing is written without approval.
- license
- CC-BY-4.0
Audit and clean the CRM
This skill audits a CRM and returns a fix list, highest risk first, with the evidence for every line. Use it before a forecast, before importing a list, or when sellers stop trusting the CRM. You approve fixes by line or by batch, and it keeps the old values so every change can be reversed.
Inputs
- CRM access (read), or CSV exports of deals, contacts and companies with record IDs, owner, created date and last activity date. Without access, ask for the exports; one file per object is enough.
- Scope: the whole CRM, one pipeline or one owner. Above about 5,000 records, run it one pipeline at a time.
- Required fields. Default: amount, close date, owner and next step date on open deals; email and company on contacts; domain on companies. The user can add or remove fields.
- Stage rules: what must be true for a deal to sit in each stage. If none exist, use evidence checks: "meeting held" needs a past meeting, "proposal sent" needs a proposal file or note, "closed won" needs an amount and a close date.
- Stale thresholds. Default: no activity in 30 days, or more than 45 days in the same stage.
Steps
Inventory. Count records per object, pipeline and owner, and note the export date. Every finding is as of that date.
Duplicates. Companies: same domain after removing "www" and the protocol, or same name after removing legal suffixes (Inc, LLC, Ltd, Ltda, S.A.) and punctuation. Contacts: same email, case ignored; then same name at the same company. Deals: same company, similar name, both open. Give each match a confidence: an exact email or domain is high, a name alone is low. Propose which record survives (the one with the most activity, then the oldest). Treat every merge as permanent, and read your CRM's own documentation on merging before the first one, because what can be undone differs by vendor.
Missing fields. For each required field, count the gaps and list the records, late-stage deals first.
Stale deals. Open deals past either threshold, with the last activity and its date.
Wrong stage. Deals whose stage fails the stage rules, open deals with a close date in the past, won deals with no amount, and early-stage deals far older than the pipeline's usual cycle.
Contacts without an account. Propose the company from the email domain when that company exists in the CRM. Skip personal email domains (gmail.com, outlook.com and the like) and list those contacts for a person to check.
Group by risk.
High: problems that send a wrong message or a wrong number, such as duplicate contacts both in active sequences, opted-out contacts in a sequence or list, open deals past their close date, and won deals with no amount.
Medium: missing fields on open deals, wrong stages, stale deals.
Low: contacts without an account, formatting, duplicates among closed records.
Write the fix list. One line per fix: ID, record, problem, evidence, proposed change, and the owner who should confirm it. Group identical fixes into batches so the user can approve "all 14 close date fixes" in one answer.
Apply in small batches, after approval. Apply 25 changes at a time, read the records back to confirm, and keep a log with the old and new value of every field. Hand the log over at the end as the undo list.
Output
CRM audit · export of 2026-11-20 · Sales pipeline · 1,240 contacts, 310 companies, 86 open deals
Summary: High 9 · Medium 31 · Low 44
HIGH
| ID | Record | Problem | Evidence | Proposed change | Confirm |
| H1 | Dana Ruiz (2 records) | Duplicate, both in active sequence | same email, IDs 4411 and 5820 | Merge into 4411, stop 5820 | you |
| H2 | Vale Alto, fleet rollout | Close date passed, still open | close 2026-10-31, last note 11-12 | Ask owner for the new date | Ana |
| H3 | Harbor Line Logistics, scanners | Won with no amount | stage Won on 2026-09-14 | Add amount from invoice | Ana |
MEDIUM
| M1 to M14 | 14 open deals with no next step date | batch: create "Set next step" task for each owner |
| M15 | Pinecrest, field pilot | Stage "Proposal sent", no proposal file or note | move to "Meeting held"? | you |
LOW
| L1 to L38 | 38 contacts without a company | 31 matched by domain, 7 personal emails to check |
Approve with: "H1, H3" · "batch M1 to M14" · "all low except L32"
Nothing has been changed.Guardrails
- Reads: deals, contacts, companies, activities and field history, or the exports provided.
- Writes: only the fixes the user approves, in batches of 25, with a log of every old and new value.
- Asks before: every merge, stage change, field change, deletion and association.
- MUST show the evidence for every proposed fix.
- MUST put anything that could message the wrong person or misstate revenue in the high-risk group.
- MUST keep the undo list and hand it over.
- NEVER delete a record. Propose archiving or merging, and let the owner decide.
- NEVER merge on a name match alone.
- NEVER fill a missing amount, date or email with a guess.
Sources
- How do I run outbound without hiring an SDR?, ALTARA Insights: a CRM that stays current is part of the routine.
- How can a founder sell without a sales team?, ALTARA Insights: log every reply, including the no's.
Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/store
Use it with
-
Runs in ALTARAPlaybook Plan the dayRun the Monday pipeline review in ALTARAText ALTARA for the week's plan, count the activities, find deals with no next step and fix them by chat. The review uses no credits. 20 minutes every MondayRun it →
-
Runs in ALTARAPlaybook Keep the CRM currentKeep the CRM current from your chats with ALTARAALTARA reads client chats and your call notes, prepares stage, note and next task, and saves only after your yes. Free, with undo. 5 minutes at the end of each dayRun it →
-
Connection Keep the CRM currentHubSpotALTARA reads one HubSpot pipeline, read-only, and sends each change with a link to the deal. Your own AI reads the same records through HubSpot's MCP. Reads (rolling out)See how →
-
Connection Keep the CRM currentSalesforceThe ALTARA team connects Salesforce on request, read access first. Your own AI reads the same records through Salesforce's hosted MCP servers. Connected on requestSee how →
-
Connection Keep the CRM currentPipedriveALTARA keeps your Pipedrive pipeline current from the chat, after your yes. Your own AI reads the same deals through Pipedrive's MCP server. Reads and writesSee how →
-
Connection Keep the CRM currentZoho CRMThe ALTARA team connects Zoho CRM on request, read access first. Your own AI reads the same records through Zoho's pre-built MCP servers. Connected on requestSee how →