Salesforce does not have a built-in merge function for accounts, so you will need to manually consolidate the data or use a third-party tool
Salesforce treats account merging as a manual process. The platform does not offer a single button that combines two accounts the way it does for contacts or leads. This means you will need to decide whether to move records by hand, use a data management tool, or bring in a consultant. The method you choose depends on how many accounts you need to merge, how much related data they hold, and whether you want to preserve the history of both accounts.
Before you start any merge, back up your data. Export both accounts and all their related records—opportunities, contacts, cases, activities—to a spreadsheet. This protects you if something goes wrong and gives you a record of what was where before the consolidation.
Key Takeaways
- Salesforce has no automatic account merge tool, so you must move data manually or use a third-party application.
- Before merging, export both accounts and their related records to a spreadsheet as a backup.
- The most common approach is to keep one account as the master and reassign all related records from the duplicate account to it.
- You can deactivate or delete the duplicate account after all its records have been moved, but deletion is permanent and cannot be undone.
- Data loader and third-party merge tools can speed up the process if you have many accounts to consolidate.
The manual method: moving records one by one
The simplest approach for a small number of merges is to pick one account as your master and move everything from the duplicate to it. Start by listing all the related records attached to the duplicate account: opportunities, contacts, cases, activities, and custom objects. You can do this by running a report or by opening each account and checking the related lists.
Open each related record and change its account lookup field to point to the master account instead. For example, if Account A is your master and Account B is the duplicate, open each opportunity linked to Account B and change the Account Name field to Account A. Repeat this for contacts, cases, and any other objects tied to the account. Once all records have been reassigned, the duplicate account will be empty of related data.
After you have moved all records, decide what to do with the duplicate account. You can deactivate it by checking the Active checkbox to false, which hides it from most views and searches but keeps the record in your system. Alternatively, you can delete it entirely, but deletion is permanent and cannot be recovered. Most teams deactivate rather than delete, in case an old report or workflow references the account ID.
Using Data Loader to move records in bulk
If you have dozens or hundreds of records to reassign, doing it one by one will take hours. Salesforce's Data Loader tool lets you export records, modify them in a spreadsheet, and upload them back in bulk. Download Data Loader from Salesforce Setup (search "Data Loader" in the Setup menu), install it on your computer, and log in with your Salesforce credentials.
Export all the records you need to move—for example, all opportunities linked to the duplicate account. Use Data Loader's export function to pull them into a CSV file. Open the CSV in Excel or Google Sheets and change the Account ID or Account Name column to point to your master account. Save the file and use Data Loader's update function to upload the changes back to Salesforce. Data Loader will match each row to the existing record by ID and update the account field.
This method is faster than manual reassignment but requires you to be comfortable with spreadsheets and CSV files. If you make a mistake in the CSV—for example, a typo in an account ID—the upload will fail or update the wrong records. Test with a small batch first before running a full upload.
Third-party merge tools and when to use them
Several apps in the Salesforce AppExchange are built specifically for account merging. Tools like Cloudingo, DemandTools, and Duplicate Management by Ringlead can identify duplicate accounts, preview what the merge will look like, and execute the consolidation with a few clicks. These tools handle the reassignment of related records automatically and can merge custom fields according to rules you set.
Third-party tools are worth considering if you have a large number of duplicates, if your accounts have complex related data, or if you want to preserve a record of which accounts were merged. Most charge a one-time fee or a monthly subscription. Before you buy, check whether the tool integrates with your Salesforce edition (some do not work with Sandbox or certain custom objects) and whether it can handle your specific merge rules—for example, if you want to keep the phone number from Account A but the billing address from Account B.
Handling related records and custom fields during a merge
When you move records from one account to another, think about what happens to custom fields and related data. Standard fields like phone, website, and billing address exist on both accounts. Decide which account's values you want to keep. If Account A has a phone number and Account B does not, the choice is easy. If both have different phone numbers, you will need to decide which is current or whether to combine them into a note.
For related records like opportunities and contacts, moving them is straightforward—they have a single Account lookup field. But if you have custom objects or junction objects that link to accounts, make sure you understand how they will behave after the merge. Some custom fields may become blank or show the old account ID if you do not update them. Review your data model before you start, or ask your Salesforce admin if you are unsure.
Deactivating versus deleting the duplicate account
After all records have been moved, you need to decide what to do with the empty duplicate account. Deactivation is the safer choice: it removes the account from most searches and views, but the record stays in your system. This means old reports that reference the account ID will still work, and you have a record that the merge happened. To deactivate, open the duplicate account, uncheck the Active field, and save.
Deletion is permanent and cannot be undone. Once you delete an account, Salesforce removes it from your org entirely. Any report or workflow that references the deleted account ID will break. Only delete if you are certain you will never need the account record again and if no other records in your system reference it. If you are unsure, deactivate instead.
Preventing duplicate accounts in the future
After you have merged your duplicates, set up rules to prevent new ones from appearing. Salesforce does not have a built-in duplicate prevention tool for accounts, but you can use a few strategies. Create a validation rule that prevents two accounts with the same name from being created. Set up a workflow or flow that alerts your team when a new account is created with a name similar to an existing one. Train your sales team to search for an account before creating a new one.
Some teams use a third-party duplicate prevention tool that runs in the background and flags potential duplicates as they are created. These tools can match on name, phone, website, or custom fields and either block the creation or prompt the user to review an existing account first. The investment in prevention saves time later.
Frequently Asked Questions
Can I merge accounts if they have opportunities with different close dates?
Yes. Opportunities are separate records that belong to an account, not part of the account itself. When you reassign an opportunity from one account to another, its close date, amount, and stage stay the same. You are only changing which account it is linked to. All the opportunity data moves with it.
What happens to the account ID when I merge two accounts?
The account ID of the master account stays the same. The duplicate account's ID is either deactivated (if you keep the record) or deleted (if you remove it). Any record that was linked to the duplicate account's ID will now point to the master account's ID after you reassign it.
Can I merge accounts if one is a parent account and the other is a child?
Yes, but you need to handle the parent-child relationship carefully. If the duplicate account is a child of another account, change its parent to the master account before you move the related records. If the duplicate is a parent account with child accounts underneath it, decide whether those children should stay under the master account or be reparented elsewhere.
Will merging accounts affect my reports and dashboards?
Reports and dashboards that filter by account name or account ID may show different results after a merge. If a report was built to show data for the duplicate account, it will show no data after the account is deactivated or deleted. Update your reports to reference the master account instead, or rebuild them to include both accounts if you need historical data.
Do I need administrator rights to merge accounts?
Yes. You need permission to edit accounts and their related records, which typically requires administrator or custom profile access. If you are using a third-party merge tool, you will also need to authorize the app to access your Salesforce org. Ask your Salesforce admin if you do not have the necessary permissions.