Migrate from Loops

Add your sending domain under Settings → Domains in Sendwave. Sendwave shows three CNAME records named <token>._domainkey, pointing to <token>.dkim.amazonses.com. Add them at your DNS provider and Sendwave marks the domain verified once they resolve.

You do not need to remove anything first. Loops puts its SPF and MX records on an envelope. subdomain of your sending domain. Sendwave’s DKIM selectors are different, so both sets of records can live side by side and Loops keeps working while you move.

Sendwave also offers an optional custom MAIL FROM domain: an MX and an SPF TXT record on a plunk. subdomain. It aligns bounces with your domain and is worth adding, but sending works without it.

In Loops, open your audience, use the ••• menu next to the filter box and choose Download. The CSV has one column per contact property, including email and subscribed, which Sendwave reads as they are. No renaming is needed for those two.

Custom properties come along as custom fields, lowercased: firstName becomes firstname and userId becomes userid. Templates and segments then refer to the lowercase names.

Loops can export an email’s content only as LMX, its own markup, through GET /api/v1/email-messages/{id}. There is no HTML export, so recreate each design in Sendwave’s editor and change the tags:

In Loops, a transactional email’s subject, sender and reply-to live in the email itself. Sendwave templates hold them too, as defaults the send request can override.

Transactional sends map almost field for field:

await fetch('https://app.loops.so/api/v1/transactional', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    Authorization: `Bearer ${process.env.LOOPS_API_KEY}`,
  },
  body: JSON.stringify({
    transactionalId: 'clfq6dinn000yl70fgwwyp82l',
    email: '[email protected]',
    dataVariables: {orderId: '3980'},
  }),
});

const response = await fetch('https://api.usesendwave.com/v1/send', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    Authorization: `Bearer ${process.env.PLUNK_SECRET_KEY}`,
  },
  body: JSON.stringify({
    template: 'YOUR_PLUNK_TEMPLATE_ID',
    to: '[email protected]',
    data: {orderId: '3980'},
  }),
});

if (!response.ok) {
  throw new Error(`Sendwave returned ${response.status}`);
}

Events move the same way:

Simple values in data are saved on the contact. Wrap a value as {value: …, persistent: false} to make it available to the workflow without storing it. The track endpoint accepts your public key, so it can run in the browser.

If you used Loops’ SMTP server, note that it expects a JSON body naming a transactional email. Sendwave’s SMTP server takes ordinary email instead: host smtp.useplunk.com, port 587, username plunk and your secret key as the password.

Loops returns a workflow’s structure from GET /api/v1/workflows/{id}, one node at a time, so it can serve as a checklist, but there is no import. Rebuild each one in Sendwave: the trigger becomes an event, segment entry or schedule trigger, and the emails, delays and branches become steps.

Sendwave has no global webhook setting. Instead, you create a workflow that starts on an event and add a Webhook step that posts to your URL. One workflow per event you care about, each with its own URL and headers if you want them.

Sendwave’s email.open and email.click fire on the first open and first click of each email, not on every one. The payloads differ, so the code that reads them needs updating. Sendwave’s payload for each event is listed in the webhooks guide.

1. 1

   Send to yourself first

   Send a few real templates from Sendwave to your own inboxes and check rendering, links and variables. Gmail’s “Show original” should report DKIM pass for your domain.
2. 2

   Move one kind of email at a time

   Switch one flow, such as password resets, and watch delivery in Sendwave for a day before moving the rest. Loops stays available as a fallback the whole time.
3. 3

   Remove the old records last

   Once nothing sends through Loops any more, wait a few days for any retries to settle, then remove its DNS records and cancel the plan.