Cleaning CRM data when multiple teams sell into one account

How one customer ends up as five records

To clean CRM data when several teams sell into one account, agree a single master record for the customer, merge duplicates against a reliable identifier such as the SSM registration number, and settle who owns each contact and opportunity before merging anything. Freeze new record creation for that customer during the work so duplicates do not reappear behind you.

Duplicates grow quietly. The industrial products team creates 'ABC Holdings Sdn. Bhd.', the services team creates 'ABC Holdings Sdn Bhd', and someone imports a trade show list containing 'ABC Hldgs'. A branch manager in Johor Bahru gets entered as a separate company. Each team builds its own contacts and opportunities on its own record, so nobody sees the whole relationship, and the customer receives three uncoordinated calls in the same week.

Merge rules to agree before anyone presses the button

Merging is hard to reverse, so decide the rules with the team heads involved. Choose the surviving record: usually the one with the correct registered name, the most complete history, or the account linked to invoices in your finance system. Decide which field values win when records disagree, such as address, industry and tier. Agree that opportunities keep their current owners after the merge, because changing deal ownership during a clean-up turns a data exercise into a commission dispute.

Name one account owner for the merged record and record the other teams as secondary sellers with their product lines noted.

Bring finance into the conversation early. If your accounting system holds the customer under one debtor code, align the surviving CRM account to that entity so sales figures and invoiced revenue can be compared later. Where the CRM shows a group and finance bills three subsidiaries, build the hierarchy so both views agree rather than forcing one to match the other. Write the agreed rules into a short note that every team head signs off, so nobody reopens them halfway through the merge.

A clean-up sequence for one shared account

Work account by account, starting with your largest shared customers. For each one:

• Announce a short freeze on creating new records for that customer and tell every team involved.
• Export every account, contact and opportunity that could belong to the customer, searching by name variants, email domain and registration number.
• Mark which records are true duplicates and which are genuine subsidiaries or branches that need their own place in the hierarchy.
• Pick the surviving account and confirm the merge rules with each team head.
• Merge accounts, then reconcile contacts under the surviving record.
• Check that every open opportunity still has the right owner, stage and close date.
• Lift the freeze and record the date of the clean-up on the account.

Contacts that appear under several records

The same procurement manager may exist three times with a personal Gmail address, an old work email and a mobile number typed in different formats. Keep one contact, carry over every logged activity, and store alternative emails or numbers as secondary fields rather than deleting them. Activity history matters more than tidy fields, because it shows who talked to whom and what was promised.

Use the clean-up to mark people who have left the customer as inactive, and to confirm each remaining contact's role in buying decisions. Where two teams know the same person for different reasons, note both relationships on the contact so neither team is surprised by the other's calls.

Stopping duplicates from returning once teams go back to selling

Set a naming convention based on the registered company name, with trading names in a separate field. Require a search before any new account is created, and have the system warn when a name, domain or registration number matches an existing record. Appoint a data steward in sales operations who reviews new accounts each week and merges early, while the fix is still small.

Bulk imports from events or marketing lists are a common source of new duplicates. Route them through the steward rather than loading them directly, so each row is matched against existing accounts before it lands.

When the system itself keeps creating the mess

If teams each run their own spreadsheet or a separate tool, cleaning the CRM will only ever be temporary. One shared system with account hierarchies, owner roles and duplicate checks matters more than any clean-up project. BukuCRM, Fasttrade's product for sales teams, centres on shared accounts and contacts alongside pipeline, activity and delivery handover. Speak with Fasttrade to confirm scope for a multi-team setup.

Frequently asked questions