Group chat for people who care if their incentives actually make money
0
Days
0
Hours
0
Minutes
0
Seconds
Join marginmaxx
2026-11-12 12:00 am
2026-10-07 12:00 am
2026-09-23 12:00 am
2026-09-22 12:00 am
2026-09-09 12:00 am
2026-08-18 12:00 am
2026-09-29 12:00 am
2026-05-06 12:00 am
2026-04-14 12:00 am
2026-04-21 12:00 am
2026-04-23 12:00 am
2026-04-28 12:00 am
2026-01-11 12:00 am
2026-09-28 12:00 am
Loyalty

How to migrate and revamp your loyalty program (without losing points or customers)

Julia Gaj
November 17, 2026
  • Don't just move your loyalty program to a new platform, use the migration to fix what wasn't working.
  • Get leadership to agree on who you'll upset before you change anything, not after.
  • Protect existing point balances at all costs, and make any devaluation on the earn side, never the redemption side.

Where loyalty program migrations go wrong

Every loyalty program eventually gets replatformed. The vendor gets acquired, the in-house system nobody wants to touch finally breaks, or someone in finance asks what all those points are even for? And most teams handle it the same way: they move everything, exactly as it was, to a shiny new platform. A nicer admin panel with the same earn rate, tiers and rewards nobody cares about.

A loyalty program migration is the one moment when changing the program is expected. Your members are already getting an email about it. Your engineers are already rebuilding the integrations and leadership is finally paying attention (hallelujah!) Wasting that moment on a straight copy-paste is like moving house and packing the broken toaster.

This guide covers both parts: how to migrate a loyalty program without losing points or member trust and how to use the move to revamp what wasn't working before.

When it's time to migrate or revamp your loyalty program

Not every program needs a new loyalty platform, some just need a hard look. Here's what I hear most often from teams who are ready to move:

  • Nobody can maintain it anymore: The in-house system was built by someone who left years ago and every change is now a risk.
  • Every change needs a sprint: Marketing wants to test a double-points weekend, and all engineering does is add it to the backlog.
  • Our channels don't agree: Online and in-store run separate promotion and loyalty logic, so the same customer gets different answers at checkout.
  • We can't prove it works: The program costs real money every year and nobody can say what it returns besides optional member count growth or higher email open rates.
  • Our vendor changed: An acquisition, a pricing jump at renewal or a roadmap that drifted away from what you need. 
  • We want to do things it can't: Rewarding reviews or app streaks, adding tiers, going multi-country or multi-currency, you name it.

Most teams face a mix of the above, which is why a loyalty program migration and revamp usually belong in the same bucket.

How to choose your loyalty migration approach?

There are really 3 ways to move a loyalty program and each one trades speed for impact.

ApproachWhat changesBest whenRisk
Lift-and-shiftOnly the platformThe program works and you're only escaping a bad system or vendorYou pay for a migration and get the same results
Staged revampPlatform first, program in planned phasesYou need to move fast but know the program needs workPhase two quietly never happens
Full revampPlatform and program at onceThe program can't justify its cost anymoreTwo big changes land on members at the same time

The default is the staged revamp. Move the balances and the rules members can see, keep them stable for one cycle, then start changing the program once the new platform is proven. One brand I worked with put it simply when launching a new market: start with the simplest version that will go live safely, then grow.

The one thing I'd never do is a lift-and-shift with no plan for what comes next. A migration project burns a lot of goodwill with engineering and leadership, make sure you spend it on something.

What moves in a loyalty migration and what stays behind

Before anyone writes a migration script, sort your data into three piles. This is the checklist I'd start with:

DataMove it?Why it matters
Point balances (active and pending)AlwaysThis is money in your members' heads, and a liability on your books
Tier status and progressAlwaysLosing someone's Gold status overnight is the fastest way to lose them
Customer profiles and IDsAlwaysEverything else hangs off the customer ID, so map it first
Issued vouchers and codes in walletsAlwaysA code a customer already holds has to keep working
Active campaigns and earning rulesRebuild, don't copyThe perfect moment to delete the rules nobody understands
Point expiration datesAlwaysResetting them is either a gift you didn't budget or a complaint you didn't plan
Full transaction historyUsually notExport it to your data warehouse and keep it for support and audits
Old, expired or unused campaignsNoLeave them behind, with relief

The most common surprise is history. Teams assume every past transaction must come across, then discover it doubles the project. Most of the time, the new platform needs balances and statuses, while the history lives happily in your warehouse.

A step-by-step loyalty program migration plan

