Step 1
Export source evidence.
- suppression lists
- dynamic templates
- event webhook samples
Migration guide
Migrate from SendGrid to PulsePigeon
Use this guide as a cutover checklist. Verify current SendGrid export formats before importing, because vendor exports can change.
Last verified: August 8, 2026. Review current SendGrid 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
SendGrid migration checks
CheckMap categories to PulsePigeon preference topics.Confirm in sandbox before production cutover.
CheckReview any shared-IP reputation assumptions.Confirm in sandbox before production cutover.
API mapping
SendGrid exports, mapped to PulsePigeon endpoints
ExportContact export CSV (email, custom fields)POST /v1/imports/contacts/preflight validates email, name, source, status, and opt-in timestamp headers before anything is stored
ExportSuppression group export (bounces, blocks, spam reports, unsubscribes)POST /v1/suppressions/import accepts email, reason, suppressed_at
Preflight endpoints validate before anything is stored. Confirm the SendGridexport format against its current docs before mapping fields.