Migrate from beehiiv
Moving from beehiiv to SendRaven.
beehiiv exports every subscriber in one CSV, with a status column, from Settings → Export Data. The full export adds custom fields and statistics, which is the one to take.
The part that is easy to miss is the suppression list. beehiiv keeps hard bounces there rather than in a subscriber's status, so a bounced address can still read Active in the export. Bring the suppression list across before the first campaign.
Export steps checked 16 November 2026 against beehiiv.com/support and developers.beehiiv.com.
- Settings → General Info, pick the publication, then Export Data.
- Under Export Subscribers, choose Export All Subscribers (the full export, with custom fields and statistics). The basic export has only email, status and tier.
- It appears under Historical Exports as Processing; beehiiv emails a link when it is ready, and a Download link appears there too. Both last 24 hours.
- For posts, Export Posts → Export All Posts on the same page.
Let your AI do it
One prompt moves everything from beehiiv.
Paste it into Claude, ChatGPT, Cursor or any assistant with SendRaven connected. It gets your data out of beehiiv, shows you the plan with counts, and waits for your OK before it writes anything.
- Contacts, opt-outs, preferences, templates and automations, in the order that keeps your domain safe.
- Sends nothing, activates nothing and deletes nothing. The first campaign is left as a draft.
- Needs SendRaven connected first: one guide per assistant.
Move my email from beehiiv to SendRaven, using the SendRaven MCP tools. If you don't have them, stop and tell me to connect SendRaven first: https://sendraven.ai/mcp
Getting my beehiiv data:
- If you can reach beehiiv's API (a connector, its MCP server, or code you can run), ask me for an API key and read everything from there.
- If not, tell me exactly what to export and ask me to upload the files here: Settings → General Info → Export Data → Export All Subscribers (the full export, with custom fields and statistics); the Suppression list under Subscribers; and Export Posts.
Before you write anything, show me what you found and your plan, with counts, and wait for my OK. Then bring over everything SendRaven can hold, in this order:
1. Sending domain: check list_sending_domains. If the domain I send from is not there, add_sending_domain, show me the DNS records to publish, and run verify_sending_domain once I say they are live.
2. List: use mine from list_audiences, or create_audience "beehiiv import".
3. Opt-outs before anyone else, so nobody who left is mailed again: inactive subscribers, who unsubscribed (status unsubscribed), and everyone on the Suppression list, hard bounces and spam complaints (status bounced). A bounced address can still read active in the export, so the Suppression list wins. Import them with import_contacts and that status, source "beehiiv". Never import an opted-out person as subscribed.
4. Subscribers: import_contacts in batches of up to 5,000, with first and last name, tags, and custom fields as attributes. Leave out anyone who never confirmed. Do not trigger automations. For a list of more than a few thousand, ask whether I would rather upload that CSV in SendRaven (Contacts → Import) while you do the rest.
5. Templates: posts you reuse (their email HTML, from beehiiv's posts API or Export Posts), with beehiiv's merge tags. Save each with save_template, merge tags rewritten as SendRaven {{variables}} ({{first_name}}, {{email}}), and their unsubscribe links and footers removed: SendRaven adds its own to every marketing email.
6. Automations: automations do not export. From what you can read, or what I describe, rebuild each with create_automation and leave it as a draft.
7. First campaign: tag subscribers the full export's statistics show opening recently as engaged, create_segment on that tag, then draft one campaign to it with create_broadcast and check it with preview_broadcast. A new domain warms up, so it starts with engaged readers.
Rules: send nothing, activate nothing, and delete nothing, in beehiiv or in SendRaven. Finish with a table of what came over (contacts imported and updated, suppressed, topics, templates, automations) next to beehiiv's own numbers, and list anything you could not move.What moves
What comes across, and what you rebuild.
- In beehiiv
Subscribers
In SendRavenThe email and status columns. Active imports as subscribed, inactive (unsubscribed) as unsubscribed.
- In beehiiv
Custom fields
In SendRavenIn the full export; each becomes a custom property.
- In beehiiv
Pending
In SendRavenLeft out. They never confirmed, and beehiiv does not email them either.
- In beehiiv
Suppression list
In SendRavenSubscribers → Suppression list. Imported as bounced, which suppresses everything.
- In beehiiv
Posts
In SendRavenTheir email HTML moves into SendRaven templates, from Export Posts or the posts API.
- In beehiiv
Automations
In SendRavenRebuilt as SendRaven automations; beehiiv has no export for them.
The file
What the export looks like, and how the import reads it.
beehiiv documents the basic export as email, status and tier, and the full export as those plus custom fields and statistics; it does not publish the exact headers. The mapping step matches the address, reads the status column (active is subscribed, inactive is unsubscribed), and turns each custom field into a property.
Pending subscribers have a status the import does not take as subscribed, so they are left out and counted, which is right: they never confirmed.
The part that matters
Bring the opt-outs.
Inactive subscribers unsubscribed, or were set inactive by you or by a re-engagement automation. They import from the status column as unsubscribed, suppressed for marketing.
Hard bounces and spam complaints are on beehiiv's suppression list (Subscribers → Suppression list), with a reason: bad address, not deliverable or manual. Import every address on it as bounced, which suppresses everything. A bounced address that reads Active in the export would otherwise be mailed again from your new domain, and a run of bounces in the first campaign is what trips the reputation gate.
Templates and sending
The copy and the code.
A post's email HTML comes from beehiiv's API: GET /v2/publications/{publication}/posts/{post}?expand=free_email_content, in content.free.email. Save the newsletters you reuse as SendRaven templates, replace beehiiv's merge tags with {{variables}}, and drop its footer and unsubscribe link; SendRaven adds its own to every marketing email.
What it costs
Estimate the bill by emails sent, not contacts.
- Emails a month
- 200,000
- SendRaven, Standard plan
- $85.00 a month
- For the 50,000 contacts
- $0
On a new sending domain, the first campaign to all 50,000 goes out over 8 days: the warm-up pauses it at each day's ceiling and resumes it at midnight UTC. The ceiling keeps rising for 14 days from the first send, then comes off. Published plan prices, before tax. Transactional mail, if you move it too, counts on the same meter; replies are never metered.
Then, in order
The steps every migration shares.
Verify your domain first
Add the domain under Domains and publish the DNS records it gives you. Use a subdomain you have not sent from before if you can (mail.yourdomain.com for transactional, news.yourdomain.com for campaigns), so the two reputations stay separate. Nothing sends until this is green, and it can take a while for DNS to settle, so start it before the export.
Import the subscribers
Contacts → Import a CSV. Pick or create the list, upload the export, and check the column mapping: address, names, tags, and which columns become custom properties. Re-running the same file is safe: existing contacts are updated, not duplicated.
Import the opt-outs
Then the unsubscribed, bounced and complained lists, with the matching status. Each one is flagged and suppressed before your first send: unsubscribes for marketing only, bounces and complaints for everything. An import never resubscribes someone who has opted out here.
Check the counts
The audience page shows how many were imported, updated and suppressed. Compare the suppressed count to what the old provider reported. If it is far off, the status column was read differently from how you meant. The mapping step shows what each value became.
Switch the API key
For transactional mail, point the code at POST /v1/emails with a SendRaven key. The request shape is from, to, subject, html or text, and an Idempotency-Key header. Keep the old key alive for a day in case something still points at it.
Send the first campaign to the engaged part of the list
A new domain has no history, and mailbox providers judge it on the first few thousand messages. Opens and clicks start from your first SendRaven send, so use the old provider's engagement: tag the recently engaged people on import, send the first campaign to a segment on that tag, then widen. A new sending domain also warms up, so a large first campaign spreads over several days on its own. The reputation gate refuses a campaign once the bounce or complaint rate is already high; it cannot refuse the one that gets you there.
Questions
Asked by people leaving beehiiv.
Why import the suppression list separately?
Because beehiiv records hard bounces there and not on the subscriber, the subscriber export alone can list a dead address as Active. Importing the suppression list as bounced is what stops the new domain mailing it.
Do premium subscribers come across?
The people do, as contacts, with their tier as a property if you want it. Paid subscriptions themselves are billed by beehiiv and do not move: SendRaven sends email and does not run a paywall.
Can an AI agent read my beehiiv publication directly?
Yes, through beehiiv's API with a key from its settings, or beehiiv's own MCP server. The migration prompt above uses either when the assistant can reach it, and otherwise walks you through the exports.

Start with the domain.
3,000 emails a month, inbound included, and no charge until you switch paid sending on. Verify the domain today and import the list once the DNS has settled. The other guides are on the migrate page.

