---
id: CON-CRM-DQ-005
name: Merged Record Alias
feature: FEAT-CRM-DQ-05
product_area: crm
module: data-quality
revision: 1
status: superseded
product_intent: confirmed
implementation_evidence: partially-observed
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
definition: Absorbed identities are retained here as a retired concept; aliases now form part of the merge concept.
owned_by: MOD-CRM-DQ
synonyms:
  - merged-into pointer
  - tombstone
not_to_be_confused_with:
  - Ordinary deletion leaves no merge alias.
  - Archiving preserves the original record.
facets:
  - name: Survivor pointer
    meaning: The absorbed identity points directly to the current survivor and redirects after later merges.
    used_for: Resolving older identities without a chain.
  - name: Merge reference
    meaning: The alias retains its own merge event and time.
    used_for: Explaining the original absorption.
  - name: Old number and integration identity
    meaning: 'Original number, source identity and external identity remain available on the alias.'
    used_for: Finding current identity through historical references.
  - name: Reuse guard
    meaning: The database prohibits assigning an absorbed identity to a new same-type record in the workspace.
    used_for: Preventing replayed payloads from recreating an absorbed person.
  - name: The merged answer
    meaning: Record responses distinguish merging from simple absence and identify the destination.
    used_for: Helping links and clients handle old references.
  - name: History through the survivor
    meaning: Absorbed record history remains accessible through the survivor lineage.
    used_for: Inspecting the earlier information behind the current record.
relationships:
  - to: CON-CRM-DQ-004
    statement: An alias identifies the merge that writes it within the same transaction.
    provenance: test
    source: >-
      services-crm:modules/merges/tests/integration/services/persistence/merged-record-aliases.integration.spec.js#records
      the aliases in the transaction the caller opened, so they commit with the merge or not at all
  - to: CON-CRM-ENT-001
    statement: Contact aliases resolve to the survivor and prevent reuse of absorbed contact identity.
    provenance: test
    source: >-
      services-crm:modules/merges/tests/integration/db/merged-id-reuse.integration.spec.js#refuses a contact
      under it, naming the id and what became of it
  - to: CON-CRM-ENT-002
    statement: Organization aliases provide equivalent resolution independently of contacts.
    provenance: test
    source: >-
      services-crm:modules/merges/tests/integration/db/merged-id-reuse.integration.spec.js#refuses an
      organization under it, naming the id and what became of it
  - to: CON-CRM-ENT-033
    statement: Absorbed contact history remains accessible through the current survivor.
    provenance: test
    source: >-
      services-crm:modules/merges/tests/e2e/merged-records.e2e.spec.js#reads the absorbed contact’s own
      history through the survivor, ending in its deletion
acted_on_by:
  - CAP-CRM-DQ-016
  - CAP-CRM-DQ-018
  - CAP-CRM-DQ-019
visible_to:
  - ACT-CRM-002
  - ACT-CRM-004
  - ACT-CRM-009
evidence:
  - repository: services-crm
    source_sha: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
    paths:
      - docs/merging/README.md
      - docs/merging/experience/README.md
      - modules/merges/tests/e2e/merged-records.e2e.spec.js
      - modules/merges/tests/integration/db/merged-id-reuse.integration.spec.js
      - modules/merges/tests/integration/services/persistence/merged-record-aliases.integration.spec.js
    note: >-
      Static examination uses the cited records and implementation anchors; repository tests are not executed
      by this corpus check.
supersedes: []
intent_sources:
  - 'services-crm:docs/merging/README.md#Status'
  - 'services-crm:docs/merging/experience/README.md#Status'
---

# Merged Record Alias

## What It Is

This retired entry preserves the allocated identity of an earlier concept. Aliases now appear among the facets of a merge.

## What It Is Not

It is no longer a separate broad concept in the planning layer.

## How It Is Used

Earlier references remain resolvable. New planning reads the parent concept.

## Its Facets

The retained facet rows provide continuity with the earlier classification.

## How It Relates

Merge is the current conceptual home.

## What It Could Become

Future additions belong to that parent unless Product establishes a distinct broad outcome.