Cleaning a list you inherited and did not build
How the list got this way
- An acquisition brought a customer database along with the company, under terms that rarely mention email consent.
- A predecessor left and the documentation left with them, so the list's history is whatever the files suggest.
- An agency handed over a platform account at the end of a contract, with segments nobody can now explain.
- Several lists were merged during a platform migration and the source of each row was lost in the mapping.
Provenance is the missing field, and it changes everything
Two addresses can return an identical verdict and carry opposite risk. One was typed by a customer into a checkout last month. The other was scraped in 2019 and merged in twice. The check cannot tell them apart.
Without a source field, a clean result is weaker evidence than it looks. You have learned the mailbox accepts mail. You have learned nothing about whether the person agreed to hear from you.
This is also the legal exposure. Under GDPR the burden is on you to show a lawful basis. Inheriting a file does not inherit a consent record that nobody wrote down.
What a check removes, and what it leaves
Both columns matter. A verifier that only advertises the left one is describing half the job.
| Removed by checking | Still there afterwards |
|---|---|
| The accumulated decay of however long the list sat unused, which on an inherited file is usually substantial. | Reconstruct where an address came from, which is the field you actually need and the one nobody wrote down. |
| Domains belonging to companies that folded between the list's last use and yours. | Establish consent, or tell you whether the previous owner obtained any. |
| Duplicates created by the merge itself, which inherited files carry heavily. | Identify addresses that already unsubscribed, if the suppression list did not come across in the handover. |
| Disposable and malformed rows from whatever collection practice you are now responsible for. | Tell you whether these people will recognize your name, which on an acquired list is the difference between a campaign and a complaint spike. |
What to do instead
Find the suppression list before anything else
Unsubscribes and complaints from the previous owner still bind you. Mailing someone who already opted out is the worst outcome available here and no check will warn you.
Ask what the handover documents actually say
An acquisition agreement or agency contract sometimes records how the data was collected. Often it does not. Knowing which case you are in changes the plan.
Reintroduce yourself before you campaign
If the sending name has changed, a short message saying who you now are will surface the mismatch at a volume you can survive.
Record provenance from this point forward
You cannot recover the history you were not given. You can make sure your successor is not in the same position.
Questions people ask
Can we email a customer list acquired with a company?
It depends on what the original consent covered and the jurisdiction it came from. That is a legal question rather than a deliverability one. Verification tells you the addresses work, which is a different matter.
What if the suppression list was not handed over?
Treat that as the main risk and reconstruct what you can from the sending platform's history before mailing anything. Bounce logs and complaint records in the old account are usually still there.
Why does an inherited list produce complaints even when it verifies well?
Because recipients react to the sender name rather than to the state of their address. Someone who signed up with a company you acquired may not know who you are. The fastest way to say so is the spam button.
Is an old inherited list worth cleaning at all?
Cleaning is cheap, so measuring it is worth doing before deciding. What you learn is the shape of the file, which tells you whether there is a list here or a liability.
Related list problems
Measure your own list before you clean it
100 free checks a month, no card. The rows we could not get an answer on come back labeled rather than guessed at, and we never bill for them.