Understand the working context

Two companies may share a name, while one company may appear under several abbreviations. Compare identifiers, contacts and business context before deciding what to keep. A cleanup also needs to consider opportunities, documents, ownership and notes attached to each record. Deleting an apparent duplicate without understanding those relationships can make the account harder to follow. Establish a consistent approach and work on a small set before applying broad changes.

Put it into practice

  • Confirm whether the records represent the same customer.
  • Identify the record and details the team considers authoritative.
  • Review linked work and any differences in ownership.
  • Plan a supported correction or migration rather than assuming automatic merging.

A practical example

A customer appears as both “Northstar” and “Northstar Studio”. One account contains current quotations while the other holds older contacts. The administrator investigates the relationship and chooses a controlled correction approach. The team also agrees how to name the customer in future imports.

HOW THIS RELATES TO ATLAS

In the current workspace

Atlas does not currently include a general duplicate-detection or merge workflow. Review source data and supported import/record actions before planning a cleanup.

Explore the product

Atlas feature scope reviewed 17 October 2026. Plan availability and connection setup apply.