For the complete site index, see llms.txt. Docs index: llms-docs.txt. Marketing corpus: llms-full.txt. Docs corpus: llms-full-docs.txt. Prefer markdown URLs where available (append .md).. Product skill: skill.md. Pricing: pricing.md. Docs MCP: /docs/mcp.

Reloop vs Sweego

Migrate from Sweego to Reloop.

7 steps. Keep Sweego running until the last one, so nothing breaks while you switch.

  1. 1

    Add your domain in Reloop

    Add your domain in Reloop and publish the DKIM record (reloop._domainkey). Merge include:reloop.sh into your existing SPF record rather than adding a second one.

  2. 2

    Swap the client

    Replace calls to /send with reloop.mail.send, and map recipients/from/subject/message-html/message-txt to to/from/subject/html/text. If you use SMTP, change the host and credentials.

  3. 3

    Move templates

    Export the HTML and change placeholders to triple braces: {{ name }} becomes {{{name}}}.

  4. 4

    Carry over suppressions

    Export hard bounces and unsubscribes from your Sweego logs or webhook history and import them, so you never mail someone who opted out.

  5. 5

    Point webhooks

    Point webhooks at a new handler. Reloop events are named email.delivered, email.bounced, email.complained and so on.

  6. 6

    Move inbound

    Point the inbound subdomain's MX at Reloop and read replies from the mailbox instead of a webhook.

  7. 7

    Ramp traffic

    Ramp traffic from 10% to 100% over a week or two, then remove Sweego's DNS records. Keep your Sweego account if you still send SMS.

Our SendGrid migration guide walks through the same steps in more detail.

Reloop