Notes on identity, membership, and platform change.
Practical notes for merchants planning a migration — what can be checked, what cannot be assumed, and what to ask before committing.
An OpenID is not a customer ID
The member export looks complete: every row has an ID, a points balance, and a join date. Then the new platform tries to use it. Why the identifier in column A is not the customer, and how to test the gap before you commit.
Read the article →The member export looks fine. Check these five things.
Every migration starts with a file that opens. Then the totals do not add up, three phone formats appear in one column, and nobody can say which rows are the same person. Five checks to run before the import button.
Read the article →Points, tiers, and stored value are three different migrations
They sit in one export and often one spreadsheet. But points, tiers, coupons, and stored value do not share a conversion rule, an owner, or a failure mode. Treat them as separate workstreams before you promise continuity.
Read the article →There is no account migration: moving members to a new entity's mini program
The old mini program cannot be transferred, redirected, or renamed into the new one. Members have to be re-linked, not imported. Here is the order of work that keeps a cross-entity migration honest.
Read the article →