Article

How to Re-Import a Cleaned Email List into Your ESP Safely

By Unlimited Verifier Team ·

Flow diagram showing how to re-import a cleaned email list into an ESP: export valid contacts, subtract suppressions, pause automations, then import into a new

Summary

To re-import a cleaned list into your ESP, export only the Valid contacts, subtract every suppressed address, pause automations, and import into a new dated segment instead of overwriting your main list. This protects opt-outs, engagement dates and custom fields from accidental damage during the import.

To re-import a cleaned list into your ESP (email service provider), export only the Valid contacts as a CSV, subtract every suppressed address, pause automations, and import into a new, dated segment instead of overwriting your main list. Unlimited Verifier sorts results into Valid, Risky and Invalid, so the export is the easy part. The risk comes from what the ESP does with the file: a careless import can resubscribe opted-out people, reset engagement dates or blank out custom fields.

Quick answer

For the broader process, see the bulk email list verification workflow.

Why does re-importing need its own process?

A re-import changes live contact records, not just a file, so it needs its own controls. Cleaning is usually the careful part. The import is where cleaned lists often get damaged again, and three failure modes recur:

The deliverability stakes are real. Google's bulk sender guidelines recommend keeping user-reported spam below 0.10% and warn against reaching 0.30%. Yahoo's sender requirements cite a 0.3% complaint level. The two figures differ, so we recommend 0.10% as your working target. Mailing opted-out people pushes complaint rates up quickly.

Bottom line: A re-import can undo your cleaning if it resubscribes people or resets data, so run it as a controlled step.

What should you do in your ESP before exporting?

Before exporting, take an untouched snapshot of the full list, export the suppression list as its own file, and pause every automation that could fire on import. Together these give you a rollback point, a subtraction file and protection against accidental sends.

Export every column and store the file unchanged. It is your recovery copy. Some platforms' standard exports leave out suppressed contacts, so check yours and export suppressions separately either way.

Then note the match key your platform uses to find existing records, usually the email address or a contact ID. Your verified file must keep that column, or the import may create duplicates instead of updating records.

Pausing automations matters because welcome, onboarding or re-engagement flows can trigger on newly imported contacts. Turn them off for the whole import window, not just for the send.

Bottom line: Snapshot, suppress and pause first; the export is only as safe as the preparation.

Which re-import method should you choose?

For most teams, importing Valid contacts into a new segment is the safest first move, because it changes nothing else until you've checked the results. The other approaches trade simplicity for control, and the right choice depends on how often you'll repeat the process.

Approach How it works Best for Main risk Effort
Import Valid into a new, dated segment Original list stays untouched; cleaned contacts sit in their own segment First cleanup, or any time you're unsure of the match key Duplicate contacts if the match column is wrong Low
Overwrite the main list with the Valid file Cleaned file replaces existing records Teams that want one list and a file containing every column Blank fields and lost history if columns are missing Low to medium
Delete Invalid contacts outright Removes addresses from the platform Lists where storage or billing is a concern Deleted addresses can be re-added later with no record Low
Suppress Invalid contacts Keeps a do-not-mail record Nearly every case, especially compliance-sensitive lists Suppressed records count toward your platform's stored contacts Low
Scripted sync through the ESP's API Verify, then update contacts programmatically Recurring imports and large volumes Developer time, rate limits and error handling High
Migrate to a new ESP Move contacts and suppression history together Switching providers Suppression history is lost if it isn't exported High

Overwriting is tempting when you want a single list, but it removes the comparison point you need to spot errors.

Bottom line: Start with a new segment and a suppression file, and move to scripted syncing only after you've repeated the process several times.

How do you re-import a cleaned list step by step?

Work through seven steps in order: snapshot, subtract suppressions, verify, check the results, build the import file, import into a new segment, and reconcile. Each step produces a number you can check before moving on.

  1. Snapshot the current list. Keep the untouched export with all columns, plus the suppression file.
  2. Subtract suppressions. Remove unsubscribes, complaints and past hard bounces. Doing this first matters because it stops you spending verification credits on contacts you can never mail.
  3. Verify the remainder. Upload the cleaned file to your verifier. Split it first if it exceeds your plan's per-list cap (see the worked example below).
  4. Check the results file. Confirm that Valid + Risky + Invalid equals the number you uploaded. A mismatch means rows were dropped or duplicated, so investigate before importing.
  5. Build the import file. Keep only Valid rows, plus the match column and any custom fields you need. Save as CSV UTF-8.
  6. Pause automations, then import into a new segment. Name the segment with the date, for example "Valid re-import YYYY-MM-DD".
  7. Reconcile, then suppress. The new segment's count should equal your Valid count minus any duplicates your platform reports. Only then suppress the Invalid addresses.

Reconciliation is where import errors show up. Even a gap of a few dozen rows is worth tracing to a dropped row, a wrong match column or an unexpected merge.

Bottom line: Each step gives you a number to check; if a count doesn't reconcile, don't send.

