How to Migrate From Woodpecker to lemlist (Without Hurting Deliverability)

Why teams outgrow Woodpecker and switch to lemlist

Migrating from Woodpecker to lemlist involves exporting your prospect data as CSV files, setting up sending domains and authentication in lemlist, warming up your infrastructure with lemwarm, importing and mapping your leads, then rebuilding your sequences with multichannel steps. The biggest risk is deliverability: switching platforms changes your sending IP, which resets trust with inbox providers, so you’ll want to overlap warmup periods and verify your list before launching.

Now, why do teams make this move in the first place?

lemlist covers email, LinkedIn, calls, WhatsApp, and SMS from one campaign, backed by a 600M+ lead database. Woodpecker stays focused on cold email and mailbox deliverability, with pricing tied to prospects rather than seats. That focus works well for teams that only send email. But once you want to coordinate touchpoints across channels, Woodpecker starts to feel limiting.

Woodpecker supports call and SMS tasks and manual LinkedIn tasks as reminders within sequences, but these are logged steps for the rep to complete manually, not automated actions. There is no built-in phone dialer, no VoIP, no WhatsApp channel, and no voice note capability.

The main limitation is that it has no built-in prospect database, so results depend entirely on the quality of the list you bring. That means you’re stitching together separate tools for prospecting, enrichment, and outreach. lemlist consolidates all of that into one workflow.

What you can and cannot migrate from Woodpecker

Data you can export from Woodpecker

You can export the data of your contacts from your Prospects database or directly from a campaign. To do so, go to a chosen campaign, filter your prospects, then check-mark them and export as a CSV file.

In Woodpecker you can export statistics, data of your prospects, daily, weekly and monthly CSV reports or interest level. So the raw materials for migration (contact info, custom fields, aggregate performance data) are all available.

Data you will lose in the switch

What doesn’t carry over: email thread history, per-step engagement trails (which prospect opened which email at which step), A/B test configurations, and the warmup reputation built inside Woodpecker. This is standard for any platform migration. Save screenshots or download reports before you cancel your Woodpecker account.

Step-by-step migration from Woodpecker to lemlist

1. Audit your Woodpecker account and pause active campaigns

Before touching any data, pause every running campaign. This prevents duplicate sends when you start outreach from lemlist. Review which sequences had the best open and reply rates, because you’ll want to recreate those first.

Flag any prospects who are mid-sequence. If someone received email two of four, you don’t want to restart them at step one in lemlist. A simple tag like “mid-sequence-step-3” in your CSV saves a lot of awkward double-sends later.

2. Export prospects and campaign data

Whenever you want, you can select all prospects with a specific status (or use any of the other filters) and export this list to a CSV file. Do this for each campaign, filtering by status (sent, opened, responded, bounced) so you have clean segments.

Also download your campaign statistics as CSV. This report will give you an overview of your campaign’s performance, presenting basic statistics, like the number of sent messages, and how many of them were bounced or opened.

3. Clean and prepare your CSV files

This step is where most migrations quietly break. A sloppy import means broken personalization, bounced emails, or duplicated contacts.

• •

  Remove bounced and unsubscribed contacts: Addresses that have already bounced should be removed immediately. Carrying them to a new platform serves no purpose and inflates your bounce rate.

• •

  Standardize column headers: lemlist auto-maps specific variable names. Ensure Row 1 contains column names only, no spaces in column names (especially for URLs), each row has an email address (required), and no empty rows between leads — see lemlist’s CSV import guide.

• •

  Flag mid-sequence prospects so they’re routed into the right campaign step

• •

  Check encoding: Make sure your Sheet program is configured to use UTF-8 coding. Google Sheets is the safest option for this.

4. Set up your lemlist account, domains, and mailboxes

Connect your sending domains and configure SPF, DKIM, and DMARC records. DMARC is increasingly non-negotiable. Since February 2024, both Google and Yahoo have required bulk senders to have a DMARC record in place. Microsoft followed suit in May 2025.

If you purchase a sending domain directly inside lemlist, authentication is configured automatically. Otherwise, update your DNS records manually so they point to lemlist’s sending infrastructure instead of Woodpecker’s.

5. Warm up your sending infrastructure with lemwarm

Here’s the part most teams rush through, and it’s the one that causes the most damage.

You can carry over the reputation built on your sending domain and ‘from’ address, provided you don’t change either when you move. But because your IP address will change, inbox providers like Gmail, Outlook, and Yahoo will detect this and begin re-evaluating your sender reputation, and during that review period, they tend to be cautious. Your first few campaigns from the new platform may be more likely to land in spam, which can cause a temporary dip in open and click rates.

lemwarm (included with every lemlist seat) rebuilds that trust by exchanging real emails with real inboxes at a controlled pace. Start lemwarm before you cancel Woodpecker so there’s no gap in warmup activity. Deliverability typically stabilizes within 2–4 weeks with consistent, gradual sending. A short-term drop is not a sign of failure — it is a normal transition.

