MIGRATION GUIDE

Move the workflow without losing the customer context.

A safe migration is an operating change, not a bulk import. Inventory the current system, move one journey at a time, validate the outcome, and keep a rollback path.

Start for free
Phased migrationData validationClear ownership

Migration risks

Protect the work that already functions.

01

Unmapped fields and ownership

02

Automations triggered twice

03

Contacts moved without consent or source context

Recommended migration sequence

Inventory, map, test, validate, then cut over.

  1. 01

    Inventory

    List pipelines, fields, contacts, conversations, calendars, forms, workflows, users, domains, and integrations.

  2. 02

    Map

    Define where each required record, state, owner, consent value, and source will live in Spacebrain.

  3. 03

    Pilot

    Move one bounded workflow and test normal, failure, duplicate, unsubscribe, and human-handoff cases.

  4. 04

    Cut over

    Choose an owner, freeze conflicting edits, migrate, reconcile counts, monitor outcomes, and retain the rollback window.

Migration checklist

Do not call the migration complete until these are verified.

Record counts reconcile

01

Ownership is preserved

02

Consent and source remain intact

03

Automations cannot double-fire

04

Inbound channels reach the right workflow

05

Reports reflect the new system

06

OPERATIONAL CONTROL

Exportability is part of trust.

Keep source exports, mapping notes, validation results, and cutover decisions. Never delete the previous system until records and live workflows have been reconciled and the agreed rollback period has passed.

  • Back up before changing
  • Test with representative records
  • Run parallel only with duplicate protections
  • Document final ownership

Frequently Asked Questions

Migration questions

Clear answers about Spacebrain, setup, and what to expect.

Should we migrate everything at once?

Usually no. Moving a bounded workflow first makes mapping and operational problems easier to find and reverse.

What data should we export?

Export the records and configuration required by your operation, including contacts, fields, owners, opportunities, conversation history, consent, source, calendars, forms, and workflow definitions where available.

How do we avoid duplicate messages?

Pause or isolate overlapping automations, use a controlled pilot cohort, and verify suppression and enrollment state before cutover.

When can we close the old account?

Only after agreed record counts, live routes, permissions, automations, reporting, and rollback requirements have been verified.

SPACEBRAIN

Start with one workflow you can verify end to end.

Create your Spacebrain workspace, document the current process, and migrate only after the success and rollback criteria are clear.

Start for free