Skip to content
Skip to content
Skip to content

Prospecting and outbound

How to import enriched leads into Instantly, Smartlead, or lemlist

Export verified, scored leads to your sequencer as a CSV: map enriched fields to variables, upload, then mark the campaign in your CRM.

Photo of Utku Zihnioglu

By

ยท CEO & co-founder

Updated Nov 20, 2026

ยท 11 min read

Export wording matches the redesigned export setup

Free plan: 200 credits a month, 100 rows per table, no card

Guide cover: Verified before it reaches the sequencer, beside the HubSpot, Attio, and Pipedrive logos, the CRMs that record the campaign

A CSV of 2,000 leads uploads into a sequencer in moments, and the upload cannot tell you whether the people fit. The bounces land on your sending domain, not on the sequencer, which is why cold email deliverability starts with the list. So this guide treats the moment you import leads into Instantly, Smartlead, or lemlist as the last step of a pipeline rather than the first: the segment that leaves has already been enriched, scored, and verified.

You finish with three things. The file's headers match the variables your copy uses, each lead carries an opening line written from its own research, and your CRM knows who went into which campaign.

To build the segment while you read, open a free workspace and bring your lead list in.

Before you import leads into Instantly: build the segment worth sending

Mailbox volume is the scarce resource. Every mailbox has a safe daily send count, and every lead in a campaign takes a slot a better-fit lead could have had. Microsoft 365 also caps external recipients per tenant, and a mailbox past it gets 550 5.7.233 bounces until sending comes back. Filter hard before anything leaves.

Three filters do most of the work:

Filter

What it checks

What happens if you skip it

Verified

Deliverability is valid

Bounces count against your sending domain

Scored

ICP score clears your cut-off

Volume goes to people who were never going to buy

Enriched

The fields your copy uses are filled

A blank {{opening_line}} sends a broken first sentence

Verification is the filter people regret skipping. In Oneprofile, add Verify email beside Find work email so each new lead runs both, at up to 0.8 credits an address, or up to $16 per 1,000. Catch-all results come back marked catch-all instead of valid, because one check cannot confirm the mailbox behind them. Switch on the second verifier for catch-alls and many of those get settled too. The guide on finding verified emails for a whole list covers the waterfall that produces those statuses.

Scoring decides who goes first. An AI agent scores each account against your ICP and writes the reasons beside each score, all covered in the guide to ICP scoring with AI. For this guide you only need a cut-off. The top tier goes to the sequencer this week, and the next tier waits.

A complaint while we are here. Sequencer dashboards open on emails sent this week, which rewards exactly the wrong habit. Replies per hundred leads tells you whether the list was any good, and almost nobody puts it on the front page.

Map enriched fields to your email sequencer's variables

Anyway. Most sequencers personalize with double-curly-brace variables, and a column you map as a custom field at import becomes a variable you can put in the copy. That is the whole trick to connect enrichment to email sequencer variables: decide the variable before you export, and the mapping screen stops being a puzzle.

Name fields to match sequencer variables, and keep headers short, lowercase, and free of spaces. opening_line maps cleanly, while "Opening line (AI draft v2)" becomes a variable nobody wants to type.

What you export

Where it lands in the sequencer

What it is for

Work email

The email field

Required by all three

First name, company name

Standard fields

Greeting and subject line

opening_line

Instantly's personalization field, lemlist's icebreaker, a Smartlead custom field

The first sentence of the email

score_reason

A custom variable

Context for whoever reads the reply

Company domain

The website field

Company-level variables and spotting duplicates

Write an opening line for each lead: it is the field worth spending on. Add an AI agent to your table with a prompt along the lines of "write one sentence to /First name about something specific in /Company research", and run it on the first 10 leads before the whole segment. Reading ten drafts tells you more about a prompt than rereading the prompt.

One catch to keep in mind: a line written before export is frozen at export time. If the campaign launches three weeks later, the funding round it mentions is three weeks older too.

Import leads into Instantly, Smartlead, or lemlist

The file is the handoff, and it costs no credits.

  1. Filter to the segment. Deliverability is valid, score clears your cut-off, and opening_line is not empty.

  2. Hide what the sequencer does not need. Raw research notes and data source names stay behind. The export matches what you see: filter, sort, and field order carry across, and anything hidden stays out of the file.

  3. Export the segment as a CSV. Click the table's name at the top of the page, then Export to file, then Export to CSV (.csv). To send a hand-picked handful instead, tick those leads and click Export in the bar that appears.

  4. Upload to your sequencer. Add the file to a campaign and read the mapping screen before you confirm.

