Lemlist teams tend to have the most elaborate sequences of anyone, liquid syntax conditionals, custom images, dynamic landing pages, multichannel steps with branching across email, LinkedIn, calls and SMS.
All of that is value you built, and none of it exports. Here is how to carry across what matters and what to leave behind deliberately.
The personalisation question
Lemlist’s liquid syntax lets you write conditional logic inside a message, show one sentence if the lead has a given field, another if not. It is genuinely powerful and it is also where most of the rebuild time goes.
Before you recreate it, check how much of it is actually firing. Export your leads and look at fill rates per custom variable. Teams routinely find a conditional branch written for a field that populates on 20% of the list, which means four in five recipients are seeing the fallback anyway.
The practical approach: rebuild the conditionals that matter on fields with high fill rates, and for the rest write one good sentence with a sensible fallback. Personalisation that fails safely covers the thresholds, roughly, below 50% fill you should segment rather than branch.
Custom images and dynamic landing pages are a separate decision. If they are producing measurably better reply rates, keep an equivalent. If they were set up once in 2024 and nobody has tested them against a plain text version since, the migration is a reasonable moment to find out.
What exports from lemlist
| Asset | Export |
|---|---|
| Leads with custom variables | CSV, per campaign |
| Unsubscribes | CSV, pull first |
| Campaign reports | CSV |
| Email account list | Visible in settings |
| Sequences with liquid syntax | No export, copy the raw text |
| LinkedIn connections and history | Stays with the LinkedIn account |
| Reply threads | No export |
| Signal and intent data | No export |
Copy the raw liquid syntax into a document even though you will not paste it back. It is the clearest record of what conditions you were branching on.
The LinkedIn and channel question
Lemlist runs LinkedIn, calls, SMS and WhatsApp alongside email, so your sequences are probably genuinely multichannel. The good news is that the structure translates, you are rebuilding the same shape rather than collapsing to email only.
Two differences worth planning for:
LinkedIn accounts reconnect, history stays put. Your connections, messages and network are properties of the LinkedIn account, not of lemlist. Reconnect the account and nothing is lost. What does not come across is lemlist’s record of which lead got which touch, export your leads with status fields so that survives as data.
SMS does not have a direct equivalent. If SMS is a working channel for you, that is a genuine gap to weigh. WhatsApp covers similar ground in markets where it is the dominant channel, and better in India, LATAM and the Middle East, but they are not the same thing. Be honest with yourself about whether your SMS steps produce replies or just sit in the sequence.
Credits: the comparison that usually prompts the move
Lemlist meters several pools separately. Enrichment credits run roughly $16 to $20 a month for 2,000 credits, which the page equates to about 400 emails or 100 phone numbers. Intent signals are a separate bundle, around $21 to $29 a month for 100 signals. Both are credit-metered per successful result, so cost scales with how much you capture, which matters most on engagement-based capture, where a post that performed produces the most people to reveal.
Outboundry’s model is one credit balance across everything: 1 credit for a lead with a verified email, 0.5 for LinkedIn-only, 10 for a verified mobile, 1 for a company follower. Company records and all 50+ filters cost nothing. Signals runs as a tiered add-on ($19, $49 or $129 a month) with signal leads coming out of an allowance rather than being billed per head.
Run your own last three months through both models before deciding. If you never touch engagement-based capture the gap narrows a lot; if you run it weekly, it is probably the whole reason you are reading this.
The plan
Week 1, export and audit
Unsubscribes first, then leads with every custom variable, then campaign reports. Copy sequences including the raw liquid.
Then do the fill-rate audit described above. It decides how much of the rebuild is worth doing.
Week 2, set up in parallel
Create the workspace. Load the suppression list before any leads. Recreate custom fields using the same variable names as lemlist so your merge fields map cleanly.
Bulk-connect email accounts, and connect LinkedIn accounts. Both can stay connected to lemlist meanwhile.
Week 3, rebuild one multichannel sequence
Start with your best-performing campaign, including its LinkedIn steps. Run at 20% of volume while lemlist carries the rest.
Rebuild conditionals only where fill rates justify them. Give every merge field a fallback, the editor will not let you save a signal variable without one, which is a constraint worth having.
Week 4, shift and close
Ramp 30% every few days. Compare reply rates on comparable segments across both tools while you still can. Verify suppressions match. Export final reports, then cancel.
The short version
The sequences are the work. Audit your custom variable fill rates before rebuilding conditionals, because a good share of lemlist liquid logic turns out to be branching on fields most of the list does not have.
LinkedIn accounts reconnect with their network intact. SMS has no direct equivalent, so weigh that honestly rather than assuming WhatsApp replaces it.
And run your real usage through both credit models. If engagement-based capture is part of your motion, that comparison is likely the whole decision.
Next: the universal migration checklist, or lemlist alternatives compared.
Frequently asked questions
Can you export sequences from lemlist?
No. Leads, unsubscribes and campaign reports export as CSV; sequences including liquid syntax do not. Copy the raw text into a document before cancelling.
Do I lose my LinkedIn connections when leaving lemlist?
No. Connections, messages and network are properties of your LinkedIn account, not of lemlist. Reconnect the account elsewhere and everything is intact.
Does Outboundry support SMS like lemlist?
No. WhatsApp covers similar ground and performs better in markets where it is the dominant business channel, but it is not a direct SMS replacement. Weigh it against how many replies your SMS steps actually produce.
How does lemlist’s pricing compare on credits?
Lemlist meters several pools separately (enrichment credits and intent signals are billed as distinct bundles, each charged per successful result. Outboundry uses one balance) 1 credit for a verified email, 0.5 for LinkedIn-only, 10 for a mobile, with Signals on a tiered allowance rather than per-head billing.
