Migrate from Instantly to Smartlead (or Back) Without Losing Replies: Audit, Export, Cut Over

Phase 1: The Audit That Prevents Pointless Migrations

• •Score what you actually use: reliability incidents in the last quarter, reply-detection accuracy (test it: OOO vs human, per the classifier categories), API completeness for your dashboard, export quality, per-inbox analytics, and true cost per seat at your volume.
• •Price the migration honestly: setup and re-learning days, integration rebuilds (webhooks, CRM sync, suppression flows), and the cutover risk window. If the delta between tools is smaller than the migration cost, fix the setup instead.
• •The two legitimate triggers we see: reply handling you cannot trust, and API or export restrictions that hold your own data hostage. Price increases alone rarely clear the bar; data hostage situations always do.

Phase 2 and 3: Export, Then Overlap

EXPORT (account still alive):
  □ leads + statuses + custom fields
  □ reply history (CSV/API)
  □ blocklist / suppression list  ← the forgotten one
  □ sequences, templates, schedules
  □ mailbox↔campaign mappings
  □ analytics baselines
  □ webhooks + integrations inventory

CUTOVER (2-week overlap):
  wk 0  stop NEW sequence starts on old tool
        import suppression into new tool FIRST
        dedupe leads vs master DB before import
  wk 0+ same mailboxes connect to new tool,
        new campaigns launch there
        warmup enrolled on new tool, overlapped
  wk 0-2 old unified inbox checked daily for
        stragglers; in-flight sequences finish
  wk 2+ final export refresh → cancel old tool

NEVER: delete inboxes or domains in a migration.
Late replies arrive for weeks (rotation post).

The ordering rule that prevents the two classic disasters: suppression imports before any lead imports (so the new tool cannot email an opted-out contact even for a minute), and lead imports get deduped against your master database with statuses mapped, so finished sequences stay finished. If you built the hub-and-spoke suppression sync, the migration is just adding a spoke, which is the strongest argument for having built it.