Step 1
Export source evidence.
- server streams
- templates
- message streams
Migration guide
Migrate from Postmark to PulsePigeon
Use this guide as a cutover checklist. Verify current Postmark export formats before importing, because vendor exports can change.
Last verified: August 8, 2026. Review current Postmark 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
Postmark migration checks
CheckKeep critical streams isolated.Confirm in sandbox before production cutover.
CheckValidate template variables in sandbox before cutover.Confirm in sandbox before production cutover.
API mapping
Postmark exports, mapped to PulsePigeon endpoints
ExportSuppressed recipient export, per message streamPOST /v1/suppressions/import is tenant isolated, not stream isolated — merge streams deliberately before import
ExportTemplate content exportNo template importer yet; recreate templates through the API with PulsePigeon's variable validation
Preflight endpoints validate before anything is stored. Confirm the Postmarkexport format against its current docs before mapping fields.