Campaign migration cleaner: move leads between Instantly, Smartlead, lemlist and EmailBison
In short: Reads the old tool's lead export, sets aside bounced, unsubscribed and invalid leads (and, by choice, replied, not interested and out of office), drops the old tool's campaign columns and writes the rest under the new tool's field names, with every other column kept as a custom variable. Limit: Column names in each tool's export aren't published; they are matched by name, and the result lists what was read and dropped.
Export the leads from the tool you're leaving and upload the file here. Bounced, unsubscribed and invalid leads are always set aside; replied, not interested and out-of-office ones are by choice. The old tool's own status and count columns are dropped, standard fields get the new tool's names, and every other column carries over as a custom variable.
Price: this tool is free. Checking a whole email list is from $9/mo, and the first 100 checks are free with Google, no card. See pricing
Bounced, unsubscribed and invalid leads are always set aside.
Sample result
7 Instantly leads, 2 ready for EmailBison: bounced, unsubscribed, replied and OOO set aside.
- Moving to
- EmailBison
- Set aside
- 4
- Custom variables
- 2
What this means for you
Pain Point becomes pain_point, so the custom variable still fills in the new tool.
- Instantly, Smartlead, lemlist, EmailBison
- Bounced and unsubscribed set aside
- Columns renamed for the new tool
- Blocklist file to import
- snake_case
- camelCase
- CSV
By SimpleVerifier Team · Last updated · Runs in your browser; nothing you paste is sent to us
Should you verify leads before importing them into a new sequencer?
- Download the import file here.
- Upload it at /verify first. New inboxes in a new tool have no history, and bounces on the first sends cost the most. The first 100 email checks are free with a Google sign-in, no card.
- Import the valid rows into the new tool, and hold the risky ones for a smaller send.
How do I migrate a cold email campaign to a new sequencer?
- Export every lead from the old tool's campaigns with their status columns: Instantly and Smartlead download a CSV from the campaign's leads list, lemlist exports from the Leads tab, EmailBison from Leads.
- Upload the export here and pick the tool you're moving to.
- Choose whether replied, not interested and out-of-office leads move. Check the table of column names and the merge tags to change in your copy.
- Download the import file and the set-aside file; import the set-aside file into the new tool as a blocklist so nobody gets mailed twice.
Example
- You enter
- An Instantly lead export of 7 rows moving to EmailBison: one Completed, one Bounced, one Unsubscribed, one Replied with Meeting booked, one marked Out of office, one Not yet contacted, and
[email protected]repeating the first lead; Personalization and Pain Point columns. - You get
- 2 leads ready for EmailBison (
[email protected],[email protected]) with columns email, first_name, last_name, company, title, personalization and pain_point; 4 set aside (bounced, unsubscribed, replied, out of office); the repeat merged; Campaign Name, Lead Status, Interest Status and Last Contacted From left out as campaign data. - Limits
- Runs in your browser with no row cap; an uploaded file can be up to 25 MB.
What gets dropped when you move a campaign?
Two kinds of thing. Leads that must not be mailed again: anyone who bounced, unsubscribed or was marked invalid, and, unless you untick them, people who replied, said no or sent an out-of-office reply (re-add those after their return date). And columns that describe the old campaign rather than the lead: lead status, interest status, open and reply counts, ids, campaign names, last-contacted dates and the sending account.
Everything else about the lead carries over: name, company, title, phone, website, LinkedIn and every personalization column you wrote, such as an icebreaker or a pain point.
How are custom variables renamed?
Standard fields take the new tool's names: first_name and company_name for Instantly, firstName and companyName for lemlist, first_name and company for EmailBison. Other columns become custom variables in the new tool's style, snake_case (pain_point) or camelCase (painPoint), so a header like "Pain Point" doesn't arrive with a space that breaks {{merge tags}}.
The result shows every rename, so you can change the merge tags in your sequence copy to match; the merge tag converter rewrites them in bulk. Each tool's import screen still asks you to confirm the column mapping.
Why verify before the first send from the new tool?
Mailbox providers judge new sending setups on their first sends. Google's sender guidelines and Yahoo's best practices both ask senders to keep lists clean, and a list that sat in the old tool for months has had time to decay. The list hygiene checklist for Instantly and Smartlead covers the rest.
Which column names does each tool get?
| Field | Instantly | Smartlead | lemlist | EmailBison |
|---|---|---|---|---|
email | email | email | email | |
| First name | first_name | first_name | firstName | first_name |
| Company | company_name | company_name | companyName | company |
| Title | job_title | title | jobTitle | title |
| Phone | phone | phone_number | phone | phone |
| Other columns | snake_case | snake_case | camelCase | snake_case |
Each import screen lets you remap columns; these names are chosen so the mapping matches without edits.
Who uses this tool, and for what?
- Agencies
- Move a client from Smartlead to EmailBison without re-mailing bounced or unsubscribed leads, with every personalization column intact.
- Founders
- Switch from Instantly to lemlist and keep icebreakers and custom fields working in the new sequences.
- Sales ops
- Consolidate leads from two sequencers into one, with a single blocklist of everyone who opted out.
What can’t this tool tell you?
- Column names in each tool's export aren't published; they are matched by name, and the result lists what was read and dropped.
- It renames columns, not the merge tags inside your email copy.
- A status column is needed to set leads aside; an export without one moves every lead.
- It can't tell which addresses still have a working inbox.
Common questions
- Which tools can I move from?
- Instantly, Smartlead, lemlist and EmailBison exports are read by column name, and most other sequencer exports work too as long as they have an email column and a status column.
- Are replied leads moved?
- Not by default. People in a conversation should be handled by hand, not dropped into a new cold sequence. Untick the option to move them.
- What happens to out-of-office leads?
- They are set aside by default with the reason, so you can re-add them after they're back. Untick the option to move them with the rest.
- Does it convert the merge tags in my email copy?
- No, it renames the columns and lists each rename. Use the merge tag converter for the copy.
- Is my file uploaded?
- No. It is read in your browser. Nothing is sent unless you choose to check the addresses afterwards.
Sources
A tidy list can still be full of dead addresses.
Extracting, deduplicating and syntax checks all work on the text of an address. None of them can tell whether the mailbox exists. Only the server that hosts it can answer that, through an SMTP check, and that is what the paid product does.
- Upload the cleaned file as it is: CSVs up to 100,000 rows
- A real SMTP mailbox check on every row, with catch-all detection
- Small list? Starter at $9/mo covers 2,500 emails a month, cancel anytime
Plans from $9 a month, cancel anytime, no contract. Sign in with Google and your first 100 email checks are free, no card. The free tools stay free either way.