• Create a list of donations that can't be migrated (legacy CC provider or missing legacy data) and ask PM what to do about them. Options are
  • Delete
  • Keep with fake payment entry (maybe reuse payment ID)
  • Keep and hope they are never loaded with payment information (which would explode)

Implementation notes:

Suggested approach: create a class that takes donation data (including legacy blob), determines the legacy mapper according to payment type and booking status and tries to create a new payment instance / validates the transaction data according to the rules in the payment domain.

Create a small script that reads the donation table and calls migrator for each row, returning a list/CSV of "bad" donations so we can determine what to do with them

This is a one-off script, no need for code quality