Philippines account management crm duplicate account merge control

Prove the records describe one account

Treat the merge as a controlled data change. Confirm the legal or operational identity using approved sources, identify the surviving record, and decide field precedence one field at a time. Inventory relationships, permissions, workflows, integrations, reports, and external identifiers before changing anything. Export or preserve a permitted rollback record according to retention rules. Route ambiguous ownership, privacy, and financial fields to their accountable owners. After the merge, test linked work, reporting totals, notification recipients, and automation behavior; a clean screen can still hide broken references.

Choose an authoritative survivor

Before merging two CRM accounts, compare authoritative identifiers, billing or contract references, domains, addresses, ownership, and current client confirmation where appropriate. Similar names can represent a parent, subsidiary, reseller, or unrelated organization. Inventory contacts, open opportunities, service cases, consent or preference records, activities, custom objects, integrations, and automation triggers on both candidates. Choose the survivor based on an approved identity rule, not whichever record looks cleaner. For every conflicting field, name the source and decision owner; do not let the merge tool's default precedence make a business decision.

Decide fields individually

Similar names do not prove identity. Compare authoritative organization identifiers, agreement references, approved domains, addresses, ownership, and current confirmation where appropriate. A parent, subsidiary, reseller, and unrelated company can share words in their names. Record match evidence and contradictions before selecting a survivor. If the evidence cannot resolve identity, keep the records separate and route the question. A premature merge can mix contacts, permissions, opportunities, and service histories in ways that are difficult to reverse.

Map relationships and automations

Choose the surviving account using an approved identity rule, then decide precedence field by field. Recent is not always authoritative. A newer informal note should not replace an agreement identifier, while a current confirmed contact can supersede an old directory entry. For each conflict, record both values, sources, effective dates, and decision owner. Do not let the merge tool’s default setting make a business decision merely because it can complete the operation quickly.

“Accountability allows actions to be traced to an entity.”

NIST accountability glossary

Preserve a permitted rollback

Inventory linked contacts, cases, opportunities, activities, files, consent or preference records, custom objects, reports, integrations, external identifiers, and workflow triggers. Identify which links will move automatically and which require controlled correction. Preserve a permitted rollback record under the applicable retention rule. Schedule the merge when reviewers can test it and dependent teams can avoid simultaneous changes. Notify only operators who need the new controlling identifier.

Test downstream consequences

After execution, test operational use rather than only the account page. Reconcile report totals, search results, ownership, case history, notification recipients, synchronization logs, and automations keyed to the retired identifier. Search downstream systems for remaining references and assign each exception. Confirm that the retired record cannot silently receive new work. Closure preserves the identity decision, field choices, change evidence, tests, and residual queue so history remains understandable.

Route residual references

After approval, preserve the permitted rollback evidence and execute during a controlled window. Verify more than the new account screen. Check report totals, relationship links, opportunity ownership, ticket history, notification recipients, synchronization logs, and any workflow keyed to the retired identifier. Search for the old identifier in downstream systems and route residual references. Tell affected operators which record now controls and how to report a discrepancy. Close only when tests pass and exceptions have owners. This procedure protects history while preventing a duplicate from continuing to fragment future account work.

Close without erasing history

Record the approved match, field decisions, change evidence, post-merge tests, and any residual correction queue.