Buyer guide · Migration
Migrate the loyalty promise before moving the records.
Customers care about balances, rewards, and what happens next. Define those rules before importing data or replacing the counter workflow.
- First decision
- What customer value survives
- Built-in foreign import
- No general importer
- Safe route
- Staged launch or scoped migration
Short answer
Start with the operating rule.
Migrate the customer promise before moving data. Record what the old program owes, decide which balances and rewards survive, explain the cutover, and rehearse the new counter flow. Reward Loyalty exports its own ledgers, but it does not ship a general importer for another vendor’s customer files and balances. A full data move needs scoped custom work against the source format and current application model.
Who it fits
Use this model when the work matches.
A feature can exist in the product and still be the wrong starting point for a business. These conditions make the recommendation useful.
The old program has a clean export
Member identity, balances, reward state, consent, and history can be separated and explained.
The operator can define equivalence
A point, stamp, tier, voucher, or pass in the old system has a clear treatment in the new program.
The cutover can be rehearsed
Staff can test lookup, earning, redemption, correction, and customer explanations before the old workflow closes.
Setup
Configure the decisions in this order.
The order keeps presentation work from hiding an unresolved commercial or operational rule.
-
1
Inventory the old promise
List member identifiers, balances, incomplete stamp cards, unredeemed rewards, tiers, referrals, passes, expiry, and marketing consent separately.
-
2
Choose what survives
Preserve value where the customer could reasonably expect it. Document conversions, expiry, exclusions, and the treatment of dormant accounts.
-
3
Select the migration shape
Use a fresh launch with a controlled welcome offer when records cannot map safely. Commission a source-level migration when exact balances and history must move.
-
4
Build a staging rehearsal
Use representative records, check totals, test duplicate identities, and keep the old system read-only during validation. Never use production data in demo mode.
-
5
Train the counter before cutover
Give staff one lookup path, one explanation for old balances, and one escalation route for a disputed record.
-
6
Close and reconcile
Take the final source export, run the agreed process once, compare control totals, publish the start time, and retain a secure audit copy under the operator’s retention policy.
Operating workflow
What happens after launch.
The workflow matters because every extra counter decision raises training cost and increases inconsistent treatment.
Customer sees the change before the visit
State the cutover date, what carries over, what action the customer needs to take, and where to raise a discrepancy.
Customer joins or verifies identity
Use the agreed email or member identity. Do not treat marketing consent in an old export as permission without checking its scope and provenance.
Staff checks the opening state
The counter sees the starting balance or welcome treatment and follows the new earning and redemption flow.
Operator handles exceptions
Use a documented correction policy and preserve the source record behind each approved adjustment.
Product and operating limits
Know the boundary before launch.
A clear limit protects the buyer from choosing the feature for work it does not perform.
- Reward Loyalty has export tools for its own points, stamp, voucher, and pass ledgers. That does not create a general import path for another vendor’s schema.
- The achievements history import recognizes qualifying activity already present inside Reward Loyalty. It is not a customer or balance migration tool.
- A source-level migration can create obligations around consent, retention, reconciliation, security, and customer disputes. Scope and test it as a data project.
- When a source export lacks reliable identifiers or history, a smaller welcome conversion can be safer than pretending the records map exactly.
Implementation guides
Continue in the current product documentation.
Each link opens the setup or operating workflow behind the recommendation above.