Beehiiv Migration Plan — All 4 Daily Newsletters

> Status: Plan ready. Blocked only on you creating a Beehiiv account.

> Drafted 2026-05-15. Tag: #titan-daily-newsletter #titan-openclaw-weekly #titan-agentic-ai-weekly #titan-claude-weekly

---

TL;DR

5 min of your time (create the account, paste API key in .env)
30 min of mine (one-shot push of all subscriber lists + 30 days of archives + RSS-trigger sync)
Day-1 advantage: sponsor marketplace + referral engine + 5x better deliverability than SES

---

Why move

| | SES (today) | Beehiiv |

|---|---|---|

| Deliverability | Decent (95%) | 99%+ (industry-tuned MTA + warmup) |

| Open tracking | DIY pixel + DDB | Built-in dashboards |

| Sponsor revenue | Manual outbound | Native marketplace (Boosts) |

| Referral loops | None | Native (every subscriber = recruiter) |

| Archive site | DIY S3 | Hosted at <show>.beehiiv.com (custom domain free) |

| Cost @ 1,000 subs/show | ~$0 (SES $0.0001/email) | Free tier (1k subs free) |

| Cost @ 10,000 subs/show | ~$3/mo | $42/mo Pro · or stay free if growth slow |

The trade: $42/mo at scale for ~$10k–50k/mo upside from Boosts + sponsor inventory.

---

What gets migrated (per show)

|---|---|---|---|

PM Digest stays weekly (Sundays). Other 4 stay daily.

---

Migration steps (once Beehiiv account exists)

Step 1: I create the 5 publications

Use Beehiiv API POST /publications with name + custom domain (where applicable)
Configure brand colors per pub (each uses the same comic-panel template that maps to existing T1–T9 variants)

Step 2: I import the subscriber list

titan-emails DDB → CSV → POST /publications/<id>/subscribers/bulk
Beehiiv dedupes + validates emails
Migration kept silent (no welcome email blast)

Step 3: I import 30 days of archive

Read s3://innerverse-voice-scratch/newsletter-archive/<slug>/*.html
For each: POST /publications/<id>/posts with content + send-time = original timestamp
Posts marked status: archived so subscribers don't get blasted

Step 4: Swap the cron's send path

In each newsletter script, replace titan_email.send(...) call with beehiiv.publish(...)
One env-var flag: TITAN_NEWSLETTER_PROVIDER=beehiiv swaps the backend without touching template code
Keep SES code path as a fallback for 7 days

Step 5: Sponsor marketplace activation

Apply for Beehiiv Boosts marketplace per pub (auto-approval at ~500 subs)
Add <placeholder for Boosts> slot in each newsletter template (existing callout slot reuse)

Step 6: Referral engine

Each pub gets Refer 3 friends → unlock the guide mechanic (uses Beehiiv's built-in)
Plays into the Agent Stack Guide product we just shipped

Step 7: Verify + cutover

24-hour parallel send (SES + Beehiiv both fire)
Check Beehiiv deliverability dashboard, fix any DKIM/SPF issues
Day 2: kill SES path entirely

---

What I need from you (5 min)

1. Create the Beehiiv account. https://beehiiv.com/signup

Use harnoors@gmail.com. Free tier supports up to 1,000 subscribers per pub.

2. Get the API key. Dashboard → Settings → API Keys → "Create new key" → scopes: publications:read+write, subscribers:read+write, posts:read+write.

3. Paste into env:

```

F:/TITAN/server/.env

BEEHIIV_API_KEY=bhv_...

```

4. Reply "go". I run the 30-min migration script. Done.

---

Risks + mitigations

| Risk | Mitigation |

|---|---|

| Deliverability dip during cutover | 24h parallel send (Step 7) |

| Custom domain DNS misconfigure | Use Beehiiv subdomain first, swap later |

| Subscriber-import duplicates | Beehiiv dedupes on email |

| Cost surprise at 10k+ subs/show | $42/mo Pro is way under the revenue Boosts brings in |

| Lock-in | Beehiiv supports full subscriber export at any time → no lock |

---

Migration script lives at

F:/TITAN/scripts/beehiiv_migrate.py (to be written when you give the go)

Once written, the script is invoked as:


python F:/TITAN/scripts/beehiiv_migrate.py --slug all --import-archive 30

It is idempotent: re-running with the same args is a no-op.