Migrate from Smartlead to Reply.io Without Losing Your Sending Domains

The trigger is almost always the same. A client pings me because their Smartlead reply rates have slipped two points in a quarter, support tickets are sitting open for five days, or they want LinkedIn steps baked into the same sequence without duct-taping a second tool on top. At that moment, Reply.io becomes the obvious next conversation. The question is never really “should we switch.” It is “how do we move three sending domains and a dozen live sequences without torching deliverability.” That is exactly what this guide covers.

Before you migrate: the prep checklist

Do not skip this section because you are eager to get into Reply.io. I have watched teams blow up their primary outbound domain by connecting it to a new platform while the old one was still sending. Thirty minutes of prep here saves a week of deliverability recovery.

Gather the following before you touch a single setting:

• Active sequences. Screenshot or document every step: subject lines, body copy, wait days, conditions. Smartlead has no native sequence export, so this is manual.
• Lead exports. In Smartlead, go to Leads > export CSV for every campaign you intend to migrate. Include the status column so you know who replied, who bounced, and who is mid-sequence.
• Mailbox inventory. List every sending address, the Google Workspace or Microsoft 365 account it lives in, and its current daily sending limit in Smartlead. You will re-enter these one by one in Reply.io.
• DNS records. Pull the current SPF, DKIM, and DMARC TXT records for every sending domain from your DNS provider (Cloudflare, Route 53, wherever). You need these on hand when Reply.io gives you its own DKIM selector.
• Warm-up status. Note the warm-up score and current daily ramp for each mailbox in Smartlead. Accounts with a warm-up score below 70 should not be migrated until the score recovers, or you accept the risk of starting fresh.
• Pause, do not delete. Set all active Smartlead campaigns to paused. Do not delete them. You will want the data for comparison reporting later.

Step-by-step migration

What breaks and what does not transfer

The gotchas in this migration are predictable once you know where to look. Here is what I have seen trip up teams most often, and a few of these surprised even teams who had done platform migrations before.

What does not transfer:

• Smartlead’s A/B test data stays in Smartlead. You cannot export winner variants with statistical context.
• Inbox rotation logic is rebuilt from scratch. Reply.io handles inbox rotation differently (account-level vs. campaign-level), so your rotation ratios need to be reconfigured manually.
• Warm-up reputation is not portable. A mailbox with a 90-day warm history in Smartlead starts from zero reputation with Reply.io’s warm-up network. The underlying domain reputation from SPF/DKIM alignment with ISPs does carry over.
• Unsubscribe lists. Smartlead stores opt-outs per campaign. Export these and upload them as suppression contacts in Reply.io before importing any leads.

# Both records coexist safely:
smartlead1._domainkey.yourdomain.com  TXT  "v=DKIM1; k=rsa; p=..."
reply1._domainkey.yourdomain.com      TXT  "v=DKIM1; k=rsa; p=..."

Verify it worked

Before you declare the migration complete, run these four checks. Teams that skip even one of them tend to find out the hard way three weeks later when a domain gets flagged.

1. MX Toolbox DKIM lookup. Enter your domain and Reply.io’s selector at MXToolbox DKIM lookup. You should see a valid public key returned. If it errors, DNS has not propagated yet or the record was entered incorrectly.
2. Send a test sequence to a seed inbox. Use a personal Gmail or a tool like Mail-Tester to send a real Reply.io sequence email and check the spam score. A score of 9/10 or above means auth is clean.
3. Bounce rate below 2% after 500 sends. Pull the Reply.io campaign analytics after the first real batch. Anything above 2% bounce on a clean list means either the lead import included bad addresses or there is a deliverability issue that needs attention now, not next week.
4. Suppression list confirmed. Search for three known opt-out addresses from your Smartlead exports in Reply.io’s suppression list. If they do not appear, your unsubscribe import did not complete correctly.

Who should switch and who should stay

Smartlead alternative: Reply.io vs. staying put

Choose Reply.io if

• You want LinkedIn, phone, and SMS steps inside the same sequence without a separate tool.
• Your team books calls and wants a built-in meeting scheduler tied to the sequence.
• You need CRM sync (HubSpot, Salesforce, Pipedrive) with two-way activity logging out of the box.

From $49/user/month Try Reply.io →

Choose Smartlead if

• You run high-volume pure cold email (10k+ emails/day) across many sending accounts and need cheap mailbox slots.
• Your workflow is email-only and you do not need multichannel steps.
• You rely heavily on Smartlead's AI-powered inbox categorization and warm-up scoring.

From $39/month Stay on Smartlead →

Choose Instantly if

• You want an even cheaper per-mailbox model than Smartlead with unlimited sending accounts on paid plans.
• Your agency manages multiple client domains and needs clean workspace separation.
• Deliverability analytics and warm-up are your primary feature requirements.

From $37/month Try Instantly →

Choose Lemlist if

• You want image and video personalization inside emails (Lemlist's core differentiator).
• Your sequences rely heavily on dynamic landing pages per prospect.
• You are a small team who wants an all-in-one prospecting and sequencing tool.

From $39/month Try Lemlist →

I have watched the Instantly vs. Smartlead vs. Lemlist decision come up repeatedly for agencies, and it almost always comes down to mailbox economics versus channel breadth. For teams that have already outgrown pure email and need CRM-connected multichannel sequences, Reply.io is where I keep landing. For teams who live and die by raw email throughput at the lowest cost per mailbox, Instantly or Smartlead still win on economics. Full stop.

If your migration anxiety is really about deliverability infrastructure rather than the sequencing tool itself, the domain-auth challenges that surface in phone-stack migrations are worth reading too. The overlap window and dual-auth principles apply across platforms.

One week to a cleaner outbound stack

The Smartlead to Reply.io migration is not technically hard. It is operationally unforgiving. The teams that botch it skip the prep phase, delete DNS records too early, or import their full lead list without filtering out bounces and opt-outs first. Follow the overlap window religiously. Verify DNS with MXToolbox before you send a single real email. Rebuild your sequences from screenshots before you disconnect anything.

Done right, you come out the other side with multichannel sequences, cleaner CRM sync, and a Reply.io setup your whole GTM team can actually use, not just the one SDR who remembered where the Smartlead settings live.