Moving In

Move-in is a done-for-you migration: you give us read-only access to your old platform, we bring your audience across into your SendBeam workspaces in the right order, run the two side by side while you switch your forms and domain over, and hand you a log of exactly what was moved. It is included for every site you run on the Pro and Business plans; request it at sendbeam.io/move-in.

If you would rather do it yourself, the same result is available through CSV import and the suppression list. Everything below applies either way.

What we move

• Subscribers with their names, status and original signup date.
• Suppressions: everyone who unsubscribed, bounced or complained on the old platform stays suppressed here, before a single contact is imported.
• Tags (and, on platforms that use them, groups and lists) as SendBeam tags.
• Custom fields: merge fields, subscriber fields and attributes become custom fields with tidy snake_case keys, up to 30 per contact.
• Language: Mailchimp's own language field, or on any platform a field named language, lang, locale, language_code or preferred_language, fills the contact's language when it is empty, so a multi-language campaign reaches a migrated audience in the right version.
• Consent evidence: the signup IP, confirmation time and signup source wherever the old platform kept them (see below for what each platform can provide).
• Up to 3 forms rebuilt as SendBeam forms, with the embed code ready to swap in.
• Your sending domain, verified in SendBeam before any campaign goes out (how sending domains work).

We support Mailchimp, MailerLite, Kit (ConvertKit), Brevo (Sendinblue) and EmailOctopus through their APIs. From any other platform we work from a CSV export, which carries subscribers, status and fields but usually no consent evidence.

What cannot be moved

• Automations and sequences. No platform exports them in a form another can run. We rebuild the ones you list for us as SendBeam automations; existing subscribers are not re-enrolled in welcome sequences they have already received.
• Paid subscriptions on Substack, Beehiiv, Ghost and similar. The billing relationship belongs to the old platform; paid readers must subscribe again through your new checkout. We move them as ordinary contacts, tagged so you can write to them about it.
• Engagement history (opens, clicks, campaign reports). It stays on the old platform; SendBeam starts measuring from your first campaign here.
• Unconfirmed sign-ups. Someone who never clicked the confirmation email on the old platform is not a subscriber. We leave them out by default; on request we import them as pending, which never sends them email.
• Templates and campaign archives. Recreate the one or two layouts you use as SendBeam templates.

What we need from you

1. A read-only API key for the old platform, or a temporary seat with read access. Send it through the Move-in request page, never by email; we revoke or return it when the move is complete.
2. A list of your sites and which SendBeam workspace each audience should land in. One account can hold every site you run, so nothing needs to be merged unless you want it to be.
3. The automations to rebuild: a short description or screenshots of each one.
4. DNS access for your sending domain, or someone who can add the records we send you — two CNAMEs per domain.
5. A signed scope. The request page produces it; its reference number appears in your migration log.

The order we do it in

1. Suppressions first. Every unsubscribed, bounced and complained address from the old platform is written to your suppression list before anything else. If a later step goes wrong, nobody who opted out can be emailed.
2. Sending domain. Your domain is verified and set as the default from-address so the first campaign from SendBeam arrives authenticated from the address people know.
3. Import. Subscribers are imported with their tags, fields and consent evidence, in chunks, with duplicates skipped so re-running a step never creates a second copy. We then compare counts against the source and stop if anything is short.
4. Parallel run. Both platforms stay live while you switch your forms and links. Send your first campaign from SendBeam to a small segment before the whole audience.
5. 30-day unsubscribe sync. For 30 days after cutover we bring across anyone who unsubscribes through an old email that is still in inboxes, so late opt-outs are honoured here too. After that the old account can be closed.

The evidence we carry

Consent evidence lets you show, for each subscriber, when and how they signed up. Platforms differ in what they keep, and we only carry what the old platform actually recorded:

Each imported contact records the migration as its source, and the consent fields it arrived with are visible on the contact page. Your migration log lists the source platform, the scope reference, who ran the move and when, counts by status, the tags and field keys created, each import step's result and the final count check. Ask for it any time under your data-processing agreement.

Working copies and your data

During the move we hold a working copy of your list: the exact files sent to your workspace. They live on an access-controlled machine, are never emailed or shared, and are deleted once you confirm cutover. Only the migration log, which contains counts and settings but no contact rows, is kept. The API key you gave us is revoked or returned at the same time.

Ready to move? Request a Move-in, or start with a CSV import if you would rather do it yourself.