Migrate
Your email code,
rewritten for Nextmail.
Paste the code that sends your mail today. It comes back in the same language on the Nextmail SDK, with every change listed and every call checked against the reference.
Converter
Paste it in,
read what changed.
Pick where the code comes from and its language. Recognised keys are removed in your browser, and nothing you paste is kept.
A guide for
every platform you leave.
What maps to what when you move your code, and every step when you move a mailbox.
- Resend
Migration guide
Keep your code on the compatible API, or convert it.
- SendGrid
Migration guide
Personalizations, dynamic templates and event webhooks.
- Postmark
Migration guide
Server tokens, message streams and templates.
- Mailgun
Migration guide
Domains, o: options and v: variables.
- Amazon SES
Migration guide
SESv2 calls, configuration sets and SNS events.
- Gmail
Migration guide
Mail, labels and threads, from Google Takeout.
FastmailMigration guide
One export per folder, threads intact.
- Proton Mail
Migration guide
Proton's own export, with folders and labels.
- HEY
Migration guide
Every message and attachment, from one export.
Four steps
from paste to production.
- 01
Paste one file
The code that sends your mail, in Node.js, Python, Ruby, PHP or cURL. Recognised keys are removed in your browser first.
- 02
Read the rewrite
The same program on Nextmail, with each change, each manual step and each option left out listed beside it.
- 03
Check every call
Every Nextmail call is matched against the SDK reference, and anything left of the old provider is flagged.
- 04
Ship it
Add your domain, create an API key, set NEXTMAIL_API_KEY and deploy.
Questions about
moving your code.
Converted?
Create the key it reads.
A workspace takes a minute. Add your domain, create an API key and set NEXTMAIL_API_KEY.