Email marketing migration
Move your email marketing without losing opt-ins, history, or control.
This product preview maps the people, permission, content, logic, and history involved in an email-platform move instead of treating it as a simple CSV import. It shows what is in the old account, how fields would map, what a no-change preview finds, and how the final move would be checked.
- Preview first
- Review the move before the new account changes
- Permission first
- Opt-ins and do-not-send statuses keep their meaning
- A way back
- The proposed plan lists changes that could be undone
The complete move
What is an email marketing platform migration?
An email marketing platform migration moves more than email addresses. It also moves permission settings, audiences, content, automations, history, and related customer data. Importing addresses alone leaves behind the rules that decide who may receive what.
People
Subscribers, identities, fields, tags, and audience membership.
Permission
Opt-ins, unsubscribes, bounces, complaints and other do-not-send statuses.
Work
Templates, campaigns, forms, automations, assets, and owners.
History
Past sends, reports, results, decisions and their original records.
See it before you move it
How does a Moosewave migration work?
First, Moosewave would inventory the old account and preview the move without changing the new one. The move begins only after a person reviews what is included and what the checks found. This is a workflow preview, not a live migration tool.
Mailchimp, step 1 of 6: Inventory
Read the source
See the whole account before choosing what moves.
Moosewave lists the people, permission settings, audiences, content, automations, history and connected tools in the old account. Each item is marked to move, rebuild, leave behind or review.
- Source account
- Attached to this plan
- Item totals
- Recorded by type
- Connected tools
- Visible before selection
- People & permissionProfiles, audiences, opt-ins and do-not-send statuses Found
- Audience structureTags, fields, groups and saved audiences Found
- WorkTemplates, campaigns, forms and automation steps Found
- HistoryPast sends, reports and their original records Found
- 01
Inventory
The intended flow reads the old account and lists its audiences, permission settings, messages, rules and connected tools.
- 02
Preview
The intended preview maps the selected data without changing the new account.
- 03
Check
Compare totals, field choices, permission settings and anything that still needs a team decision.
- 04
Move
The proposed approval applies only to the reviewed data. Imported automations remain paused until your team starts them.
- 05
Final sync
The proposed final sync brings over later changes and checks the new account again before your team switches platforms.
- 06
Check & undo
The intended plan checks the result and keeps a clear way to undo the imported changes.
Migration planning detailsOpen the transfer map, old-platform notes, deliverability plan, final checks, switch plan and way to undo an import.
Item by item
What moves to Moosewave?
In the intended plan, people, permission, audience logic, editable work, and past activity are reviewed together. Every item found gets a clear result rather than silently disappearing between an export and an import.
The design matches one person across several old audiences while preserving membership, tags, fields, and conflict history. Learn how Moosewave handles this in Moosewave Audiences.
| Item | Intended outcome | What it means |
|---|---|---|
| 01Subscribers & matching | Matched | Profiles are matched by their source ID and email. Duplicate merges keep a record of where each value came from. |
| 02Opt-ins & do-not-send list | Protected | Opt-ins, unsubscribes, bounces, complaints and unknown permission stay distinct. Anyone on a do-not-send list remains blocked from email. |
| 03Fields, tags & membership | Preserved | Custom fields, tags, groups, interests, list membership, and source relationships retain their meaning. |
| 04Segments & audiences | Rebuilt | Rules that Moosewave supports become editable audiences. Any rule tied to the old platform stays listed for your team to rebuild or leave behind. |
| 05Templates & content | Editable | Templates, variables, assets, and plain-text content move into work your team can inspect and continue. |
| 06Automations & forms | Prepared | Starting events, wait times, choices, actions, signup sources and connected tools become paused work your team can review. |
| 07Campaigns & reports | Remembered | Past campaigns, reports and their original records remain history. They do not become new drafts that could be sent. |
| 08Commerce & subscriptions | Connected | Customer, purchase, product, cart and subscription details stay beside the records that use them. |
Bring the platform you outgrew
Which platforms can Moosewave migrate from?
The preview shows possible ways to move from Mailchimp, Klaviyo, HubSpot, ActiveCampaign, Kit, Brevo, Beehiiv, MailerLite, Customer.io, Substack, Omnisend, Drip, Campaign Monitor, Constant Contact, AWeber, Flodesk, Loops, Bento, Sendy, and structured CSV exports. Inclusion here is not a claim of a live or self-serve migration from that platform.
Connect the old account
A proposed way to read the old account directly and keep the move tied to the account your team selected.
- MailchimpPreview path · Connected account migration
- KlaviyoPreview path · Connected account migration
- HubSpotPreview path · Portal-connected migration
- ActiveCampaignPreview path · Connected account migration
- Customer.ioPreview path · Workspace-connected migration
- BeehiivPreview path · Connected publication migration
- KitPreview path · Connected account migration
- BrevoPreview path · Connected account migration
- MailerLitePreview path · Connected account migration
Import a provider file
A proposed way to match and check a provider's structured export before importing it.
- SubstackPreview path · Checked file import
- OmnisendPreview path · Checked file import
- DripPreview path · Checked file import
- Campaign MonitorPreview path · Checked file import
- Constant ContactPreview path · Checked file import
- AWeberPreview path · Checked file import
- FlodeskPreview path · Checked file import
- LoopsPreview path · Checked file import
- BentoPreview path · Checked file import
- SendyPreview path · Checked file import
Import a subscriber file
A proposed way to use a well-formed subscriber file while keeping opt-in status separate from audience choices.
- Structured CSVPreview path · Universal subscriber migration
Protect the first send
Will migration affect email deliverability?
A platform move does not erase the reputation attached to your sending domain, and a rushed switch can still damage placement. The intended migration workflow checks opt-ins and do-not-send statuses first, then checks sending-domain authentication, tracking configuration, and volume before a first send.
- 01
Permission before targeting
Opt-ins and do-not-send statuses are compared before a new audience can receive email.
- 02
Authentication before volume
SPF, DKIM, DMARC and tracking-domain settings are checked before the platform switch.
- 03
A deliberate volume plan
The transition reflects audience quality, sending history, and provider behaviour.
- 04
One active automation
Both platforms are watched during the overlap so the same customer does not receive the same sequence twice.
A record of the move
What does the final check show?
The preview’s check report compares what was found with what would be moved, merged, translated, archived, left out by choice, or left for a team decision. It is an illustrative report, not a record of a completed customer move.
The report shows whether everything selected is accounted for, records permission details, explains duplicate-contact choices, lists field mappings, and notes work still to rebuild or undo.
No cliff edge
Change platforms without losing the review window.
The intended process keeps the old account available while a move is previewed and reviewed. It then brings over later changes and checks the plan again before your team switches platforms. This production workflow is not currently live or self-serve.
- 01
Preview
The complete move is reviewed without changing the new account.
- 02
Overlap
The source stays available while decisions close.
- 03
Final sync
Later changes from the old account are brought over.
- 04
Switch
Only approved data moves; your team decides when automations start.
- 05
Watch
The result and time available to undo the import remain visible.
Undo the import without undoing your team’s other work.
The proposed completed-plan view lists the imported changes and how long they could be reversed. This option is not currently available through this site.
See the safeguardsAfter the move
The migration ends when the new workspace makes sense.
A populated account is not enough. Audiences should still respect opt-ins and do-not-send statuses, automations should keep their messages, and campaigns should keep their reports.
In this preview, a migration is a controlled move. Its ongoing counterpart is a Moosewave integration, whose provider-specific availability must also be confirmed.
Permission comes before targeting
The proposed plan keeps opt-ins, do-not-send statuses, fields, tags and audience membership with each customer.
02Automations remain understandable
The model keeps starting events, choices, messages and owners together. Imported automations stay paused until your team starts them.
03Check before sending
The plan checks domain authentication, sending volume and inbox placement before the first send from the new platform.
04History informs the next send
The preview keeps past campaigns and reports as useful history rather than turning them into new sendable work.
05The workspace stays connected
The intended workspace keeps audiences, campaigns, approvals, messages, customer events, and results connected.
06Your assistant can help with the move
The preview shows an assistant checking selected data, requesting a no-change preview and reading the result through an allowed MCP connection.
Common migration questions
The answers describe the intended migration model. Production migration is not currently live or self-serve, so confirm feasibility before choosing a date to switch platforms.
What data can Moosewave migrate?
The product preview covers subscribers, opt-ins, do-not-send statuses, custom fields, tags, audiences, templates, campaigns, automations, forms, past reports, commerce details, assets and original records. Actual coverage must be confirmed before an evaluation; production migration is not currently self-serve or live.
Which email marketing platforms can I migrate from?
The preview models paths from Mailchimp, Klaviyo, HubSpot, ActiveCampaign, Kit, Brevo, Beehiiv, MailerLite, Customer.io, Substack, Omnisend, Drip, Campaign Monitor, Constant Contact, AWeber, Flodesk, Loops, Bento, Sendy, and structured CSV exports. That list is not a claim that every source has a live production migration today.
Can I preview the migration before moving data?
The intended workflow includes a no-change preview: it lists and maps the selected data without changing Moosewave. This public preview does not accept customer data or run an import.
Will unsubscribed contacts stay blocked?
Yes in the intended design. Unsubscribed, bounced, complained, cleaned and otherwise blocked contacts remain on a do-not-send list, sometimes called a suppression list. Actual source-field coverage must be checked for each evaluation.
What happens to my automations?
The preview shows starting events, waits, choices, actions and audience rules rebuilt as editable automations that remain paused for review. It describes intended behavior, not an automation import available today.
Can my current platform stay live during migration?
The intended plan keeps the old account available while the data is listed, previewed and reviewed. It then brings over later changes before your team switches platforms. This workflow is not currently live or self-serve, so do not schedule a switch from this preview alone.
Will switching platforms affect email deliverability?
A migration does not reset your sending domain's reputation. Email authentication, volume, audience quality and the timing of the switch still matter. The intended process checks these points and preserves opt-ins and do-not-send statuses before sending; confirm the real plan before moving.
Can I roll back a migration?
The design includes a limited period in which listed migration changes could be undone without reversing unrelated team work. This option is not currently live or self-serve, so this preview does not guarantee that an import can be undone.
How long does an email marketing migration take?
Timing would depend on account size, limits imposed by the old platform, automation complexity, and decisions found during review. Production migration is not currently live or self-serve, so Moosewave must first confirm whether a guided evaluation is possible. This preview does not provide a delivery estimate.
Know what will move before anything moves.
Tell us which source and records matter so we can discuss current feasibility. Do not send or upload customer data through the public site.