6. Import leads and map custom variables

lemlist requires Row 1 as column names (email, firstName, companyName, etc.) and Row 2+ as lead data, one lead per row. The required column is email (every lead needs one).

During import, you assign each CSV column to the correct lemlist variable type. This is what makes lemlist recognize fields like {{email}} and {{linkedinUrl}} in your campaign steps — see lemlist’s guide on choosing the right CSV import type.

You can also enrich leads at import time. On the “Enrich leads data” step, choose whether you want lemlist to find/verify emails, find phone numbers, or enrich LinkedIn data. This is a good moment to re-verify email addresses that may have decayed since you last used them in Woodpecker.

7. Rebuild your sequences and launch

Recreate your best-performing Woodpecker sequences inside lemlist. You don’t have to do this manually. lemAgent can generate full multichannel sequences from a plain-language prompt, including timing, branching logic, and channel mix.

The real upgrade here: you can now add LinkedIn, phone, SMS, and WhatsApp steps alongside your email touches, all in one campaign. All replies across channels surface in a Unified Inbox supporting up to 15 email addresses per user. Adding LinkedIn to outreach reportedly generates 2.5x more replies compared to email alone.

Deliverability risks during migration and how to avoid them

Switching email platforms is one of the most disruptive things you can do to your email program. Even if your new ESP offers better features, lower costs, or improved integrations, the transition itself carries real risk. Without careful planning, an email platform migration can damage your sender reputation, tank your inbox placement rates, and cost you the audience trust you have spent years building.

Here are the specific risks and how to handle each one:

• •

  Sender reputation reset: Migrating email platforms hurts deliverability because your new sending infrastructure has no established reputation. The fix: warm up gradually with lemwarm and start with low daily send limits.

• •

  Warmup gaps: If you stop Woodpecker’s warmup on Monday and don’t start lemwarm until Thursday, your domain goes cold for three days. Overlap the two.

• •

  Stale list data: Migrating without verifying the list first is the most common and most damaging mistake, since it introduces bounce risk at exactly the moment your new infrastructure is most vulnerable to reputation damage. Run email verification through lemlist’s waterfall enrichment before sending.

• •

  DNS mismatches: Forgetting to update SPF records for the new sending servers is a close second, producing authentication failures that undermine deliverability regardless of list quality.

Feature mapping from Woodpecker to lemlist

If you’re wondering where a specific Woodpecker workflow lives inside lemlist, here’s a quick reference:

lemlist runs email, LinkedIn, calls, WhatsApp, and SMS natively in one campaign, while Woodpecker treats LinkedIn as a paid add-on.

What lemlist unlocks that Woodpecker does not have

Beyond a feature-for-feature swap, there are capabilities that simply don’t exist in Woodpecker.

Built-in lead database and waterfall enrichment. A 600M+ database, enrichment agents, and intent signals are built in, so you find and qualify accounts without a separate data tool. You can go from “I want to reach CFOs at Series B SaaS companies” to a verified contact list in minutes without leaving lemlist.

AI-powered campaign generation. lemAgent builds full multichannel sequences from a text description of your goal and ICP. Smart messaging cleans data, generates personalized copy, and can even clone your voice for audio notes. Woodpecker has basic AI assist for email copy, but nothing at this level.

Intent signals and agentic enrichment. lemlist tracks high-intent events (hiring, funding, tech stack changes, website visits) and auto-enrolls matching leads into campaigns with context-based personalization. AI enrichment agents pull structured insights from LinkedIn, websites, CRM data, and call recordings to qualify and prioritize leads automatically.

Post-migration checklist

Before you send your first real campaign, verify every piece of the setup:

• •

  DNS authentication: Confirm SPF, DKIM, and DMARC pass for every sending domain

• •

  Warmup status: Verify lemwarm has been running for at least two weeks

• •

  Import accuracy: Spot-check 20–30 imported leads for correct field mapping

• •

  Sequence logic: Send test emails, trigger conditions, verify LinkedIn steps fire correctly

• •

  CRM sync: Confirm leads, activities, and replies flow to your CRM

• •

  Inbox placement test: Use Deliverability Hub to check whether emails hit primary inbox or spam

• •

  Daily send limits: Set conservative caps per mailbox and scale up over two to four weeks

• •

  Old platform shutdown: Cancel Woodpecker only after lemlist campaigns are live and stable

Over to you

Migrating from Woodpecker to lemlist is a straightforward process if you protect deliverability at every step: export clean, verify your list, overlap warmup periods, and ramp volume gradually. The payoff is a single platform that covers prospecting, enrichment, multichannel outreach, and deliverability monitoring in one place.

lemlist’s support team can also walk you through the migration if you’d prefer a guided setup.