Import is a commitment point. Clean before it.
Once a list is inside your sender, campaign pressure makes it much harder to stop and clean it. Someone is ready to launch. The sequence is configured. The copy is ready. At that moment, removing records feels like losing work.
That is exactly when teams rationalize sending records they should not send. The pre-import step creates the right kind of friction — before the weak records are inside the system, not after.
Cold Email Verification Framework
This page covers one sender or workflow. The full framework explains the complete path from list source through verification, segmentation, and import into your sender.
Why lists need cleaning before every import.
No source consistently produces clean lists. Database exports go stale. Enrichment tools introduce inaccuracies. Scraped data includes generic inboxes and duplicate records. CRM contacts accumulate over time and may not reflect current email status.
| Source | Common quality problems |
|---|---|
| Apollo or ZoomInfo export | Invalid emails from stale contact data, role-based inboxes, duplicates across lists |
| LinkedIn Sales Navigator | Catch-all domains from company email patterns, work emails that changed after job changes |
| Web scraping | Generic inboxes (contact@, info@), outdated domains, emails that never belonged to a person |
| CRM export | Contacts added years ago, departed employees still in the system, emails verified in a prior tool |
| Manual list | No consistent format, typos, addresses from business cards or event signups |
| Purchased list | Unknown verification date, high proportion of role-based and invalid addresses |
Verification is not a one-time step. It is a standard gate that runs each time a list moves from any source into any sender.
What to clean — before every import.
Pre-import list cleaning has four stages. All four apply before any list enters a sender, CRM, or sequence.
Normalize the list.
Before verification, the list should have consistent formatting: lowercase email addresses, no trailing spaces, no duplicate rows, consistent column structure. Most verification tools expect clean input and return cleaner results when the input is normalized.
Deduplicate.
Remove addresses that appear more than once. Duplicate records result in repeated sends, which increases complaint risk and distorts campaign performance data.
Verify.
Run the normalized, deduplicated list through BillionVerify. The output assigns a signal to each address: valid, invalid, catch-all, role-based, unknown, or risky.
Route by signal.
Apply a routing decision to each result before any record enters the sender.
Route each result before import.
| BillionVerify result | Action before import |
|---|---|
| Valid | Import into sender or CRM |
| Invalid | Do not import — add to suppression list |
| Catch-all | Separate segment, lower volume, or hold for enrichment |
| Role-based | Separate campaign with shared-inbox messaging |
| Unknown | Review manually — exclude from main campaign |
| Risky or disposable | Do not import |
Where cleaned records go.
Verification output splits a single list into multiple destinations. Each destination has a clear purpose.
| Destination | What goes there |
|---|---|
| Main sender campaign | Valid addresses that match your targeting criteria |
| Catch-all segment | Addresses that may deliver — managed separately with lower volume |
| Role-based campaign | Shared inboxes that need different messaging |
| Suppression file | Invalid, disposable, and opted-out addresses — kept permanently |
| Review queue | Unknown and borderline results — reviewed before any send decision |
| Enrichment queue | Addresses that need additional data before a send decision can be made |
A suppression file is not optional. It is the record of addresses that should never enter a future campaign. Addresses that bounce, opt out, or fail verification go into suppression and stay there. Without a maintained suppression file, the same bad records can re-enter through a later import.
The standard pre-import flow.
Export list from source
→ Normalize fields and format
→ Remove duplicates
→ Verify with BillionVerify
→ Apply routing rules by result
→ Import valid records into sender
→ Move catch-all and role-based to separate campaigns
→ Add invalid and risky to suppression file
→ Move unknowns to review queue
This flow applies to every import — net-new lists, re-imported lists from previous campaigns, and CRM exports that have been sitting unused.
Re-verification before re-import.
A list that was verified in a previous campaign is not automatically safe for a new one. Email addresses change. Employees leave. Domains expire or get acquired. Any list older than 90 days should go through verification again before it re-enters a sender.
Re-verification is cheaper than discovering drift during a live campaign.
Other workflows with similar decisions.
Verify Emails Before Warmup
Understand why list verification must happen before warmup, not after.
Catch-All Policy for Cold Email
Define a routing policy for catch-all results before they enter cold email campaigns.
Cold Email Bounce Rate Control
Control bounce rate at the list level — before the sender is ever involved.
Warmup vs Email Verification
Understand which problem warmup solves and which problem verification solves.
Built-In Verifier vs Third-Party Verification
Compare native sender verification against a dedicated pre-send quality gate.
Folderly + BillionVerify Workflow
Verify lists before Folderly deliverability optimization — clean data makes warmup work.
Mailforge + BillionVerify Workflow
Apply a pre-send verification step before Mailforge infrastructure runs campaigns.
Pre-import list cleaning common questions.
1. How often should I clean a list?
Every time it moves from a source into a sender. Not just when you suspect problems. A consistent pre-import standard removes the need to make case-by-case decisions under campaign pressure.
2. Can I skip verification for a list that came from a trusted source?
No source is exempt. Trusted databases still produce stale records. Apollo, ZoomInfo, and LinkedIn data all require verification before import, regardless of the provider's stated accuracy.
3. What is the difference between deduplication and verification?
Deduplication removes addresses that appear more than once in the list. Verification checks whether each unique address is deliverable and what kind of address it is. Both steps are necessary — deduplication first, then verification.
4. Should I clean my CRM contacts before importing into a sender?
Yes. CRM contacts accumulate over time and are rarely actively maintained. An export from a CRM that was not built for outbound sending will contain invalid addresses, outdated contacts, and records that should be suppressed. Verify before the export reaches a sender.
5. What should I do with the catch-all segment?
Create a separate campaign for catch-all addresses with lower volume and closer monitoring. Do not mix catch-all addresses into your main campaign — their uncertain delivery status makes it harder to interpret your campaign performance data accurately.
6. Does list cleaning improve reply rates?
Indirectly. Cleaning removes addresses that would never reply because they do not exist, are not real contacts, or route to shared inboxes with no accountable owner. A smaller, cleaner list with verified addresses gives you a more accurate picture of how your campaign is actually performing.