Year-End CRM Cleanup: A 90-Minute Checklist

Two records for one customer, a proposal still marked open after the job was canceled, and a tag nobody remembers creating: these are useful places to start year-end CRM data cleanup. Each makes the next person’s work harder. Some can also send a contact into the wrong follow-up sequence.

Set aside 90 minutes for a small-team first pass. The goal is a reviewed batch of corrections and an assigned list of unresolved questions. A large database, uncertain recovery options, or conflicting customer records will need more time. Stop at each time limit and defer unfinished work instead of rushing a bulk change.

This checklist covers maintenance. If you later want to contact dormant leads, use the separate database reactivation guide for audience eligibility, messages, and campaign controls. Finishing cleanup does not authorize outreach.

Your 90-minute plan

Time	Task	What you should have afterward
0–15 minutes	Set scope and check exports	A verified export or documented gaps
15–30 minutes	Protect consent and map automation dependencies	A list of fields and records that need special handling
30–50 minutes	Review duplicate candidates	Approved pairs and a separate conflict queue
50–65 minutes	Review fields and tags	A short change list with dependency checks
65–80 minutes	Reconcile stale pipeline records	Owner-approved outcomes or dated review tasks
80–90 minutes	Validate the batch and assign follow-up	Validation results, pending checks, and named owners

Choose one person to make approved changes and another to review merges and ambiguous records. If you work alone, separate the review from execution and leave irreversible changes pending when you cannot verify them.

Minutes 0–15: Set scope and check your recovery copy

Choose a manageable slice, such as one pipeline or one recent import. Write down its filters, record count, location, export time, and owner. Keep a change log outside the CRM with record IDs, original values, proposed values, reasons, and reviewer decisions. Even adding a “cleanup” tag could affect an existing automation.

Export the selected contacts and separately capture the opportunity information you intend to change. Import each CSV into your spreadsheet with ID and phone columns set to text before loading the data. This helps prevent lost leading zeros or altered long values. Check column names, row counts, non-English characters, phone prefixes, and a few known records.

Treat a contact CSV as a reference copy, not a full account backup. Confirm whether it includes the selected custom fields, notes, consent evidence, and suppression states you need. Conversation history, attachments, workflow configuration, and active workflow positions may need separate handling. A file that opens successfully does not prove you could restore those relationships.

Before deleting or merging anything in SMBcrm, ask SMBcrm Support to confirm the applicable recovery options and what would remain missing after restoration. Do not assume a deleted-record recovery feature can reverse a merge or rebuild lost history. Keep deletion out of this first pass.

If the export is still processing or the recovery scope is unclear at minute 15, continue with a read-only review. Record proposed changes without applying them.

Minutes 15–30: Protect consent and inspect automation dependencies

Identify the records and fields used for email unsubscribes, SMS opt-outs, Do Not Disturb (DND), complaints, hard bounces, and wrong-number reports. Preserve the evidence behind those states, including the channel, collection source, date, and disclosure where available. Do not convert a missing value into “subscribed.”

Check a few suppressed records against the original source and your export. A new email address, corrected spelling, or merged record must not silently erase an applicable restriction. If two records disagree, hold the proposed merge and retain the restrictive treatment while the responsible person resolves the conflict. An email preference does not establish permission for SMS.

For messaging programs using Twilio, its Messaging Policy requires consent and a straightforward way to withdraw it. Verify the rules of your actual sending provider and applicable requirements separately. This maintenance session should preserve permissions, not decide that an old contact is newly eligible.

Next, list the automations, saved segments, forms, reports, and integrations that read the fields you plan to edit. In SMBcrm, contact tag changes require confirmation, but that confirmation does not establish that the resulting workflow activity is safe.

Review what adding or removing each tag, changing an owner, or moving a deal could trigger. Include enrolled contacts and queued actions. Do not assume switching a workflow to draft cancels everything already scheduled. If you cannot explain the downstream effect, defer the live edit.

Before any production changes in the next three steps, review the proposed behavior offline with fictional records. If an edit could affect an automation, require a controlled test approved by the account owner before applying it to customer records. Use an isolated setup with internal recipients and outbound integrations controlled. If that test cannot be completed within this session, defer the edit. SMBcrm’s workflow testing update confirms that tests execute real actions, including messages and record changes.

Minutes 30–50: Review duplicates before merging

