Blog·November 2, 2026

What Happens to Bills When You Delete a Client in Clio?

Every Clio firm ends up with duplicate contacts. The easy ones are two records with a name, an email address, and maybe a phone number. Figure out which one to keep, move what you need, and delete the other one.

The scary ones are the duplicates that have actually been used. They have matters, bills, payments, trust activity, communications, documents, and years of history attached to them. Before you delete one of those, it's worth knowing what Clio actually does with the financial history.

What happens if the client has an unpaid bill?

Clio won't let you delete a contact with an open bill. The deletion fails and the contact stays where it is.

That's a useful safeguard. You can't accidentally delete the client attached to money the firm is still owed. The open bill has to be dealt with in Clio before that contact can be deleted.

Paid and void bills are different. Once there are no open bills blocking the deletion, Clio will let you delete the contact. The old bills, transactions, and payments don't disappear with it. They stay in Clio, but the client attached to them is gone.

That can be surprising if you're cleaning up duplicates by hand. The financial history still exists, but you've removed one of the easiest ways to understand who that history belonged to.

Moving the matter doesn't move old bills

Moving the duplicate's matters to the contact you're keeping is an important part of cleaning up a duplicate, but it doesn't change bills that already exist.

A bill belongs to both the matter it was created for and the client it was issued to. If you change the client on the matter, Clio doesn't go back and rewrite old bills. The matter can now belong to the contact you're keeping while its existing bills still point to the duplicate. You can change the client on each old bill by hand, one at a time. If you delete the duplicate first, those bills just show the client as deleted.

Future billing needs attention too. If the duplicate is a bill recipient or has a share of a split bill, those settings need to follow the contact you're keeping. Moving the matter alone doesn't take care of that.

Trust is a different story

A duplicate with trust activity deserves even more care. Before deleting a client, you need to know whether that contact has money or financial history associated with a trust account.

This isn't something to guess about based on whether the two names look like obvious duplicates. Once money is involved, the records attached to the contacts matter just as much as the names on them.

Clio does give you a recovery window

Deleted contacts in Clio can be recovered for six months, so accidentally deleting the wrong contact isn't immediately permanent. That's useful, but it isn't a substitute for knowing what was attached to the contact before you deleted it.

If you're merging duplicates manually, keeping some record of the deleted contact and what was moved is still a very good idea.

Doing all of this by hand gets old quickly

For one duplicate, you can work through it manually. Check for open bills and trust activity. Move the matters. Check bill recipients and split billing. Move the information you need from the duplicate. Make a record of what was there. Then delete it.

The problem is that law firms rarely have one duplicate.

A firm with years of Clio data can have hundreds or thousands of duplicate groups, and the contacts that matter most are usually the ones with actual work attached to them. Finding two contacts with the same phone number is the easy part. Safely dealing with everything attached to them is harder.

That's the problem MERGEguard was built to handle.

MERGEguard checks the records attached to both contacts before it deletes anything. It moves matters, bill recipients, and split-payer shares to the contact you're keeping. If an open bill means the duplicate can't safely be deleted, the merge stops and tells you what needs to be fixed in Clio. It checks for trust activity, preserves the other supported information attached to the duplicate, and saves a snapshot of the contact in the merge log before deletion.

The point isn't just to find duplicate contacts. It's to actually finish cleaning them up without losing the things attached to them along the way.

Clio doesn't have a merge button. We built one.