CRM refresh

4 min Advanced

What you'll learn

  • Which fields decay fastest and why
  • Run a refresh pass that re-validates your records against current data
  • Review the proposed changes and write them back to your CRM safely

A CRM decays a little every day. People change jobs, companies move, and direct dials stop working, so records that were accurate last year quietly mislead your team today. CRM refresh re-validates your existing records against current truth, then writes the corrections back. This lesson covers what tends to go stale, how to run a refresh pass, and how to review and write the updates back safely.

What you’ll have
RecordWhat changedNew value
Jane DoeTitleCRO, was VP Sales
John RoeEmployerGlobex, recently moved
Sam PoeDirect dialre-verified

The workflow, step by step

  1. 1

    What goes stale

    The fields that decay fastest are title, employer, and contactability, because people change jobs and direct dials stop working. Records that were accurate last year quietly mislead your team today.

  2. 2

    Run a refresh pass

    A refresh pass re-validates your existing records against current data in one go, rather than checking them by hand. Landbase compares what you hold against the dataset and flags what has changed.

  3. 3

    Review and write back

    You review the proposed changes before anything touches your CRM, then write back the corrections you trust. Keeping a review step means the refresh improves your data without overwriting it blindly.

Try it in Landbase

  1. Take one stale segment of your CRM, such as contacts you have not touched in a year.
  2. Run a refresh pass and review what changed in titles, employers, and contact details.
  3. Write back the corrections you trust.
  4. Note how many records were quietly out of date.
Tip
Always keep the review step. A refresh proposes changes, and you decide which ones are written back.