Moving from SendGrid to SendRaven.

This is the migration an agent in your editor is best at, because half of it is code. Connect SendRaven's MCP server to Claude Code, Cursor or another client that can read your repository and the exported files, and ask for the whole thing.

Over MCP the agent adds and verifies the sending domain (add_sending_domain, verify_sending_domain), loads the suppression files (suppress_many, up to 10,000 addresses per call), imports Marketing Campaigns contacts (import_contacts, up to 5,000 per call) and sends a test (send_email). In the repository it replaces the SendGrid send calls with POST /v1/emails, which you review like any other change.

The SendGrid exports are in ./sendgrid-export.

1. Suppress everything in bounces.csv, spam_reports.csv and
   invalid_emails.csv with scope "all", and everything in
   global_unsubscribes.csv with scope "marketing" and reason
   "unsubscribe". Report the counts per file.
2. Import contacts.csv into the audience "Customers" with
   names and custom fields.
3. In this repository, replace every @sendgrid/mail send with
   a POST to https://api.sendraven.ai/v1/emails using
   SENDRAVEN_API_KEY and an Idempotency-Key header. Keep the
   SendGrid path behind an EMAIL_PROVIDER environment variable.
4. Send one test email from mail.example.com to me.

• Load the suppressions before anything sends. Re-running the same file is safe: each address is written once, however many times it is loaded.
• Group unsubscribes are topic preferences, not suppressions. Load them with POST /v1/topics/{key}/import (one call per group); the MCP server only sets one person's preferences at a time.
• The audience is created in the dashboard or with POST /v1/audiences; the MCP server has no tool for it.
• Everything passed to a tool goes through the model's context. For contact files beyond a few thousand rows, ask the agent to write a script against POST /v1/audiences/{id}/contacts in batches of 5,000, or use the dashboard's CSV import.

Connect the SendRaven MCP server to your client, then paste the prompt with your own audience, segment and domain names.

The contact export: EMAIL, FIRST_NAME, LAST_NAME, ALTERNATE_EMAILS, ADDRESS_LINE_1, ADDRESS_LINE_2, CITY, STATE_PROVINCE_REGION, POSTAL_CODE, COUNTRY, PHONE_NUMBER, WHATSAPP, LINE, FACEBOOK, UNIQUE_NAME, CONTACT_ID, CREATED_AT, UPDATED_AT, then one column per custom field. Alternate emails are not the address column, and the import knows.

A suppression export is a list of addresses with a created time and, for bounces, the reason. There is no status column because the file is the status: choose it at import.

Five files, three statuses. Global unsubscribes are "unsubscribed": marketing suppressed, transactional untouched. Bounces and invalid emails are "bounced", spam reports are "reported spam"; both suppress everything. Bring all of them before the first campaign. SendGrid learned that list at the cost of its reputation; you can have it for the cost of an upload.

Group unsubscribes are per group, so they are topic preferences rather than suppressions: create a topic for each group and load the members with subscribed false. Someone who left the promotions group still gets the product update, which is what they asked for.

Dynamic templates are Handlebars over HTML. Copy the HTML out of the editor into a SendRaven template. Plain {{substitutions}} carry over as they are; conditionals and loops do not, so flatten those in the code that fills the variables. Remove the unsubscribe tags and footer; SendRaven adds the link and the List-Unsubscribe headers to marketing sends.

The v3 mail send call, with personalizations and content arrays, becomes POST /v1/emails with from, to, subject and html or text, or a template slug and variables. One recipient per call for transactional; POST /v1/emails/batch for a small fan-out; a broadcast for a campaign.

# Group unsubscribes → one topic per group, members opted out
curl -X POST https://api.sendraven.ai/v1/topics/promotions/import \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "emails": ["ana@example.com", "bo@example.com"], "subscribed": false }'

• Keep the SendGrid account and its API key active until the switch is done. Nothing in SendRaven touches them, so going back is changing EMAIL_PROVIDER.
• Move transactional mail one kind at a time, the lowest-stakes first: a notification before a receipt, a receipt before a password reset. Watch each one's bounces and delivery in the email log for a few days before moving the next.
• Move campaigns by splitting the list, never by sending one campaign from both. The engaged part goes from SendRaven while the new domain warms up; the rest stays on SendGrid until the warm-up can carry it.
• While both send, bounces and opt-outs have to travel both ways. Re-export SendGrid's suppression lists and load them again before each SendRaven campaign, and add SendRaven's new ones (the Suppressions page, or GET /v1/suppressions) to SendGrid before each of its sends.