hub - CRM cleanup before and after examples
CRM cleanup before and after examples
Use before-and-after examples to normalize CRM lead sources, owners, stages, and import fields. This page is built for RevOps, sales ops, CRM admins who need to make CRM cleanup rules visible and reusable.
Where this workflow helps
Common friction
- CRM fields drift over time
- cleanup rules live in people heads
- imports create new inconsistencies
- sales reports become unreliable
Repeatable process
- Paste raw values and desired standardized values.
- Ask for a mapping table and exception rules.
- Review rows that cannot be mapped confidently.
- Use the mapping as the future cleanup reference.
Reusable prompts
Open prompt packCreate before-and-after CRM cleanup examples for these field values.
Normalize lead source, owner, and lifecycle fields into an import-ready table.
Flag values that need manual review instead of guessing.
Tools to compare first
Full comparison| Tool | Best for | Use it when | Link |
|---|---|---|---|
| Zapier | Connecting tools and automating repeatable steps | Good for sending alerts, moving data between apps, and reducing routine manual work. | Visit |
| Make | Visual automation and multi-step flows | Fits users who want more control over branching automation and data routing. | Visit |
| Notion AI | Docs, SOPs, and reusable team knowledge | A natural home for prompt libraries, checklists, and lightweight knowledge bases. | Visit |
| Airtable AI | Structured records and lightweight databases | Useful when the workflow needs a database shape before automation or reporting. | Visit |
Mistakes to avoid
Make the prompt more specific, keep the source data visible, and review the output before using it in a live workflow.
Make the prompt more specific, keep the source data visible, and review the output before using it in a live workflow.
Make the prompt more specific, keep the source data visible, and review the output before using it in a live workflow.
Make the prompt more specific, keep the source data visible, and review the output before using it in a live workflow.