How to merge duplicate accounts without upsetting customers
A runbook to merge duplicate accounts in your SaaS. Confirm who owns both, decide what to keep, tell the customer, and never pay out free credits twice.
Hi, this is the third time I've written. We've paid you $149 a month for 14 months. Our company changed its name in September and IT moved everyone to a new email domain, so sign-in codes for my old address go nowhere. I made a new login with my new email so I could at least reach our projects. This morning it says that login is suspended as a duplicate. So the old account has all our work and I can't get in, the new one is locked, and you charged our card on the 1st. I've got a board review at 2 p.m. and the numbers are in there. Is anyone reading these?
It's 11:26 a.m. on a Tuesday and you're reading that on your phone, in line for coffee. You know where the word "duplicate" came from. Last Thursday you and your co-founder finally went through the free accounts that looked like second accounts, and you suspended 312 of them. Say a fully used free account costs you $2.40 a month. (This whole story is a scenario, so swap in your own numbers.) You'd put the sum in your team chat, and you were pleased with it: 312 × $2.40 = $748.80 a month, or $8,985.60 a year.
You lift the suspension by 11:31, which fixes half of it, because the work is in the old account and that account's mailbox no longer exists. Your admin panel has no merge button. If you typed merge duplicate accounts SaaS into a search box this morning, this is probably why, and you've got two and a half hours and a production database.
You get them in at 1:40 p.m. with a hand-written update and twenty minutes to spare. You apologize. They don't answer. A week later they cancel, and the reason box is empty. They'd paid you 14 × $149 = $2,086. If customers like them stay 36 months, the other 22 were worth 22 × $149 = $3,278, gone without a word.
Then you open the list again. That customer wrote in three times, and most people don't write in once. Someone locked out on a Thursday is trying another product by the weekend. So say six of those 312 logins belonged to people at paying customers, and all six companies leave:
| What you do | Arithmetic | Cost over a year |
|---|---|---|
| Leave all 312 accounts running | 312 × $2.40 × 12 | $8,985.60 in usage |
| Suspend them and lose 6 customers | 6 × $149 × 12 | $10,728 in revenue |
Six out of 312 is 1.9%. You were right about 98.1% of the list and you're at least $1,742.40 a year worse off. Work out the break-even for your own product:
Here that's $8,985.60 ÷ $1,788 = 5.03 customers, so the sixth puts you behind. If you spend $12,000 a month, $10,728 is about 27 days of runway, lost to a cleanup that was meant to save money. Now it's 2:15 p.m. and you have a decision you didn't expect to be making: lift the other 311 suspensions and go back to paying for them, or leave them on and wait to find out who never writes in.
Why duplicate accounts pile up in a SaaS product
Your database stores accounts, and people don't map onto accounts one to one. A company changes its domain. Someone signs up with a social login in March and a password in June without realizing. Someone keeps a work account and a personal one. And a few people open a fresh account because the last trial ran out. In your accounts table, every one of those is just two rows.
That's why the obvious fixes don't hold. Merging automatically when two accounts look alike treats a resemblance as proof, and merging the wrong two shows one customer's data to another, which is far worse than any duplicate. Sort each case first, because only one of these needs a merge:
| What you've got | What to do |
|---|---|
| One person, two accounts, by accident | Merge them |
| Two real people who look alike | Leave both alone |
| Someone claiming a benefit again | Don't merge. Decline the benefit and offer a paid plan |
How to merge duplicate accounts, step by step
Start from a request. Merge when the customer asks. If you found the pair yourself, write and ask first.
Confirm they control both accounts. They're signed in to one and read back a code sent to the email on the other. If that mailbox is gone, ask another admin on the account to confirm, or ask for the latest invoice number and the last four digits of the card on file. A matching name isn't enough, since a merge hands over everything inside.
Pick the account that survives. The one with the paid subscription wins, then the one with more work in it. The customer chooses their sign-in email.
Show them the result first. List what moves, what ends and their next charge, and get a yes in writing.
Pause and export. Stop renewals and scheduled jobs on both accounts and save a copy of each. A renewal landing halfway through is how you charge someone twice.
Move everything in one database transaction, so a failure leaves both accounts as they were. Log both account IDs and who ran it.
Leave a way back. Keep the retired account read-only for 30 days and send its old login to the survivor.
Already suspended a batch? Let those owners sign in and confirm, and apply a written policy before anything else.
What to keep when you merge two accounts
| Item | Rule |
|---|---|
| Paid credits and seats | Add them together |
| Projects, files and API keys | Move them, and keep keys working |
| Free credits | Keep the higher balance. Don't add them |
| Trials and offers | Used on either account means used |
| Usage this period | Add it together, or the merge resets the limit |
| Second subscription | End it and refund any overlap |
The free credits rule is the one that gets missed. Say your signup bonus is 500 credits. Add balances across five accounts and one person walks away with 2,500 credits from a support ticket you helped with. A merged account should never hold more free benefit than one account would have had.
What to tell customers when you merge their accounts
Leave out "duplicate" and "flagged". Say what happened and what they'll see next, and keep the same tone if the answer is no.
After the merge
Your accounts are now one, and you'll sign in with your new email. Your projects, invoices and paid credits are all there. We've ended the second subscription and refunded the $149 overlap. If anything looks wrong, reply here and you'll reach me.
When you got it wrong
We suspended your login by mistake, and that's on us. It's back on and everything is where you left it. We've taken this month's charge off too. I'm sorry.
The basic fixes for duplicate accounts, and how they break
A good merge cleans up one case. The usual ways of having fewer each catch something, and each sends somebody real to your merge queue.
Email rules. Verification catches typos and dead addresses, and that's about all it proves, and it strands anyone whose code lands in spam. Unique emails stop the same address twice and miss any second inbox. Gmail ignores dots and delivers plus-tagged mail to the same inbox, so one mailbox has many spellings. Disposable-domain blocks catch known throwaway services, miss new ones, turn away people using privacy forwarding, and need a list someone updates forever.
Extra signup steps. CAPTCHA stops simple scripts and misses anyone signing up by hand, and it gets in the way of people using screen readers. Phone or card requirements put off casual second accounts. Anyone with another number or card gets through, while students and people without a reliable mobile get stuck. Every text costs money, and a required card costs signups.
Network rules. One per IP stops repeats on a single connection and misses every other network. It lands on offices, campuses and households. VPN blocks catch the ranges on your list, hit staff on company VPNs, and give you a second list to keep current.
Limits. Rate limits stop bursts from one account, do nothing about 40 accounts under the limit, and can trip for real users in a busy hour. Usage caps hold one account while each new account arrives with a fresh cap. Shorter trials cut your cost per account, but every honest user pays for that and more accounts make up the difference.
Manual review. At 90 seconds a row, 312 rows is 7.8 hours. You'll catch plenty, miss whatever arrives after hours, sometimes land on whoever looks odd to a tired reviewer, and do it again next month.
Fewer second accounts to clean up later
Each of those fixes sees one scrap of a signup and has to guess the rest. AbuseZero exists to evaluate whether a claim should go through at the moment a free benefit goes out. Your domain list goes stale, and AbuseZero checks mailbox aliases, disposable domains and mail routing. Your IP rule stops at the address, and AbuseZero sees beyond it with VPN, hosting, network reputation, Tor and proxy intelligence. AbuseZero flags abuse that single checks miss. Its multi-layer AI risk analysis examines 140,000+ signals and detects linked claims. AbuseZero uses a proprietary algorithm, with AI that checks the claim again. Creating a fresh account isn't enough to erase previous activity, and you don't have to build your own abuse prevention system.
You make one API call before each grant and get a clear allow or deny, under rules you control. A customer you know is real can go on an allow list, and Observe mode shows you what would be denied before anyone is blocked. The quickstart sets up your first benefit.
Frequently asked questions
Should I merge duplicate accounts automatically?
No. Merge only after the person has confirmed they control both. A wrong merge exposes one customer's data to another.
What happens to a free trial when two accounts are merged?
If either account used it, it's used, so the merge doesn't restart anything.
Can two people at the same company merge their accounts?
Don't merge two people. Move them into one shared workspace, so each keeps their own login and history.
Keep real customers while you clean up
Start with Builder
Pay as you go. Protect your first benefit today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.