A data merge change log records what changed during a deduplication or merge process.

It usually lists records that were updated, deleted, or merged, with their values before and after the operation.

Why a change log matters

Bulk merging can change many rows at once. A change log helps you audit what happened.

Use it to answer questions such as:

  • Which rows were deleted?
  • Which master records were updated?
  • Which values were added to the master record?
  • Which groups were skipped because of conflicts?
  • What changed before the CRM import?

🔍 Good to know

A merge preview helps before the action. A change log helps after the action.

What a merge change log contains

A practical change log can include:

  • Record ID
  • Action, such as updated or deleted
  • Previous values
  • New values
  • Master record ID
  • Duplicate group ID

This is useful for teams that need traceability before pushing cleaned data back to a CRM.

Datablist workflow

Datablist can generate a changes list for merge operations. It records deleted items and updated master records, so you can review the cleanup output.

Use this when merging CRM exports, Pipedrive duplicates, lead lists, scraped data, or enriched records.

Read the merge duplicate leads guide and the CRM cleanup guide for examples.