Use the checklist during the parallel run. An item is complete when the answer is yes and the evidence is attached: a reconciliation report, a replay log, a signed feed test, a finance sign-off. Items marked gate block cutover.

1. Balances and sub-balances

  • Gate. Does every member's total balance in the new platform match the legacy platform, across the full member base and not a sample?
  • Are sub-balances (points, credits, vouchers, comp dollars, status credits) carried as separate purses rather than netted into one total?
  • Does each accrual lot keep its source rule, currency, brand, partner and expiry date?
  • Are escrowed or pending accruals carried with their release conditions?

2. Points and currencies

  • Do qualifying and non-qualifying points remain distinguishable after migration?
  • Is the burn order (FIFO or tagged source) configured to match legacy behaviour, or has a change been approved by finance?
  • Are currency conversion rules for multi-currency programs reproduced and tested on real transactions?

3. Tiers and status

  • Gate. Does every member hold the same tier in both platforms?
  • Is qualification progress toward the next tier carried, not reset?
  • Are tier expiry and re-qualification dates preserved?
  • Are status-match, soft-landing and grace-period rules reproduced?

4. Expiry

  • Gate. Do points expire on the original dates, lot by lot, with no mass expiry and no silent extension?
  • Have expiry warnings and notifications been tested against the migrated schedule?
  • Has finance confirmed the breakage recognition timing is unchanged, or approved the change?

5. Historical transactions

  • Are historical transactions loaded with original dates, sources, locations and amounts?
  • Are reversals, cancellations and adjustments loaded and linked to the activities they unwind?
  • Can member care see the same history in the new platform that the legacy call centre could?
  • Has replay of historical events against the new rules produced the same outcomes?

6. Partner balances and settlement

  • Gate. Are partner wallets and open settlements carried, with the same amounts owed to and by each partner?
  • Are partner funding rules, rates and date-relative billing parameters reproduced?
  • Has each partner's feed (inbound accrual, outbound billing) been tested end to end?

7. Promotions and rules

  • Gate. Has a rule audit compared what the legacy program actually runs with what the documented terms say, and has each difference been decided?
  • Are in-flight promotions carried with their remaining budgets, count limits and cool-off states?
  • Are member-specific promotion states (streak progress, challenge completion, mission progress) carried?
  • Have discount arbitration outcomes been compared on real mixed baskets?

8. Integrations

  • Gate. Is every inbound channel (POS, pump, app, web, kiosk, partner API, batch) connected and tested against production-shaped traffic?
  • Do response times at the register and pump meet the timeout window under load?
  • Is degraded-mode behaviour (what the lane does when the platform cannot answer) tested?
  • Are authentication, secrets and network rules in place for every integration in the production environment?

9. Downstream feeds

  • Gate. Is every consumer of loyalty data (warehouse, CDP, email and messaging, general ledger, partner reporting) receiving events or files from the new platform?
  • Have downstream teams confirmed schemas and cadences match, or that changes are absorbed?
  • Is the event stream (Kafka, Kinesis, EventHub or equivalent) live with the same event types?

10. Member-facing continuity

  • Do members see the same balance, tier and history in the app and on receipts on day one?
  • Are card numbers, membership numbers and identifiers unchanged?
  • Is member care trained and equipped to answer questions on the new platform, with the audit trail visible?
  • Is the communication plan ready if members must be told anything at all?

11. Financial reconciliation

  • Gate. Can finance reproduce the liability rollforward (prior + earned − redeemed − expired) from the new platform's transaction-level exports for the parallel-run period?
  • Does each brand's liability tie out separately in a multi-brand program?
  • Has finance signed off the cutover date relative to period close?

Cutover governance

  • Are named owners assigned for data, rules, integrations, finance and member experience?
  • Is the go/no-go written, with success conditions agreed before the parallel run started?
  • Is rollback armed, owned, and tested, and is the legacy platform kept live for the agreed period after the switch?
Loyalty platform migrationthe complete enterprise guideSafe Migrationthe SafeSwitch™ methodLoyalty ledger and audit trail