Migration paths
A careful move should not depend on one connector.
A provider connection, a structured export, or a subscriber file can each begin a move. The dry run should make the limits of each path visible.
Moosewave is in private early access. This page explains the product direction; a described workflow is not a promise that every provider or channel is available today.
Choose the evidence your source can provide.
Different exports contain different degrees of permission, history, and automation detail.
Connected account
Read the selected source under scoped access, then compare the mapped records before import.See connection pathsProvider export
Inspect a structured file for fields, memberships, exclusions, and unsupported resources.See export pathsSubscriber file
Map columns and quarantine invalid rows without treating every address as a fresh opt-in.Review audience rules
Verify before the first message.
The outcome is a reviewed plan, not just a count of imported contacts.
Protect exclusions
Keep unsubscribes, complaints, and other do-not-send decisions ahead of targeting.Read the noteName rebuild work
If a workflow cannot be translated safely, carry the evidence and ask a person to rebuild it.Explore journeysQualify the sender
Check domain authentication and sending pace before contacting the imported audience.Read sender guidance
The next step
Review the move before committing it.
The migration page shows the proposed sequence and the questions a no-change preview should answer.