Analysis / Revenue operations and CRM hygiene
Find duplicate customer accounts in CRM exports
Use Proforma to find duplicate customer accounts in CRM exports. Produce ranked account duplicate groups and merge review impact table from your business data.
Revenue operations manager · Sales operations analyst
Bring this question into Chat
Your starting prompt.
Find likely duplicate accounts in our [CRM export]. Normalize company names and website domains, then compare billing addresses and linked records to rank matching evidence. Show candidate groups, existing owners and the opportunities that could be affected. Keep parent companies and subsidiaries distinct unless our supplied policy says otherwise. Prepare a merge review list without merging or deleting any CRM records.
Copy this starting point, then replace the placeholders with your own inputs.
Method and review
Keep the assumptions visible.
Check ownership, identifiers, stage definitions and activity dates before interpreting performance. Preserve the original record IDs and send ambiguous cases for review.
For this task, check
Shared website domains can represent distinct subsidiaries rather than duplicate customer records.
Before you begin
- Uploaded exports or permitted Data covering the listed inputs
Work with permitted files or queryable data. Verify the result against the original records.
Synthetic illustrative example
See the method in practice.
Synthetic input. Illustrative output checked locally; this is not a live Proforma run or customer result. CRM account exports include two possible duplicate records and one explicitly separate subsidiary.
These invented records explain the method. They are not a recorded Proforma run.
| Account | Company / domain | Billing address | Linked opportunities |
|---|---|---|---|
| A-1 | Birch Ltd / birch.test | 10 Oak St | D-1 |
| A-2 | BIRCH / birch.test | 10 Oak Street | D-2 |
| A-3 | Birch Labs / labs.birch.test | 20 Pine St | D-3; subsidiary |
| Comparison | Evidence | Impact | Decision state |
|---|---|---|---|
| A-1 ↔ A-2 | Same domain; similar name/address | D-1 and D-2 need owner review | Candidate only |
| A-1 ↔ A-3 | Separate domain/address; subsidiary | D-3 stays separate | Do not consolidate |
| A-2 ↔ A-3 | Same parent is not same account | Check entity policy | No merge proposed |
Method
Normalize case and common address suffixes, then compare identifiers and supplied entity relationships. Similarity supplies evidence for review, not a definitive corporate identity.
What the result tells you
A-1 and A-2 are plausible duplicates; linked opportunities make owner confirmation necessary. No CRM record is merged, deleted or updated by this example.
Take the next step
Make it your investigation.
Copy the prompt above, create or open your Workspace, and paste it into Chat. Add the inputs you have permission to use and adapt the assumptions with your agent.
Start exploringYour prompt is carried by copy and paste. Signing up does not submit it or start this work automatically.
Or start with your own agent
The setup prompt includes this public task. Your agent will help you connect when needed and use the access you approve.