Skip to the documentation
Knowledge base

Move from Resend

Bring your suppressions, audiences, contacts, templates and webhooks across with one key, with a checklist for your domains and API keys.

Details

  • Settings → Import reads a Resend account with a full-access key. Every segment becomes an audience, every subscribed contact arrives with its name, and the suppression list keeps each address’s reason: bounce, complaint or manual. Contacts who had unsubscribed are left out and counted rather than silently added to a list you might mail later.
  • Templates arrive as HTML templates. Each {{{VAR}}} becomes a declared variable, a fallback becomes its default, a variable used in a link becomes a URL and one used as an image source becomes an image, and a published template arrives published. Each webhook endpoint is registered with the same URL and the nearest matching events, switched off, because deliveries here are signed differently; update the check in your endpoint, then switch it on.
  • The key is held encrypted only while the import runs and is erased when it finishes, fails or is cancelled. The import reads gently, so your live sending keeps its own rate limit, and running it twice duplicates nothing, because every imported item is remembered and skipped the second time.
  • Domains and API keys come back as a checklist rather than moving, because a signing key or a token cannot leave the service that made it. Each domain shows whether it is added here yet and which records at Resend can go once mail sends from here; each key is listed by name so you can create its replacement. Broadcasts, topics and contact properties are not brought across.
  • Your sending code does not change. Set RESEND_BASE_URL to https://api.openemail.uk/compat/resend and RESEND_API_KEY to an OpenEmail key, and the Resend SDK sends through OpenEmail: send, batch, get, list, reschedule and cancel answer in Resend’s own shapes and error names. Attachments given as a buffer or a URL come across, tags and scheduled sends too, and an idempotency key of any form is honoured. One reply-to address per message, and an inline image referenced by content id arrives as an ordinary attachment.