Workflow
How to verify a B2B database export
Treat a database export as unverified input. Test a sample, measure the result mix, and only then verify the rest.
Example
A sample file (fictional data)
| db_status | exported_on | |
|---|---|---|
| ana@northwind.example.test | verified | 2026-09-01 |
| raj@quill.example.test | likely | 2026-09-01 |
| info@lumen.example.test | unknown | 2026-09-01 |
exported_on lets you relate result quality to export age.
1. Sample first
Take a random 200 rows. Verify them and count valid, role, catchall, unknown and invalid. The mix tells you whether the full export is worth verifying.
2. Verify and compare
Verify the whole file with the original columns returned. Cross-tabulate db_status against the result to see where the database and the live check disagree.
3. Decide
Send to valid. Test catchall on a small batch. Retry unknown before dropping it. Remove invalid and disposable, and record the invalid rate for the next purchase decision.
Related