PulsePigeonemail infrastructure

Migration guide

Migrate from Mailgun to PulsePigeon

Use this guide as a cutover checklist. Verify current Mailgun export formats before importing, because vendor exports can change.

Last verified: August 8, 2026. Review current Mailgun documentation

Run import preflightReview comparisons

Step 1

Export source evidence.

  • suppressions
  • routes
  • stored templates

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

Mailgun migration checks

Importer first
CheckPreserve bounce and complaint suppressions first.Confirm in sandbox before production cutover.
CheckMove transactional mail before campaigns.Confirm in sandbox before production cutover.

API mapping

Mailgun exports, mapped to PulsePigeon endpoints

Dry run first
ExportSuppression export (bounces, complaints, unsubscribes)POST /v1/suppressions/import accepts email, reason, suppressed_at
ExportMailing list member CSVPOST /v1/imports/contacts/preflight is a dry run only — contacts are not stored until a separate import step

Preflight endpoints validate before anything is stored. Confirm the Mailgunexport format against its current docs before mapping fields.