Build a candidate list using matching identifiers, then inspect each pair. A shared email address or phone number is a reason to investigate. Families, office teams, and different people with the same name can legitimately share details.

Use a simple review sheet. These examples are fictional:

Candidate	Evidence	Decision
Contact A and Contact B	Same person confirmed by the owner; one has an outdated address	Review the surviving record and field choices
Contact C and Contact D	Same office phone; different names and roles	Keep separate
Contact E and Contact F	Same email; conflicting opt-out history	Hold for permission review

For a confirmed duplicate, identify the surviving contact and compare names, primary contact details, owners, custom fields, notes, documents, opportunities, and communication restrictions. Check active workflows before approval. Do not simply keep whichever record looks newer or has more filled fields.

SMBcrm’s contact merge update describes documents transferring from secondary contacts to the primary contact. That specific behavior is not a promise that every field or connected record will resolve as you expect. Review the merge dialog and verify the affected information afterward.

Treat a confirmed merge as irreversible. Ask the reviewer to approve the surviving ID and selected values before applying it. For this first pass, use individually reviewed merges; leave automated deduplication rules for a separate project with test evidence.

If a pair needs the account owner’s explanation, place it in the external review queue with a question and due date. Do not dismiss an unresolved duplicate candidate just to clear it from the screen.

Minutes 50–65: Simplify fields and tags without breaking references

Start with a few obvious inconsistencies. For example, your team might use estimate-sent, quote_sent, and proposal-out for the same event. Verify that they really mean the same thing before choosing a standard. A legacy campaign tag may be historical evidence rather than clutter.

For each proposed change, record:

• The existing name and the intended meaning.
• The preferred field or tag and who owns its definition.
• The forms, filters, workflows, integrations, and reports that reference it.
• The records affected and how you will verify the result.

Prefer correcting a documented value over deleting a field. Defer field-type changes, removal of historical source tags, and broad find-and-replace operations until dependencies are tested. Do not overwrite a known value with a blank during a cleanup import.

Standardize phone formatting only when the country is known. Avoid guessing missing country codes, names, dates, or company relationships. For dates, retain the meaning and timezone rather than merely making the spreadsheet look consistent.

Apply only the small, approved corrections whose downstream behavior has been checked. For the rest, leave the original data intact and assign the proposed mapping for review.

Minutes 65–80: Give stale pipeline records an honest status

Use an agreed business rule to find deals for review. “No meaningful activity for 60 days” is an illustrative filter, not a universal definition of a lost opportunity. Long buying cycles and scheduled future work can remain legitimate.

Ask the owner to check the last conversation, proposal, booking, and known outcome. For each reviewed opportunity, choose a next step supported by the record: retain it with a dated action, correct the stage, or close it with the appropriate reason. If nobody knows the outcome, assign a review task rather than inventing a loss reason.

Check whether two opportunities represent duplicate records or separate projects for the same contact. Contact deduplication and opportunity deduplication are different decisions. Reconcile values and owners without rewriting historical revenue to make the dashboard look tidy.

Review stage-change and status-change automations before saving. A closed deal might start onboarding, request a review, or stop follow-up. Make only changes whose consequences have been approved. Leave customer messages out of this maintenance session.

Minutes 80–90: Validate and hand off unfinished work

Compare the original and final counts for the selected batch. Reconcile the reduction caused by approved merges, verify surviving IDs, and spot-check the changed fields, attached information, and opportunity associations. Check the known suppressed records again. Document any mismatch before expanding the work.

Review automation logs and queues where changes were applied. Confirm that no unexpected enrollment or action occurred. Offline walkthroughs establish the intended logic; only an approved controlled test can show what the workflow actually does. If that evidence is missing, leave dependent changes pending.

Finish with a short handoff: what changed, what was deliberately deferred, each unresolved record or dependency, its owner, and a review date. For a large dataset, schedule additional batches sized to the team’s review capacity. A high-volume merge, retention purge, consent dispute, or integration rewrite deserves its own plan.

Bring the change log and unresolved questions to SMBcrm onboarding and training when the team needs help with its setup. Then put a recurring maintenance review on your own calendar so next year’s cleanup starts with fewer mysteries.

Sources and platform guidance checked November 9, 2026.

---

Make your CRM easier to maintain

Review your contact structure, pipeline rules, and automation handoffs with the SMBcrm team.

See plans & pricing or schedule a demo.