Three steps. Every important choice stays visible.

Connect mode avoids a forced ESP cutover. Move mode treats migration as real work. The first offer remains supervised.

  1. 01

    Choose Connect or Move

    Connect is designed to keep Klaviyo as the delivery rail with no forced cutover. Move adds a written migration scope, dual-run, cutover, and rollback plan. Both paths start with one lifecycle decision worth testing.

  2. 02

    Declare and reconcile the data

    The source manifest names the objects and history to import. The data contract requires identity lineage, consent, and suppression to be preserved, with counts, totals, conflicts, duplicates, and unmatched records visible before release.

  3. 03

    Review, launch, and measure

    The pilot contract records the customer facts, permitted treatment, exclusions, message plan, and reason. A lifecycle owner approves it before the first supported Klaviyo delivery. Where volume permits, a holdout shows whether the result earns expansion.

Sources

Declared scope, lineage, consent, and reconciliation

Personably

Reviewed customer decision and brand treatment

Delivery

Existing rail, controlled launch, and holdout

Outcome

Decision record, measured result, and go-forward recommendation