Step 1
Export source evidence.
- segments
- suppression profile exports
- journey inventory
Migration guide
Migrate from Customer.io to PulsePigeon
Use this guide as a cutover checklist. Verify current Customer.io export formats before importing, because vendor exports can change.
Last verified: August 8, 2026. Review current Customer.io 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
Customer.io migration checks
CheckConvert profile traits into contact attributes.Confirm in sandbox before production cutover.
CheckRebuild journeys after consent topics are reviewed.Confirm in sandbox before production cutover.
API mapping
Customer.io exports, mapped to PulsePigeon endpoints
ExportSuppression profile exportPOST /v1/suppressions/import accepts email, reason, suppressed_at
ExportSegment/journey inventoryNo journey importer yet; workflows must be rebuilt in the visual workflow builder
Preflight endpoints validate before anything is stored. Confirm the Customer.ioexport format against its current docs before mapping fields.