GTM use case · Editorial decision guide
Outbound campaign migration: preserve state, replies and suppression
Treat outbound campaign migration as a state transfer, not a CSV upload. Our editorial recommendation is to pause enrollment and sending, migrate suppression first, preserve conversations separately, and classify every contact before granting the destination permission to send. A copied sequence does not carry the whole campaign's history. This documentation-backed guide uses Instantly's explicit export and transfer boundaries to explain a general migration process; it is not a hands-on test of cross-platform compatibility.
Reviewed . Based on linked public documentation, not hands-on benchmarking. Recommendations and workflow designs are Cheetah assessments. Features and commercial terms can change.
Decision comparison
On narrow screens, scroll the table horizontally.
| Artifact | Instantly documentation boundary | Recommended destination treatment |
|---|---|---|
| Campaign configuration | Workspace import copies sequence, schedule and settings | Inspect variables, sender assignments and local-time meaning[1] |
| Leads | Not included in campaign sharing; separate export/import needed | Classify by prior contact and current eligibility[1][2] |
| Replies | Not included in campaign sharing; no interface-wide bulk Unibox export | Preserve via documented API route or an authorized conversation archive[1][2] |
| Progression status | Moves do not preserve Completed or Reply received progression | Do not assume interest labels prevent renewed sending[3] |
| Blocklist | Separate address/domain export and enforcement surface | Install and reconcile before audience enrollment[2][4] |
| Historical analytics | Campaign sharing excludes analytics; moved leads start fresh tracking | Retain old campaign identifiers and report pre/post periods separately[1][3] |
Inventory the objects a campaign export does not contain
List sequences, variants, variables, lead memberships, contact and interest statuses, sender accounts, reply threads, suppression rules, schedules, webhooks, ownership, and reporting identifiers. Assign an owner to each artifact and document its export path. Include dependent CRM and enrichment workflows: a perfectly copied campaign can still receive duplicate enrollments if the old integration remains active.
Instantly says workspace campaign imports copy sequence, schedule, and settings but exclude leads, analytics, and replies. Its export documentation describes separate lead, account, activity, analytics, and blocklist exports. These are different artifacts, not a complete workspace backup. Read the destination's documented import behavior independently, especially for a different vendor. Treat every unmapped field or unsupported state as a hold that must be resolved before sending, rather than accepting the importer's default.
[1][2]Freeze outbound actions while keeping inbound reply coverage
Set a migration cutoff with a precise timestamp and timezone. Stop new enrollment sources and pause sending at the origin, but keep the mailbox and reply-handling process available. A prospect can answer an earlier email during the freeze. Our recommended control is a single owner for each contact's next action, with origin and destination incapable of independently scheduling the same follow-up.
Capture an initial snapshot and a final change set for replies, objections, and status changes that arrive during the migration. Preserve source event times rather than substituting import times. Reconcile queued activity and investigate uncertain sends before moving those contacts into an active destination audience. A pause is not proof that every worker stopped instantly, so treat events near the cutoff carefully. Never make a test send to real prospects simply to demonstrate that the new connection works.
[2][1]Move preference enforcement before moving sendable audiences
Export and reconcile address- and domain-level blocklists, plus your authoritative preference ledger with reasons and scope. Load enforcement identifiers at the destination before audience enrollment. Instantly documents separate blocklist exports and says the Blocklist tab prevents imports and contact in ongoing campaigns. Its connected Google Sheets blocklist is import-only, so do not confuse a successful sheet connection with protection for already active leads.
Retain the preference evidence outside an identifier-only enforcement list. Include objections arriving after the snapshot in the final change set. The ICO recommends minimal suppression records so future imports do not reintroduce someone who objected. Migration does not reset that preference. If the destination cannot enforce a required exclusion, hold the affected audience outside active campaigns rather than relying on operators to remember not to resume it.
[2][4][5]Map sequence progression separately from interest labels
Keep last sent step, last sent time, next scheduled action, response state, interest classification, and eligibility as distinct fields. 'Interested' describes a relationship outcome; it is not the same thing as 'do not send another automated step'. Likewise, completed means the prior plan ended, not that a new campaign may restart it. Build a documented state translation rather than matching labels that merely sound similar.
Instantly's move documentation warns that campaign progression statuses such as Completed and Reply received are not preserved even when interest status is preserved. Its example says a completed contact can become Contacted and sendable in the destination campaign. Do not assume cross-workspace CSV imports restore more than documented same-workspace moves. Our recommended default is to keep previously contacted records on hold unless their next action is explicitly established and supported by the destination.
[3][2]Preserve conversations without pretending they were imported as threads
A reply archive should retain contact identifier, sender account, received time, message content, available message and thread identifiers, classification, and current owner. Preserve the association to the originating campaign and sequence. Document what the export actually provides. If message identifiers or headers are absent, do not manufacture them or promise the destination can continue the original thread automatically.
Instantly says there is no direct interface method to bulk export all Unibox replies and points to its Email API for reply content, timestamps, account, and lead address. Campaign sharing excludes replies. An accessible archive is useful continuity, but it is not equivalent to restoring native inbox threading. Keep active conversations assigned to a human and maintain origin access until the receiving team can read the necessary context and handle new inbound replies without duplicate responses.
[2][1]Reconcile identities and states rather than only row counts
Compare stable source contact identifiers, normalized address keys, campaign memberships, preference exclusions, and state totals. Row-count equality can conceal a duplicate replacing a missing record. Retain a mapping from old campaign and contact IDs to new ones. Review rendered variables and schedule semantics before activation: empty custom fields, changed timezone interpretation, or a sender assignment error can make an otherwise accurate import unsafe.
Hypothetical example: 200 source contacts include 90 never contacted, 70 completed, 25 with active conversations, and 15 suppressed. The destination should not contain 185 newly sendable contacts. Only the 90 never-contacted records are candidates for ordinary first-step enrollment, subject to fresh eligibility checks; the other categories need separate treatment. These illustrative counts explain state reconciliation, not actual account data, a vendor limit, or an expected migration success rate.
[3][2][4]Authorize the destination once and preserve a non-sending recovery path
Release a defined cohort only after suppression, state mapping, conversation ownership, variables, and sender assignments are accepted. Keep the origin paused and disable obsolete enrollment integrations. Assign one owner to authorize sending; an import finishing is not authorization. Preserve a read-only migration receipt with cutoff, exported artifacts, unresolved holds, ID mappings, and the final change-set reconciliation.
If the destination behaves incorrectly, pause it first. Do not resume the old campaign from its pre-cutover snapshot without incorporating new replies, sends, and opt-outs. Instantly notes that original campaign analytics remain with the origin while moved contacts start fresh tracking. Keep pre- and post-cutover reporting separate with common contact mappings instead of summing apparently comparable counters. Decommission origin access only after reply continuity, record retention needs, and accountable owners are settled.
[3][2][5]Frequently asked questions
Does sharing an Instantly campaign move all its data?
No. Instantly explicitly says sequence, schedule and settings are copied, while leads, analytics and replies are excluded. Export those artifacts separately and verify the destination's import support. A visible campaign at the destination is not evidence that its contact history or suppression arrived.[1][2]
Can preserving interest status prevent completed leads from restarting?
Do not rely on it. Instantly documents that progression states such as Completed and Reply received are not preserved by its move operation even when interest labels remain. Treat sequence progress and contact eligibility as separate migration fields, and hold prior contacts until their next action is explicit.[3]
How do I preserve replies if the interface has no bulk export?
Instantly points to its Email API for replies and associated content and timestamps. Use an authorized export process and document the available identifiers. An archive can preserve context without restoring native threading; keep active conversation owners and inbound coverage until continuity is established.[2]
When is it safe to cancel the origin subscription?
After required exports, retention decisions, and reply continuity are complete. Instantly says dashboard export access requires an active main subscription and recommends exporting important data before expiry. Cancellation timing should follow the migration acceptance decision, not the first successful sequence import.[2]
Relevant Systems Lab skills
Inspect permissions, external actions and provider costs before installing. A catalogue link is not an endorsement or proof of compatibility.
- CRM migration and consolidation skill
Organize identity mapping, state reconciliation and accountable cutover ownership.
- Inbox lifecycle manager skill
Plan sender continuity and inbound coverage without restarting old conversations.
- RevOps change management skill
Define release responsibility and communicate the migration's operating boundaries.
Sources and research limits
Source notes state the scope of the evidence. No deliverability, revenue or model-quality outcome is established by a vendor documentation page.
- [2] Instantly: How to export data from your accountChecked
Retrieved separate lead, account, activity, analytics and blocklist exports, active-subscription requirement, and reply API route with no direct interface-wide bulk Unibox export.
- [3] Instantly: How to move and copy leadsChecked
Retrieved distinction between interest and progression statuses, completed leads becoming sendable, fresh destination tracking and separate cross-workspace export/import.
- [4] Instantly: Global BlocklistChecked
Retrieved upload and ongoing campaign enforcement for Blocklist-tab entries, versus import-only connected Google Sheets checking.
- [5] ICO: Respect people's preferencesChecked
Retrieved preference scope, objections and minimal suppression records intended to prevent future reintroduction.