A loyalty migration runs in five phases, but the order matters more than the speed.

  1. Audit and decide: List every rule, reward and integration. Decide what moves, what gets rebuilt and what dies. Get sign-off on the program changes now (more on that below).
  2. Build in parallel: Set up the new platform, rebuild the rules you're keeping and connect it to your commerce, CRM and POS systems. The old system keeps running.
  3. Run side by side: Send the same orders to both systems and compare balances until the numbers match. This is the step teams skip when they're behind schedule, and it's the one that saves them.
  4. Cut over: Freeze the old system, move the final balances and switch traffic. Pick a quiet week, not the one before Black Friday.
  5. Revamp in phases: Once the new platform has run cleanly for a full cycle, start changing the program itself: new earn rules, new rewards, new tiers.

How to protect points, tiers and member trust during a revamp

If a revamp means making the program less generous somewhere, the question is where. And there's a right answer.

Change the earn side, not the redemption side. Points already in a member's account are a promise. Change what they're worth, and you're breaking it. Ory Adler, who relaunched a decades-old loyalty program at a large retailer, put it bluntly when I interviewed him for our marginmaxx community:

"If you are playing with the redemption value, you could trigger a run on the bank." – Ory Adler, co-founder @Innovate Marketing

A points balance is a liability on your balance sheet and an expectation in your customer's head. Cut what it's worth, and members rush to redeem before it shrinks further. Earn changes only affect the future, which is why devaluations should happen there.

A few other rules that keep trust intact:

  • Carry every balance and tier across, exactly.
  • Tell members before with one clear email: what's changing, what isn't, and when.
  • Give a grace period on tiers, keep everyone's current status for one full cycle on the new program.
  • Don't reset expiry dates. Members who were about to lose points will notice if they suddenly don't, and the ones who were about to keep them will notice if they suddenly do.

Get leadership to sign off on the backlash before you launch

Here's the moment every loyalty team dreads. You launch the revamped program, a vocal group of members complains on Reddit and socials, and a senior stakeholder forwards you an angry email with one line: "Why are customers upset?"

What happens next decides whether your revamp survives. Most teams soften the offer, restore the old perk and end up with the old program, minus their credibility.

Ory Adler avoided that by having the hard conversation first. Before relaunching, he took a proposal to the exec team: high-value customers would be rewarded disproportionately, and some customers would like the program less. Leadership agreed upfront:

"We agreed with the exec team that we will accept negative feedback from those infrequent customers." Ory Adler, co-founder @Innovate Marketing

The other part of the conversation is how you'll measure success. Ory measured retention in margin, not customer counts:

"If I lost one whale that spends 4,000$ a year and generates 1500$ in margin, that is more meaningful to the business." – Ory Adler, co-founder @Innovate Marketing

Count heads, and losing 15 occasional customers looks worse than losing one big one. Count margin, and the big one is ten times the problem. Agree on which number matters before launch, and the complaints from low-value members stop looking like failure.

How a loyalty migration to Voucherify works?

Full disclosure: this is the part where I tell you how we do it. We've moved teams off homegrown systems and other vendors, and the process follows the plan above.

  • What comes with you: active campaigns and their rules, vouchers and codes already in customers' wallets, current point balances and customer profiles.
  • What stays behind: past transaction records. Export what you need for support and audits before you go.
  • How we run it: you get a free migration scope, even if you don't switch. Then you choose self-service, guided support or a dedicated migration lead.
  • The safety net: both platforms run side by side until the numbers match, and nothing switches off until you say so.

We're also happy to run a free POC before you commit to anything longterm.

Once you're live, the revamp phase is where the platform earns its keep. Marketers build and test new campaigns without an engineering sprint, and guardrails like pending points, earning caps and budget limits stop a new program from leaking margin while you experiment.

 FAQs

How do you migrate a loyalty program to a new platform?

Audit what you have, rebuild only the rules worth keeping, then run both systems side by side until the balances match. Cut over in a quiet week, and save the program changes for after the new platform has proven itself.

Do loyalty points carry over when you switch platforms?

They should, always. Move every balance, tier and expiry date exactly as it is. A member who loses points in a migration rarely sticks around for the explanation.

How long does a loyalty program migration take?

It depends on how many systems the program touches, not how many members you have. Whatever your plan says for the side-by-side run, add a bit. That's the step that catches the surprises.

Should you revamp your loyalty program during a migration?

Yes, just not on the same day. Move first, keep things steady for one cycle, then revamp. Changing the platform and the program at once is two surgeries in one appointment.

How do you cut loyalty program costs without upsetting members?

Change the earn side, not the redemption side, and point the expensive perks at your best customers. Agree with leadership upfront that some low-value members will grumble, so nobody panics when they do.

Do you need to migrate transaction history?

Usually not. The new platform needs balances, statuses and profiles. Your old transactions can retire happily to the data warehouse.

Julia Gaj

Product Marketing Manager @Voucherify

Shapes how Voucherify talks about incentive optimization, from positioning and competitive narratives to campaign launches. Obsessed with modern marketing mechanics and what actually moves pipeline.

Are you optimizing your incentives or just running them?