# Archiving a duplicate makes it look fresher to last-writer-wins

Archiving can bump the modified time, which makes last-writer-wins pick the retired record.

By Ki Moon · 2026-08-24 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/archiving-makes-a-duplicate-look-fresher/

**Symptom:** After a duplicate cleanup, a merged entity shows values from the archived copy rather than the active record.

When two source records describe the same entity, a merge has to pick a value per field. Letting the most recently modified record win is the natural first choice, and that textbook rule holds up until the first duplicate cleanup.

In a CRM, deleting or archiving a record is an edit that can bump its modified time like any other change. Because this behavior depends on the CRM, run the check below before relying on either rule.

When someone archives a duplicate to retire it, that action can make it the freshest record in the set and invert last-writer-wins, letting its old values beat the active record's. This happens when reading the source's own modified time, though a warehouse copy may not move that timestamp on archive.

Rank by status first instead, per field:

- Active records beat archived ones.
- Modified time, read from the source, decides among records with the same status.
- The older created date breaks a modified-time tie, since the original record is usually the one kept.

Equal timestamps also need their own rule, so a deleted record never comes back because its timestamp ties a live one.

In a synthetic test set of 200 people, 20 with an archived duplicate whose archive bumped its modified time, last-writer-wins took the archived copy's value for 44 fields; ranking by status first took none. The set shows the mechanism, not how common it is.

## Check your setup (read-only)

Take the 10 most recently merged entities built from 2 or more source records where 1 record is archived. Look at which record supplied each field. Look for fields that came from the archived record while the active record had a value. Any such field means the tiebreak favors archived data.

**Passes if:** In all 10 sampled entities, every field with a value on the active record came from the active record.

**Access needed:** context-read, crm-read

## If it fails (changes to make later, not part of the check)

1. Choose each value per field, not per record.
2. Rank by active status first, then by modified time read from the source. Use the older created date only to break a modified-time tie.
3. Treat an archive or delete as a status that lowers a record's rank, not as a fresh edit.
4. Keep a deleted record deleted when the timestamps are equal.

**Applies if:** Your dedupe or enrichment config merges contact or account records from several systems and breaks ties by the most recent modified time.

**Skip if:** Your sources never archive or soft-delete records, or you keep one record per source with no merge.

Tags: matching, crm, data quality
