Step 1
Export source evidence.
- domains
- API keys inventory
- event webhook consumers
Migration guide
Migrate from Resend to PulsePigeon
Use this guide as a cutover checklist. Verify current Resend export formats before importing, because vendor exports can change.
Last verified: August 8, 2026. Review current Resend documentation
Step 2
Import into review.
Run the PulsePigeon import preflight before production traffic moves. Do not send to imported contacts until suppressions and consent topics are reviewed.
Step 3
Dual-write before cutover.
Keep critical transactional mail on the proven route while PulsePigeon gathers delivery evidence and SLO history.
Provider notes
Resend migration checks
CheckRecreate domains with DKIM rotation.Confirm in sandbox before production cutover.
CheckUse idempotency keys during dual-write testing.Confirm in sandbox before production cutover.
API mapping
Resend exports, mapped to PulsePigeon endpoints
ExportDomain and DKIM record exportDomains must be re-verified through PulsePigeon's own domain authentication flow; DKIM keys are not portable between providers
ExportWebhook event consumer listSigned status webhooks must be re-registered against PulsePigeon's webhook endpoints
Preflight endpoints validate before anything is stored. Confirm the Resendexport format against its current docs before mapping fields.