How companies end up with two accounts
The stories repeat. Two companies merge and each brings a CRM. A second business unit started its own account years ago because procurement was slow. Or an agency set up a separate account per brand, and the brands grew together. However it happened, the symptom is the same. Two versions of the customer, two pipelines, and reports that cannot be added up.
The instinct to merge symmetrically is wrong. Consolidation works when you pick one surviving account and treat the other as a source system. One account keeps its structure, history and integrations. The other is exported, cleaned and imported, then archived.
What carries over and what does not
From the closing account, the records move: organizations, people, deals with their stage history dates, notes, activities and files. Products can be exported and recreated. Custom field values come along once matching fields exist in the survivor.
The configuration does not move. Automations, insights dashboards, filters, web forms, Campaigns content and app integrations stay behind and need rebuilding or repointing. Record IDs change on import, which is why every integration and report built against the closing account must be found and rewired.
Mapping: closing account to surviving account
| Closing account | Surviving account | Notes |
|---|---|---|
| Organizations | Organizations | Dedupe on domain across both accounts first. |
| People | People | Dedupe on email, merge into existing records. |
| Deals, open | Deals in mapped pipelines | Map every stage pair in writing. |
| Deals, won and lost | Deals with original dates | Keep close dates, or revenue history shifts. |
| Custom fields | Merged field set | Same name does not mean same meaning. Check types and options. |
| Users | Users and seats | Invite first, map owners by email. |
| Automations, dashboards | Rebuilt by hand | Screenshot everything before export. |
| Integrations and webhooks | Repointed | IDs change, so every connection needs attention. |
Pitfalls specific to consolidation
The overlap is the project. If both accounts sold into the same market, the same company exists twice with different owners, notes and open deals. Every overlap pair needs a decision: which owner, which deal survives, which notes merge. Build the overlap list before the import, on domain and email, and work through it with both sales leads in the room.
Field collisions are quieter. Both accounts have a field called Industry. One is a dropdown with twelve options, the other is free text. Importing without reconciling gives you a field that is half structured, half noise. Compare the field lists side by side and merge deliberately.
Then there is politics. A consolidation always has a team that loses its familiar setup. Decide the survivor on structural quality, communicate why, and give the arriving team extra onboarding. Skipping this step is how consolidations technically succeed and practically fail.
The step plan
1. Choose the survivor and freeze changes
Pick on structure, not size. Freeze configuration changes in both accounts for the project duration.
2. Reconcile the field sets and pipelines
Merge the field lists, align option values, and write the stage mapping table for every pipeline pair.
3. Build the overlap list
Match organizations on domain and people on email across both accounts. Decide each conflict with the sales leads.
4. Export, transform, test import
Full export from the closing account, transform to the survivor's field set, then a fifty record test with manual checks.
5. Import, rewire, archive
Import in order, merge the overlap pairs, repoint integrations, rebuild the automations that earned it, and set the closing account to read-only until the contract ends.
Timeline and cost band
Three to six weeks and €4,000 to €12,000 with a partner is the honest range. Overlap volume sets the price, because every duplicate pair costs human decision time. The wider pricing context is on the implementation cost page. Treat the consolidated account as a fresh implementation for the arriving team, with the six step method as the frame, and read the common mistakes guide before the first team-wide login. If one of the two accounts is really an abandoned relic, the legacy CRM guide may describe your situation better.
Questions
Can Pipedrive merge two accounts for us?
No. There is no native account merge. Consolidation is an export from the closing account and a structured import into the surviving one, with deduplication in between. Pipedrive support can advise, but the work is yours or a partner's.
Which of our two accounts should survive?
Usually the one with the better structure, not the bigger one. Cleaner pipelines, saner fields and active automations are worth more than record count, because records move and structure does not.
Do email conversations move between Pipedrive accounts?
Synced threads do not transfer as data. When users connect their mailboxes to the surviving account, history rebuilds from the mail provider. Threads from departed employees' mailboxes are the exception, so export those to PDF first.
What happens to automations and insights dashboards?
They stay in the closing account. Automations must be rebuilt by hand in the survivor, and dashboards recreated. Screenshot both before you start, the closing account disappears from view faster than you expect.
How long does a Pipedrive consolidation take?
Three to six weeks. Deduplication across the two account overlaps is the slow part. Two accounts that never shared customers merge much faster than two that sold into the same market.