Migrate Smartlead to Instantly Keep Reply History: 2026 Playbook
By Puzzle Inbox Team · May 22, 2026 · 8 min read read
Migrate Smartlead to Instantly keep reply history with this 2026 playbook covering export formats, thread preservation, mailbox handoff, and zero-downtime cutover steps.
You can migrate Smartlead to Instantly and keep reply history intact, but only if you export threads via IMAP before disconnecting mailboxes - the in-app exports do not include conversation depth.
Switching sending platforms mid-quarter is brutal if you do it wrong. The most common migrate Smartlead to Instantly keep reply history mistake is assuming the platform export covers everything. It does not. Smartlead's CSV export gives you campaign metadata, contact lists, and reply flags. It does not give you the actual message threads. Those live in the mailbox itself, and if you disconnect the mailbox before pulling them, you lose conversation context that your AEs need to close deals.
Here is the order of operations that preserves both data and revenue.
Pre-migration audit (do this 2 weeks before)
Pull a full list of active campaigns in Smartlead. Identify any with reply rates above 2% - these are your "do not interrupt" sequences. Pull the active reply queue and count open conversations. Anything currently in back-and-forth needs special handling so the prospect does not get re-enrolled on the new platform mid-thread.
Export contact-level data: emails, statuses, reply flags, last-touched timestamps, and custom variables. Save the CSV with a date stamp.
The mailbox inventory step everyone skips
List every connected mailbox in Smartlead with: provider (Google Workspace, Microsoft 365, custom SMTP), warmup status, daily send cap, and current reputation score. You will rebuild this in Instantly, and missing one mailbox means an underbuilt sending pool on day one.
Reply history preservation: the IMAP step
This is the load-bearing step. Smartlead sends through the connected mailbox, so all reply threads physically live in that mailbox (in the Sent folder and in conversation threads in Inbox). As long as you do not disconnect the mailbox from Smartlead before connecting to Instantly, the threads stay intact.
The risk: if you disconnect the mailbox and then reconnect via OAuth to Instantly, some providers (notably Microsoft 365 with strict security policies) will re-scope tokens in a way that breaks Smartlead's reply detection on past threads. The fix is to overlap - connect to Instantly first, verify thread visibility, then disconnect from Smartlead.
Archive Smartlead conversation data separately
Smartlead's "Master Inbox" stores parsed reply data with sentiment tags and AE assignments. Export this via the API (the UI does not expose a bulk download). The endpoint is /api/v1/campaigns/{id}/inbox-history. Pull paginated, save as JSON, store somewhere your AEs can search.
Cutover sequence
Day 1: Create Instantly workspace, invite team, configure sending defaults (timezone, throttling, tracking domains). Connect the same tracking domain you use in Smartlead so click data stays consistent.
Day 2-3: Connect 25% of mailboxes to Instantly. Do not disconnect from Smartlead yet. Run a small test campaign through Instantly to validate sending, tracking, and reply detection. Verify warmup picked up the existing reputation.
Day 4-7: Connect remaining mailboxes. Pause new campaign starts in Smartlead but let existing campaigns finish their sequences. This is the most important day - active sequences must complete naturally so prospects do not get whiplashed.
Day 8-14: parallel run
Build new campaigns in Instantly. Import contact lists from your CSV. Use the "exclude" list feature to prevent any contact who replied in Smartlead from getting re-enrolled. Run new sequences from Instantly, finishing sequences from Smartlead. Reply detection should work in both tools because the mailbox is the source of truth.
Common failure modes
Failure 1: duplicate sends. If you import the Smartlead contact list to Instantly without filtering on "replied" or "interested" status, you will re-email people mid-conversation. Filter ruthlessly.
Failure 2: lost custom variables. Smartlead and Instantly handle merge fields slightly differently. Test one campaign end-to-end before mass migrating - check that {{first_name}}, {{company}}, and your custom fields render correctly.
Failure 3: warmup reset. If you disconnect a mailbox from Smartlead's warmup before Instantly's warmup is active, you create a gap. Schedule the warmup handoff so there is overlap of at least 48 hours.
The Clay integration handoff
If you push enriched data from Clay to Smartlead via the native integration, swap the integration to Instantly on day 8. Test with a small batch first - the field mapping defaults are different.
Post-migration validation
Week 3: pull reply rates for the new Instantly campaigns versus the matched Smartlead baseline. Expect a 10-20% temporary dip as new sequences ramp - that is normal. If the dip persists past week 4, audit deliverability, not the migration.
The full migrate Smartlead to Instantly keep reply history process takes 14-21 days end to end. Rushing it costs you more in lost replies than the migration saves you in tool spend.