People and households

Duplicate and cleanup posture

Cleanup guidance should reduce record mess early without encouraging casual merges or overconfident household edits.

Who this is for: Admins and staff preparing people data for migration or early setup.

Last reviewed 2026-04-30 · Source of truth: broader help library · Languages: en, es

Article metadata

Product area: people and households

Owner: People data model

Parity reviewer: Bilingual launch review

Retrieval-ready: Yes

What to expect next

Flag likely duplicates and inconsistent household relationships before deeper migration assumptions harden.
Escalate when cleanup would change the canonical meaning of a person or household record.

What cleanup should focus on first

Start by identifying obvious duplicate patterns, missing core identifiers, and places where household relationships are inconsistent across records.

Early cleanup should make review easier, not create a second wave of hidden record changes that no one can explain later.

What should not be improvised

Do not merge records casually when the overlap is uncertain, the household meaning is unclear, or the change could hide pastoral or financial history.

If your team cannot explain why two records should become one, the safest next step is review, not cleanup theater.

Escalation path

If cleanup could change the canonical identity, household structure, or history attached to a person record, escalate before making the change feel routine.

Related next steps

Read people and household basics Review migration mapping boundaries Open Spanish version Back to help center