Step 1
Export source evidence.
- audiences
- suppression exports
- template content
Migration guide
Migrate from Loops to PulsePigeon
Use this guide as a cutover checklist. Verify current Loops export formats before importing, because vendor exports can change.
Last verified: August 8, 2026. Review current Loops 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
Loops migration checks
CheckSeparate marketing consent from product updates.Confirm in sandbox before production cutover.
CheckRun a purchased-list preflight before first campaign.Confirm in sandbox before production cutover.
API mapping
Loops exports, mapped to PulsePigeon endpoints
ExportAudience CSV exportPOST /v1/imports/contacts/preflight blocks list-broker headers and high trap density before any contact is stored
ExportSuppression exportPOST /v1/suppressions/import accepts email, reason, suppressed_at
Preflight endpoints validate before anything is stored. Confirm the Loopsexport format against its current docs before mapping fields.