Migration hub
Move from Instantly or Smartlead one campaign at a time.
Use your own source API key for a read-only compatibility check, confirm the records that can be transferred, and keep the existing platform running while you cut over one campaign at a time.
Choose your source
A guided path for each platform.
Plan a move from Instantly
Check current campaign, lead, account-metadata, and block-list coverage before transferring data. Connect business inbox credentials separately for authenticated sending.
Plan a move from Smartlead
Confirm the selected campaign structure, leads, account metadata, and block-list records exposed by the current API, then review every transferred record before launch.
Import safety
Designed to preserve the decisions that protect senders.
Verify before transfer
Check the current source API and available records before MailSequence creates anything.
Deduplicate contacts
Match by email so importing the same lead does not create unnecessary duplicates.
Never un-suppress
An imported record cannot reverse an existing unsubscribe, bounce, or block decision.
Resume safely
Interrupted work can continue instead of forcing an operator to restart the entire import.
Keep tenants isolated
Imports bind to the selected workspace so one client's records do not enter another client's operation.
Export freely
Your data can leave through CSV and the public read API; the migration story works both ways.
Parallel cutover
Move one campaign. Prove the workflow.
Do not cancel the source platform first. Audit one stable campaign, verify compatibility, transfer supported records, connect or purchase business inboxes, check limits and suppressions, enable warmup, then launch a controlled batch.
Cutover checklist
[x] Source API key connected[x] Campaign selected
[x] Source compatibility checked
[x] Transfer scope documented
[x] Suppression records confirmed
[ ] Business inboxes connected
[ ] Limits and schedules reviewed
[ ] Warmup and health checked
[ ] Controlled launch approved
What does not transfer automatically
Reconnect credentials after the transfer.
- Google Workspace and Microsoft 365 credentials must be connected through MailSequence OAuth.
- The plan includes its listed provisioned-inbox allowance; additional inboxes cost extra.
- DNS and sending readiness must be reviewed before launch.
- Third-party subscriptions and source-platform billing remain under your control.
- Use historical results as context. Future delivery will vary.
FAQ
Frequently asked questions
Should I cancel Instantly or Smartlead before migrating?
No. Keep the source platform available while you check compatibility, transfer, and review one campaign. Cut over only when inboxes, suppressions, limits, warmup, and reply handling are ready.
Does MailSequence need my source password?
No. The importer uses an API key you create in the source platform. Mailbox credentials are connected separately through OAuth or replaced with configured business inboxes purchased in-product.
What happens if a transfer is interrupted?
The migration workflow is designed around recorded batches and resumable processing, but source compatibility must be confirmed before relying on that path.
Can an import re-enable an unsubscribed contact?
No. Imported data never un-suppresses an address. Existing unsubscribe, hard-bounce, and block decisions remain protected.
Can I migrate from another tool?
Smartlead and Instantly have a staged migration workflow that begins with a compatibility check. Other sources use CSV and the public import API, subject to the supported schema and suppression rules.
How long does migration take?
Readiness depends on current source API compatibility, source size, inbox connection, DNS, warmup, and review. We do not promise a fixed first-campaign deadline.
Switch one campaign before you switch everything.
Choose the source platform, verify compatibility, and plan the first cutover.