That last step differs a little by tool.

Upload the CSV to an Instantly campaign

Add leads to the campaign from the CSV. Email maps itself. Point opening_line at the personalization field, or keep it as a custom variable and write {{opening_line}} into the copy. Both work, and the custom variable is easier to find six months later when someone asks where that sentence came from.

Send leads to Smartlead with custom fields

Smartlead's import asks you to map each header to a standard field or a custom one. Map every enriched field as a custom field on the way in, even the ones the first email does not use yet. Adding a field to leads already sitting in a campaign is probably more tedious than mapping it at import.

Sync leads to lemlist through a campaign import

lemlist imports a CSV into a campaign the same way, and its icebreaker variable exists for exactly the job opening_line does. Map it there and any template already built around {{icebreaker}} picks it up without edits.

Keep the sequencer and your CRM in sync

The moment a lead enters a campaign, your CRM should know about it. Otherwise a rep calls someone on day two of a five-step sequence, and the prospect hears from you twice in one afternoon.

Every time you export leads to Instantly or either of the others, do three things alongside the upload:

  • Mark the campaign at export time. From the same table, add an export to your CRM that updates existing contacts and skips the rest, matched on email, and type a value such as "Instantly: Q4 founders" plus the date into a property. Create that property in your CRM first, since the export maps onto fields the CRM already has. HubSpot, Salesforce, Attio, and Pipedrive all take an export like this.

  • Let replies log from the sequencer. Each of the three has its own CRM connection for activity and replies. Which plan includes it varies, so check yours before you rely on it.

  • Carry opt-outs between the two tools. Oneprofile's do-not-contact list exports as plain text, one address or domain per line, ready to paste into a sequencer's blocklist. Unsubscribes collected in the sequencer paste back into Settings, under Do not contact, the same way.

There is a version of this with no handoff to maintain. Oneprofile runs email and LinkedIn sequences from the same list, with replies landing in one inbox and each lead's sequence status sitting beside the research, ready for an export to push it to your CRM. The opening line there is written at send time, which is the frozen-line problem from earlier, solved by never exporting. The outreach feature page covers mailboxes and step types.

Edge cases when you import leads into Instantly

Most problems show up on the second export, not the first.

  • Leads already in a campaign. Re-exporting a segment that changed will include people you uploaded last time. All three sequencers have a duplicate check on upload under slightly different names, so turn it on. If your list comes from the CRM, bring the campaign property in with it and filter out anyone who already has a value.

  • Catch-all addresses. Send them as their own small campaign, ideally from a separate mailbox, instead of mixing them into the main send.

  • Very large segments. Split by score tier and export each tier as its own campaign, so the best-fit leads go out first and a weak tier is easy to pause.

  • Empty personalization. A lead with no opening_line gets an email that starts mid-air. The filter in step one exists for this, so check it survived when you reuse a saved view.

Try it on a slice of your own list before the real campaign. The free plan gives you 200 fresh credits every month, plus three tables of up to 100 rows, enough to verify, score, and write openers for a genuine sample and see the file before it gets anywhere near a mailbox. Get started free and export your first verified segment.

Do this in Oneprofile

An opening line written from each lead's research

An AI agent reads each lead's own research and writes one sentence for it, ready to map to a variable in your sequencer or to send from a Oneprofile sequence.

  • Oneprofile logo
  • HubSpot logo
  • Salesforce logo

6 steps to build it

Before you start

A list with work emails checked by Verify email and an ICP score on each lead

A campaign in your sequencer, ready to take a CSV upload

A CRM property for the campaign name and date, created once

1

Filter to the segment

Keep only leads whose Deliverability is valid and whose ICP score clears your cut-off. Catch-all addresses the second verifier could not settle go in a separate, smaller batch.

2

Write an opening line for each lead

Add an AI agent that writes one sentence per lead from that lead's own research. Run it on the first 10 leads and read the drafts before running it across the segment, then filter out anyone left without a line.

3

Name fields to match sequencer variables

Give every field the sequencer needs a short, lowercase header with no spaces, such as opening_line, and map it as a custom field at import so it becomes a variable in the copy.