What does the hands-on import tutorial look like?

This tutorial uses Unlimited Verifier, but the steps apply to any verifier that returns a results file. You'll need a CSV export from your ESP and enough time to review one results file.

  1. Create an account. Sign up for the Free plan to test a small file, or choose Pro for larger ones.
  2. Prepare the CSV. In Excel, choose "CSV UTF-8" when saving, because plain CSV can corrupt accented characters. Check ID and phone columns for stripped leading zeros and scientific notation. For a full checklist, see how to clean a messy CSV before upload.
  3. Remove suppressed contacts. Delete any row that appears in your ESP's suppression export. Lowercase both files before comparing, since many ESPs match addresses without regard to case.
  4. Upload the file. Open upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. For format rules, see accepted file formats. On Pro, files above 25,000 rows need splitting first, as covered in how to split a large CSV for verification.
  5. Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains, disposable addresses and role-based addresses are flagged.
  6. Export the results the same day. Download as CSV, Excel or JSON. Free results are kept for 24 hours and Pro results for 30 days, so don't rely on the longer window.
  7. Filter to Valid. Keep the Valid rows and the match column, and hold Risky rows back. If the columns are unclear, read the results file guide. To separate the holding groups cleanly, see how to segment a list by verification status.
  8. Import into a new segment. Pause automations, import the Valid file and name the segment with today's date.
  9. Suppress the Invalid rows in your ESP so they can't be re-added, then run your reconciliation check.

Bottom line: Export results the same day, keep the match column, and reconcile counts before sending.

How do plan limits shape a re-import?

Plan limits decide how many files you need, how long results stay available and whether the API can handle the job. The figures below are Unlimited Verifier's published plan details.

Free ($0) Pro ($29/month, or $25/month billed annually)
Lists per month 25 Unlimited
Emails per list Up to 150 Up to 25,000
Deep verifications per month 750 25,000
API access No Yes, 100,000 emails a month
Results kept 24 hours 30 days
Standard verification Unlimited, no per-email fees Unlimited, no per-email fees

Free suits pilots and small files. For a re-import of several thousand contacts, Pro is the practical choice.

Bottom line: Check your file size against the per-list cap and the results window before you start.

What does a real re-import look like with numbers?

The plan limits and arithmetic below are real. The verification results are hypothetical.

Starting point: A SaaS company exports 48,000 contacts. Its suppression export lists 1,100 unsubscribes and past hard bounces.

Step 1: Subtract suppressions. 48,000 − 1,100 = 46,900 addresses to verify.

Step 2: Split for Pro's per-list cap. At 46,900, the file exceeds 25,000, so it needs two lists: 25,000 + 21,900 = 46,900. Standard verification carries no per-email fee.

Step 3: Deep-verify the Risky group. Suppose standard results return 3,900 Risky addresses. A second deep pass on those uses 3,900 of the 25,000 monthly deep verifications, leaving 21,100 (25,000 − 3,900).

Step 4: Hypothetical results

Check: 41,200 + 3,900 + 1,800 = 46,900. Percentages are rounded.

Step 5: Import plan

Result: The active audience drops from 48,000 to 41,200, a reduction of 6,800 contacts (14.2%). That is 1,100 + 1,800 + 3,900, and it is the group most likely to bounce or complain. The cost is one Pro month at $29, or $25 per month billed annually. For how verification pricing models differ, see email verification pricing.

API variant: Scripting the sync, 46,900 addresses at up to 10,000 per bulk request needs five requests (four of 10,000 and one of 6,900). Pro's 100,000 API emails a month leave 53,100 (100,000 − 46,900). Get keys from the API keys page.

Free-plan check: The same 46,900 addresses at 150 per list need 313 lists (46,900 ÷ 150 = 312.7, rounded up). Free allows 25 lists a month, or 3,750 emails at most, so a file this size needs Pro. A 3,400-row test file needs 23 lists (3,400 ÷ 150 = 22.7, rounded up), which fits, but you must export within 24 hours.

Bottom line: The arithmetic produces a 41,200-contact segment, 1,800 new suppressions and a 3,900-contact hold group.

What should happen to Risky and Invalid addresses on re-import?

Suppress Invalid addresses, hold Risky addresses back, and send to Risky only after the Valid segment has proven clean. Risky covers catch-all domains, disposable addresses and role accounts such as info@, which can't be confirmed as safe to mail.

Invalid addresses belong on a suppression list so they can't be re-imported. A high Invalid share usually points to how the list was collected, not to the verifier. See what to do if 30 percent of your list is invalid and what to do with invalid emails after list cleaning.

Risky addresses need a judgment call. A catch-all domain accepts every address, so the mailbox can't be confirmed. Disposable and role addresses may be deliverable but rarely belong in a personal-engagement segment. Hold them back, and test a small group later; a few hundred contacts is a reasonable starting size, though that is our suggestion rather than a platform rule. The catch-all email verification page explains how those results are handled, and what to do with unknown emails after verification covers the rest.

