Duplicate property records can appear after a fresh enquiry, a new instruction, a system migration or simple data entry. Two records may describe the same property, but that does not mean every field should be combined automatically. One may contain an older instruction, superseded contact detail or historic marketing material that should remain distinguishable from the current working record.
A duplicate-record merge review establishes whether the records genuinely represent the same operational entity, which record should remain authoritative and what information needs to be retained without flattening important history.
Confirm that the records refer to the same property
Compare stable identifying information available within the agency's legitimate records rather than relying only on a similar display address. Differences may reflect data quality, but they may also indicate distinct units or records that should remain separate.
If identity is uncertain, hold the merge and route the question for verification.
Understand why each record exists
Review the origin and purpose of both records. An old completed instruction and a current instruction may legitimately need separate historical treatment even though they concern the same property.
The goal is to remove harmful duplication without erasing the distinction between different periods or business events.
Choose an authoritative current record
Where consolidation is appropriate, identify which record will carry the current operational state. Consider active ownership, current seller instructions, live marketing references and other working dependencies rather than choosing whichever record was created first.
Document that choice so colleagues understand where future updates belong.
Compare fields before moving information
Review material information field by field. If the two records disagree, do not automatically prefer a populated value over a blank one or a newer timestamp over an older verified fact.
Conflicting information should be resolved through the agency's normal verification process before it becomes part of the authoritative record.
Protect linked activity and history
Identify appointments, enquiries, media, notes and other records linked to each property entry. A merge process should not leave important activity orphaned or silently attach historic events to the wrong instruction context.
Where the system cannot preserve a relationship safely, record the exception and use the appropriate controlled alternative.
Prevent the superseded record from returning to use
After consolidation, make the non-current record's status clear through the agency's supported process. Staff should not later update it because it still appears plausible in a search result.
Do not simply delete evidence needed to understand earlier activity unless the agency's authorised record process specifically requires that outcome.
Verify the surviving operational picture
Check that the authoritative record now contains the intended current information and that important linked work remains accessible. Confirm that active staff workflows point to the surviving record.
A careful duplicate-record review helps estate agencies improve data quality without treating consolidation as a blind technical merge. It protects current property information, historic context and linked activity while giving the team one dependable record for future work.