4

Export the segment as a CSV

Click the table's name, then Export to file, then Export to CSV. The file matches what you see: filter, sort, and field order carry across, and anything hidden stays out. The export costs no credits.

5

Upload to your sequencer

Add the CSV to a campaign in your sequencer and check the mapping before confirming. Point opening_line at the personalization or icebreaker field, or keep it as a custom variable, and turn on the duplicate check.

6

Mark the campaign at export time

Export the same leads to your CRM, choosing to update existing contacts and skip the rest, matched on email, writing the campaign name and date to a property you created in the CRM first, so reps can see who is mid-sequence.

Free plan: 200 credits a month, 100 rows per table, no card

6 steps to build it

Before you start

A list with work emails checked by Verify email and an ICP score on each lead

A campaign in your sequencer, ready to take a CSV upload

A CRM property for the campaign name and date, created once

1

Filter to the segment

Keep only leads whose Deliverability is valid and whose ICP score clears your cut-off. Catch-all addresses the second verifier could not settle go in a separate, smaller batch.

2

Write an opening line for each lead

Add an AI agent that writes one sentence per lead from that lead's own research. Run it on the first 10 leads and read the drafts before running it across the segment, then filter out anyone left without a line.

3

Name fields to match sequencer variables

Give every field the sequencer needs a short, lowercase header with no spaces, such as opening_line, and map it as a custom field at import so it becomes a variable in the copy.

4

Export the segment as a CSV

Click the table's name, then Export to file, then Export to CSV. The file matches what you see: filter, sort, and field order carry across, and anything hidden stays out. The export costs no credits.

5

Upload to your sequencer

Add the CSV to a campaign in your sequencer and check the mapping before confirming. Point opening_line at the personalization or icebreaker field, or keep it as a custom variable, and turn on the duplicate check.

6

Mark the campaign at export time

Export the same leads to your CRM, choosing to update existing contacts and skip the rest, matched on email, writing the campaign name and date to a property you created in the CRM first, so reps can see who is mid-sequence.

Free plan: 200 credits a month, 100 rows per table, no card

Exporting leads to a sequencer: common questions

Can I export leads to my sequencer as a CSV?

Yes. Filter your list to the segment you want, export it as a CSV, and upload the file to a campaign in your sequencer. Map the enriched columns as custom fields during the import, so fields like an opening line travel with each lead.

How do I send leads to a sequencer with custom fields?

Give each enriched field a short header with no spaces, export the CSV, and map each header to a custom field during the import. The custom field is what you reference as a variable in the email copy.

Should I verify emails before uploading them to a sequencer?

Yes. Bounces count against your sending domain, not the sequencer, and a new domain has no reputation to absorb them. Verify email is up to 0.8 credits an address in Oneprofile, or up to $16 per 1,000, so only deliverable addresses go out.

Does exporting leads to a CSV cost credits?

No. Downloading a CSV or Excel file costs nothing. Credits are spent on the enrichment, verification, and AI steps that run before the export, and each of those shows its cost before it starts.

How do I keep my CRM updated after exporting leads to a sequencer?

Write a marker at export time: match each lead on email and push the campaign name and date to a CRM property you set up for it. Replies can then log through the sequencer's own CRM connection where your plan includes one, or run the sequence in Oneprofile instead.

What happens to leads that fail email verification before the import?

Leave them out of the file. Filter the segment to leads whose Deliverability is valid before you export. Catch-all addresses come back marked catch-all unless a second verifier you switch on settles them, so import any left as their own small campaign, ideally from a separate mailbox.

About this article

Photo of Utku Zihnioglu

Utku Zihnioglu

CEO & co-founder

Serial entrepreneur who built infrastructure companies handling billions of requests. Now leads engineering at Oneprofile, which finds the people worth talking to, researches each one, and follows up until they reply.

Drafted with AI from our product docs and code. Utku Zihnioglu answers for what it says.

Send your sequencer only the leads worth a mailbox slot

Verify, score, and write an opener for each lead, then export the segment as a CSV.

Free plan: 200 credits a month, 100 rows per table, no card

Send your sequencer only the leads worth a mailbox slot

Verify, score, and write an opener for each lead, then export the segment as a CSV.

Free plan: 200 credits a month, 100 rows per table, no card