PulsePigeonemail infrastructure

Step 1

Export source evidence.

  • domains
  • API keys inventory
  • event webhook consumers

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

Importer first
CheckRecreate domains with DKIM rotation.Confirm in sandbox before production cutover.
CheckUse idempotency keys during dual-write testing.Confirm in sandbox before production cutover.