Unmerger
Learn about what the Unmerger Agent does and when to use it.
The Unmerger Agent identifies and corrects merge mistakes in your Reltio tenant. It analyzes merge history, compares contributing records, and proposes safe unmerge operations that you can approve and execute.
Who is it for?
Data Steward
Reltio Configurator
System Administrator
For more information, see About roles.
Why would I use it?
Use this agent to discover when two or more entities were merged incorrectly. It helps you investigate the cause, confirm whether to reverse the merge, and safely separate the records with full control and traceability.
When and where would I use it?
Use the Unmerger after resolving potential match issues, during data quality audits, or when you receive feedback from downstream systems or business users.
The Unmerger agent runs in AgentFlow and communicates securely through the MCP Server.
How does it support business goals?
It improves data quality and reduces risk by fixing incorrect merges without data loss. It supports governance through explicit approval flows, lineage traceability, and source-aware decision making.
Core capabilities
- Search for merged entities by ID, user, entity type, or time range
- Retrieve full merge history and contributing entities
- Compare entities side by side with enriched attribute data and match context
- Explain why merges occurred and recommend unmerge or retention
- Propose safe, minimal unmerge plans based on survivorship and identifiers
- Execute unmerge operations only after user approval
- Optionally assist with re-merging into correct targets after unmerge
- Generate merge tree visualizations and event lineage reports
Inputs and outputs
| Inputs | Outputs |
|---|---|
| Entity ID – Provide a merged entity identifier to investigate and unmerge if needed Search Filter – Specify criteria such as entity type, merge user, or date range to find merged records Confirmation Flag – Explicit approval is required before any unmerge is executed Enrichment Option – Optionally allow the agent to retrieve public data to support comparisons | Merge History – List of merged contributors, match rules used, and timeline of events Comparison View – Side-by-side table of entities showing matches, conflicts, and missing values. Enrichment Data – Publicly sourced data with references to URLs for attribute validation (optional). Recommendation – Unmerge or Keep Together, with rationale and confidence level Unmerge Plan – Proposed contributors to split, impact to attributes, and crosswalk reassignment. Execution Result – Confirmation of unmerge with resulting entity URIs Visual Report – Merge tree diagram and timeline visualization (if requested) Audit Trail – Log of all decisions, tools used, and actions executed |
Watch how it works
Watch how the Unmerger agent helps you identify and reverse incorrect merges in your tenant. This short demo shows how the agent retrieves merge history, compares contributing records, and proposes safe unmerge plans based on lineage and survivorship. You'll learn how to confirm each unmerge with full audit traceability in AgentFlow.
Safeguards, permissions, and governance
- The agent never executes an unmerge or merge operation without explicit user confirmation
- All actions are permission-aware and require access to the MCP Server with the appropriate roles
- Enrichment steps are optional and limited to publicly accessible, auditable sources
- Each step in the process is logged and traceable through a detailed audit trail
Limitations and edge cases
- The agent only works on previously merged entities that include lineage metadata
- It does not support tenant-wide bulk deduplication or automated multi-entity review flows
- Enrichment results may vary based on data availability from public sources