PulsePigeonemail infrastructure

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.

Run import preflightReview comparisons

Step 1

Export source evidence.

  • audiences
  • suppression exports
  • template content

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

Importer first
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.