Bottom line: Suppress Invalid, hold Risky, and send to Risky only after the Valid segment has proven clean.

How do you keep custom fields and avoid duplicates?

Keep the match column and every custom field in the verified file, and run a small pilot import first. A pilot of about 50 contacts is a practical size for surfacing column and matching problems. It's a recommendation, not a guarantee.

Before the full run:

If the import reports rejected rows or duplicates, don't retry blindly. Check whether the match column was renamed, whether the file is saved as UTF-8, and whether duplicates already existed in the source. Fix the cause, then re-run only the affected rows. For a fuller method, see how to keep custom fields when verifying an email list.

Bottom line: Pilot first. Empty cells and wrong match keys are the usual causes of overwrites.

When should you validate at the source instead?

Validate at the source when contacts arrive continuously, such as from signup forms, because repeated batch re-imports recreate the same problem each time. Checking an address before it enters the list is usually less work than finding, suppressing and reconciling it afterwards.

For a single address, use the free email checker. For forms and automated pipelines, the REST API accepts single-email checks and bulk batches of up to 10,000 emails per request. This is the core of email verification API and automation. For signup forms specifically, see real-time validation at signup.

Batch re-imports still make sense for periodic cleanup. A recurring schedule, as described in email list maintenance best practices, keeps the list current between full cleans.

Bottom line: Batch re-imports fix history; source validation prevents it. A growing list needs both.

What are the most common mistakes when re-importing?

Bottom line: Most failed re-imports trace back to a file or process error rather than to the verifier.

How we compared (and limitations)

This guide is based on public documentation: the FTC's CAN-SPAM guidance, Google's bulk sender guidelines, Yahoo's sender requirements and Unlimited Verifier's published plan details. We did not test any ESP's import behavior or run controlled experiments, so your platform may behave differently. Check its current import documentation before a large run.

Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark. Its verification engine is open source on GitHub, so you can review how it works.

Unlimited Verifier has no native ESP, CRM or Zapier integrations. The workflow is exporting a CSV, verifying it and re-importing, or calling the API from your own scripts. If you're comparing vendors, see the best email verification tools and how to choose an email verifier.

Bottom line: Use these steps as a checklist, confirm your platform's import rules, and keep the snapshot until your counts reconcile.

Safe re-import checklist

  1. Export a full, unchanged snapshot of the current list.
  2. Export the suppression list as a separate file.
  3. Pause all triggered automations.
  4. Remove every suppressed address from the verified Valid file.
  5. Confirm the match key column (email or contact ID) is present.
  6. Check column headers match your ESP's field names.
  7. Import into a new dated segment, not the main list.
  8. Spot-check 20-50 contacts for dates, fields and opt-out status.
  9. Resume automations only after the spot-check passes.
  10. Move contacts to the main list once the segment is verified.

Frequently asked questions

Should I import the full verification results file?

No. Import only the Valid rows. Risky and Invalid addresses should not go back into your sendable audience. Keep Invalid addresses on a suppression list so they are not re-added by a later upload or form sign-up.

What is the difference between deleting and suppressing Invalid addresses?

Deleting removes the record, so the same address can be uploaded again later. Suppressing keeps a record that blocks future sends to that address. Suppression is the safer choice for addresses that bounced or failed verification.

Why should I import into a new segment instead of my main list?

A new, dated segment keeps the original list recoverable if the import changes contact records in unexpected ways. You can compare the two sets, check results and then move contacts over once you are confident the import behaved correctly.

How do I stop automations from firing during an import?

Pause welcome series, abandoned-cart flows and other triggered automations before importing. Imported contacts can match trigger conditions, so an active flow may email people immediately. Resume automations only after you have checked the imported segment.

What match key should I keep in the file?

Keep the column your platform uses to find existing records, usually the email address or a contact ID. Without it, the import may create duplicate contacts instead of updating existing ones, which can split engagement history across records.

Can a re-import resubscribe people who unsubscribed?

It can, depending on how your platform handles imports. That is why you should subtract every unsubscribe and suppression from the file before uploading. The FTC requires opt-out requests under CAN-SPAM to be honored within 10 business days.

How do I check that the import did not blank custom fields?

Spot-check a sample of contacts before and after the import, comparing custom field values against your untouched snapshot. Confirm the column headers match the platform's field names exactly, since a mismatch can leave fields empty.

How often should I re-clean my list?

Re-verify before major campaigns, after long periods without sending, and when you add large external lists. Many senders also clean on a fixed schedule. Frequency depends on how fast your list decays and how often contacts change addresses.

Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification

Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.

Free Pro
Price $0 $29/month ($25/month billed annually)
Lists 25 a month, up to 150 emails each Unlimited, up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Result retention 24 hours 30 days

Why teams choose Unlimited Verifier

Unlimited Verifier states 99.5% accuracy for deep verification.

Create a free account and verify your next list before you hit send.

Want to test a single address first? Try the free email checker.