Short answer
Before switching loyalty programs, agree on which customer records, points, and unused rewards can move. Ask the new provider to show how it matches customers and checks a test import. Get the changeover, costs, and support in writing before ending the old service. A successful points import does not establish that the whole program has moved.
Start with the problem you need the move to solve
A loyalty program migration is a move from one rewards system to another. It may involve customer records, balances, reward rules, and the way staff run the program.
Write down why you are considering it. You might need simpler staff work, better support, a shared program across locations, or a website and customer app handled together. A new logo on the same process may not solve that problem.
Check whether your current provider can fix the gap first. If a move still makes sense, compare the new program and the work of getting there. Our customer loyalty software comparison can help you make a shortlist.
Make a list of what customers already have
Ask your current provider what you can export, in which file format, and at what cost. An export is a copy you can take out of a system. An import loads records into another one.
Keep the original export unchanged in a secure place. Work from a copy and give access only to the people handling the move. Confirm who is allowed to export, share, and import the records.
| Record | What to confirm | What could need separate work |
|---|---|---|
| Customer identity | How an old record matches the right account in the new system. | Missing details, duplicate accounts, or changed email addresses. |
| Current points | The balance and the date it was exported. | Pending, expired, negative, or adjusted points. |
| Unused rewards | Which coupons, stamps, credits, or earned perks are still usable. | Recreating an offer or handling a reward outside the new system. |
| Member levels | A customer’s current level and progress toward the next one. | Different entry rules or a separate provider-assisted import. |
| Message preferences | Which choices and opt-out records are available. | Settings that do not carry over with a points file. |
| Activity history | Which past purchases and reward actions can be read or moved. | A separate archive when the new tool cannot import history. |
For each row, ask the new provider to mark it as imported, recreated, kept separately, or unavailable. Do not treat a customer list and a points balance as the whole program.
Read the provider’s import limits before choosing
Official documentation shows why a general promise to move your data needs detail. These examples were checked on November 17, 2026. They describe specific products, not every loyalty tool or every Rehost project.
- LoyaltyLion: its migration guide distinguishes points from tier data and says it cannot import order history. It also says customers must already exist in the store for the import to match them.
- Yotpo: its points-import guide uses customer email addresses and point values. It directs businesses to support for new customers, extra attributes, and some tier setups. It notes that an adjustment affects both current points and total points earned.
- Smile: its switching page describes importing points through a CSV file, a spreadsheet-style file. The level of migration help depends on the plan.
Ask for confirmation for your exact old and new plans. A tool that can import points may still need rewards, rules, customer-facing pages, and staff access set up separately.
Keep the value and the rules clear
Two programs can use the word points and mean different things. Compare what a customer can earn and use, not just the number shown on screen.
Agree how to handle current balances, unused rewards, expiration dates, and progress toward a member level. If the rules will change, decide how existing customers are treated and what you will tell them.
A gift card or prepaid credit may use a different system and rules from loyalty points. List it separately and confirm the right handling rather than adding it to a points file by default.
Keep message preferences separate too. Ask which recorded choices can move and which settings need to be checked in the new tool before messages are sent.
Ask for a test before moving live balances
Use the provider’s supported test process. Start with test records or a small approved sample, handled securely. Ask whether an import replaces a balance or adds to it, and what happens if the same file is run again.
Example only: a test customer has 80 points and one unused reward. After the trial move, the correct account should show the agreed balance and a clear way to use that reward. The provider should also explain where the old activity history can be found.
Include cases that are easy to miss: no points, a negative balance, two possible account matches, an expired offer, and a customer who has opted out of messages. Ask how unmatched rows and errors are reported.
Compare the number of matched records and the total balances before and after. Then inspect individual examples. A matching total can still hide points assigned to the wrong person.
Get written approval of the result before the live move. Ask what can be undone, who can do it, and which changes cannot be reversed through the tool.
Plan the changeover while people are still earning
The changeover is the period when you stop using the old program and begin using the new one. Give one person or team responsibility for coordinating it.
- Set a final record time. Agree when the starting export is taken and how later purchases, refunds, and rewards will be recorded.
- Choose the live program. Avoid two systems independently changing the same reward balance unless there is an agreed way to keep them in step.
- Check the last changes. Account for activity between the first export and the switch. Keep a record of what has already been applied.
- Test the customer journey. Join or sign in, earn once, use a reward once, and check the supported refund process.
- Prepare the fallback. Agree when to pause the move, how staff answer customers, and how to record activity if a connection fails.
Keep old-system access available for the agreed review period where the contract allows it. Check the final renewal date and cancellation terms before paying for more overlap than you need.
Include the website, app, and staff process
Customers may reach rewards through your website, an app, a saved link, or a printed code. Check each route after the switch. Explain any new sign-in, download, or joining step.
Staff need the same reward rules and a clear person to contact about a missing balance. Confirm who handles requests at launch and which old records they can use to investigate.
If checkout or booking tools are involved, name the exact products, plans, permissions, and supported tasks. Moving a customer file does not establish that those tools are connected.
Compare the move and the ongoing service in the quote
Ask who exports the old records, prepares the file, checks the matches, rebuilds the offers, tests the connections, trains staff, and approves launch. Put a person or team beside each job.
Include migration help, any required plan, overlap with the old service, outside fees, and post-launch corrections. Ask what happens to the price and target date if records are missing or the old provider cannot export what you need.
For a budget method, use the small-business loyalty program cost guide. Compare the first year and the regular running cost using the same work in every quote.
When does the Rehost bundle fit?
Rehost is worth comparing when you need the website, customer app, and loyalty program built and run together. All three are included in one monthly business bundle. Your team sets the business rules and approves changes; Rehost handles the agreed software work.
A move depends on access, usable exports, vendor support, and the written scope. Confirm the records, rewards, connections, checks, and handoff before agreeing to the switch. Rehost does not promise that every old program can be copied in full.
Check current pricing and terms for the offer and ongoing service. If your only gap is a simple reward card, our small-business loyalty app buyer’s guide also covers lighter options.
FAQ
Can every customer record and reward move automatically?
No. It depends on the export, the new tool, account matching, and the work included. Ask for a record-by-record plan covering points, unused rewards, member levels, preferences, and history.
Should we cancel the old program before the import?
Agree the changeover and review period first. Check cancellation dates and what access ends with the service. Keep the records and access needed to verify the move before ending the old setup.
Can customers keep using rewards during the switch?
That depends on the supported process. Confirm where activity is recorded, which system is live, and how later changes reach the new balance. Tell staff and customers about any planned pause.
Bring one export description and one customer journey
Start by listing what your current program can provide and what customers need to keep. You can discuss the scope before sharing any customer file.
Explore Rehost’s website, app, and loyalty bundle, then review the monthly pricing and written terms.