For chains switching loyalty platforms

Loyalty platform migration without losing a single point

Move every member, balance, tier and rule to the new platform, and check its numbers against your POS before cutover. Guests keep their points and don't have to sign up again.

For restaurant groups with 30–250 locations and retail chains with 50–300 stores

It starts with a free 45–90 minute call. Bring your contract end date.

In short

A loyalty platform migration moves members, points balances, tiers, history and program rules from one platform to another without guests losing anything. Done right, it includes a full export, a map of every field and rule, a dry run on real data, and a check of the new platform's numbers against your POS before cutover. For a chain with 30–250 locations, it usually takes 8–16 weeks. The first step is a 2–3 week Assessment.

Market numbers

Your loyalty data is worth more than the platform

Checked November 9, 2026. Qu surveys chains larger than most groups we work with.

What breaks

Where a loyalty switch goes wrong

The risk sits in four moments, and most of them come before launch day.

  1. Notice given

    The contract end date is set, and the old vendor's export is missing fields you need.

  2. Mapping

    Tiers, expiring points and custom rules have no match on the new platform.

  3. Cutover

    Balances in the new app don't match the old one. Guests notice first, at the register.

  4. First 30 days

    The new platform's reports don't match POS sales, and nobody knows which number is right.

What we do

A loyalty migration plan, week by week

We rehearse the migration on your real data before any guest sees it.

  1. Assessment

    An audit of the export, a map of fields and rules, and a dry run on a sample of members.

    Weeks 1–3
  2. Build

    Migration scripts, POS connections and the rules the new platform can't handle out of the box.

    Weeks 4–8
  3. Rehearsal

    A full dry run, then balances checked against the old platform and your POS.

    Weeks 8–12
  4. Cutover

    Switch over, then 30 days of daily checks on balances and transactions.

    Weeks 12–16

Timelines are typical for a chain with 30–250 locations. We confirm them in the Assessment.

What you'll need

What you need for a loyalty switch

  • Connect your stack

    One loyalty program across every brand

    One guest profile and one balance for every brand and location, plus rules your platform doesn't offer.

    Restaurant loyalty program software
  • Connect your stack

    Reporting that matches the POS

    Loyalty transactions checked against POS sales, by brand and location.

    Restaurant reporting
  • Connect your stack

    POS integration

    Points earned and redeemed at every register, including franchisees' POS systems.

    Restaurant POS integration

What we find in loyalty migrations · November 2026

Where it usually hurts

  • The old platform set the rules, and some of them were never written down.

  • Custom rules, like double points only for guests who haven't visited in a week, have no setting on the new platform.

  • The platform's report and POS sales disagree, and nobody has checked by how much.

  • Guests won't sign up twice, so the new app has to recognize them at first sign-in.

Questions

Didn't find your answer? Ask on the call.

  • For a chain with 30–250 locations, usually 8–16 weeks from the start of the Assessment to cutover. The export and the rules take most of that time. Moving the records is the fast part.

  • Members and their marketing consents, current balances, tiers and expiry dates, the full transaction history, rewards issued and redeemed, and the program rules, including the ones that live only in someone's head. Check what your contract says the vendor must hand over before you give notice.

  • Usually not. A parallel run doubles the work for staff and confuses guests. It makes sense only when the old platform can't give you a complete export, so balances have to sync for a few weeks. We decide that in the Assessment.

  • With dry runs on real data: first a sample of members, then the full base. Balances, tiers and transactions on the new platform must match the old platform and your POS sales. You launch only when they do.

  • We build those rules next to the platform, on your data, so you're not waiting on the vendor's roadmap. Double points only for guests who haven't visited in a week is a typical example.

  • Sizl, a dark-kitchen chain in Chicago, is our US project. For a 16-brand restaurant group in Saudi Arabia, Kuwait, the UK and the US, we're launching its own ordering and delivery. Our Lisbon workday matches the UK and overlaps with US mornings.

You talk to the people who will do the work

  • Max BantsevichFounderLinkedIn
  • Andrey MaksimenkoProject Manager
Max Bantsevich, founder of dev.family
Andrey Maksimenko, project manager at dev.family

Trust and security

  • Headquartered in Lisbon, in the EU: contract and DPA under EU rules

  • We sign an NDA before the first call if you need one

  • Security pack and data-flow diagram on request

  • Our workday matches the UK and overlaps with US mornings

  • You own the code, the models and the data

Switching loyalty platforms?

A call to check your contract dates, what's in the export and which rules won't survive the move.

A 2–3 week Assessment: an audit of your export, a map of fields and rules, a dry run on a sample of members and a fixed migration estimate. It's credited toward Build if you start within 60 days. How our packages work: How we work

Max will reply within 1 business day and suggest a time for a call.

Who are you
How many locations
What's happeningpick any
Your POSoptional