Migration · From SendGrid

Migrate in an afternoon. Keep every line of code.

Inbox OSS speaks the SendGrid v3 API verbatim. Same /mail/send body. Same SDK shapes. Same webhook payloads.

Six steps

What migration actually looks like

01
Sign up + add your sending domain
Create your account, add the same sending domains you use in SendGrid. We generate a fresh DKIM keypair per domain.
02
Add three CNAMEs
mail. → mail.inbox.onesourcesoft.com, track. → track.mail.inbox.onesourcesoft.com, and the DKIM selector CNAME. Existing SendGrid DNS can stay live during cutover.
03
Verify in the dashboard
Verification polls DNS every 30 seconds. Most propagate within 5 minutes.
04
Swap two values in code
Hostname: api.sendgrid.com → api.inbox.onesourcesoft.com. API key: SG.xxx → Inbox key. That's it.
05
Mirror suppressions (optional)
Export your SendGrid suppression list as CSV and import via /api/v1/suppressions/bulk. We support the SendGrid format verbatim.
06
Cut over traffic gradually
Run both for a week. Compare deliverability scorecards side-by-side in our dashboard.

Compatibility matrix

POST /api/v1/mail/send — full v3 body

Personalizations with substitutions

Categories, custom_args, send_at

Tracking settings (open/click/subscription)

Mail settings (footer, sandbox, bypass)

Attachments (base64 + inline content_id)

Webhook events (29 of 29 mirrored)

IP pools naming convention

Subusers (Enterprise plan)

Suppression lists CSV format

Marketing Campaigns Designs API

Inbound Parse webhook payload

Our team will mirror your DNS, validate your templates, and stay on Slack with you through cutover week.