Decisions · Technology
What breaks in a loyalty migration
What breaks in a loyalty migration is the member's right to redeem at the old value. Recommend freezing new earn and settling all outstanding points as cash, vouchers, or a ringfenced liability before the new platform goes live, rather than copying balances and hoping the new rules honour them.
The decision
A loyalty migration is not a data move. It is a decision about whether the old programme's promise survives the new platform. Points are a liability created at earn, not a database field that can be mapped. If you move the balance without moving the redemption right, you have broken the contract with the member. The mechanism is liability novation: the new operator either takes on the old obligation at the old value, or the old operator must close it out before migration. The only safe version is to treat migration day as the end of the old programme: freeze earning, give members a clear window to redeem at existing rates, settle any remainder as cash or voucher, and start the new programme with a zero liability.
What it costs you
This path costs real money because you are paying down a liability you might otherwise have kept on the books. The cost appears as cash outflow, reduced margin on redemptions, and engineering time to run two systems through a cutover. Illustrative calculation: suppose a programme has 10 million points outstanding and each point is worth one cent at redemption. The maximum liability is 100,000 dollars. If you follow the recommended path and settle every point at one cent, you pay 100,000 dollars exactly. If migration instead devalues points to half a cent and members later redeem at that rate, the apparent saving is 50,000 dollars, because 10 million times half a cent equals 50,000 dollars. A member with 50,000 points sees a 500 dollar claim reduced to 250 dollars. That member may leave, and the lost future margin can exceed the saving many times over, but the immediate cash cost of doing the right thing is the full 100,000 dollars.
How to decide
Apply this test to your own programme before any data migration. Take a member who has 1,000 points at 11:59 on the night before migration. Can that member, at 12:01 after migration, redeem those 1,000 points for exactly the same value as before, without contacting support, without accepting new terms, and without a new conversion ratio? If the answer is not an unconditional yes for every outstanding point, then do not migrate balances. Freeze earning, communicate a redemption deadline, settle remaining points at the old value, and launch the new programme with no carried liability. If the answer is yes, you still need that promise written into the migration contract, not just assumed by the project team.
What would change our mind
We would change our mind if the new platform operator signs a deed of novation that makes it directly liable to every member for every point at the old redemption value, with identical redemption terms and no new consent. In that case, migrating balances is a genuine transfer of the obligation and nothing breaks. Without that deed, migration is a unilateral devaluation hidden inside a technical project, and the recommendation stands.