LoyaltyLion to Yotpo Loyalty Migration
Steps, data mapping, and the gotchas that cost merchants a weekend. Written for people actually doing the migration, not for people choosing a vendor.
A LoyaltyLion to Yotpo Loyalty migration takes one to two weeks of calendar time and roughly 8 to 15 hours of hands-on work for a single-store program. Point balances transfer by CSV matched on customer email. Nothing else does: earning rules, tiers, and widget styling are rebuilt by hand, and activity history, redemption history, and referral attribution are lost.
The biggest gotcha: reward vouchers LoyaltyLion already issued live in Shopify as discount codes, not in the app. They stay redeemable after you uninstall. If you do not audit and expire them before cutover, you carry an unbudgeted discount liability into the new program.
Before you touch anything: the export checklist
Everything you fail to document before cutover has to be reconstructed from memory afterwards. Five exports cover the whole program.
Export customers with point balances
From LoyaltyLion, export the customer list with current point balances to CSV. This file is the only thing that carries real value into the new program — everything else is documentation. Verify the export includes customer email, since email is the key both platforms match on.
Screenshot every earning rule
Points per currency unit, sign-up bonus, birthday points, review points, social actions, and any rule with a date window or product-collection restriction. LoyaltyLion rule logic does not export in a machine-readable form you can replay, so screenshots plus a spreadsheet are the practical record.
Document tier thresholds and benefits
Record each tier name, the points or spend threshold that unlocks it, the benefits attached, and the tier-review period (rolling 12 months, calendar year, lifetime). Tier logic differs between platforms, so you need the exact rules to rebuild them rather than approximate.
Pull the list of outstanding reward codes
In Shopify Admin, export active discount codes. LoyaltyLion issues rewards as Shopify discount codes, so unredeemed vouchers survive the uninstall and stay redeemable. Decide now which ones you will honor and which you will expire.
Note every integration touching loyalty
Klaviyo flows referencing loyalty events, Gorgias macros quoting balances, Recharge subscriptions granting points, custom API calls. Each is a separate rewiring job after cutover and the most common source of post-migration silence from your email program.
What transfers, what does not
Point balances are the only data that moves between LoyaltyLion and Yotpo Loyalty. Every other row in this table is either rebuilt by hand or lost, and knowing which is which before you start is the difference between a planned migration and a surprise.
| LoyaltyLion | Yotpo Loyalty | Transfers | Note |
|---|---|---|---|
| Point balances | Points balance (CSV import) | Yes | Imports as an opening balance matched on customer email. Customers with a different email in each system will not match. |
| Earning rules | Earning rules (rebuilt manually) | No | No transfer path exists. You rebuild each rule in the Yotpo admin from your documentation. |
| VIP tiers | VIP tiers (rebuilt manually) | No | Thresholds and benefits are rebuilt by hand. Tier membership recalculates from the imported balance, which can move customers between tiers. |
| Points ledger and activity history | Not supported | No | Customers lose the "how did I earn this" view. Balances arrive as one opening number with no backing history. |
| Redemption history | Not supported | No | Support agents lose the record of what a customer previously redeemed. Export it to CSV if your team relies on it. |
| Issued reward codes | Remain as Shopify discount codes | Partly | They keep working at checkout because they live in Shopify, not in the loyalty app. The new app has no record of them. |
| Referral links and attribution | New links generated | No | Advocate links change. Any referral link already shared by a customer stops attributing on cutover day. |
| Widget styling | Rebuilt in Yotpo | No | Colors, copy, and placement are reconfigured. Budget an hour, more if you had custom CSS. |
The migration sequence
Run both apps in parallel with the new widget hidden, freeze earning before the final export, and swap widgets in a single session. The order matters more than the speed.
- 1
Install Yotpo Loyalty with the widget hidden
Install the app but keep the customer-facing widget disabled or restricted to staff accounts. Two visible loyalty widgets on one storefront is the fastest way to generate support tickets.
- 2
Rebuild earning rules from your documentation
Work rule by rule from your spreadsheet. Where Yotpo has no equivalent for a LoyaltyLion rule, decide explicitly whether to drop it or approximate it. Write down every deviation; this list becomes your customer communication.
- 3
Rebuild tiers, then check who moves
Recreate thresholds, then model which customers land in which tier once balances import. Tier logic differences routinely demote a handful of long-standing customers, and finding that on cutover day is worse than finding it now.
- 4
Freeze earning in LoyaltyLion
Pick a cutover window and stop new accrual in the old app first. Points earned between your CSV export and the import land in a system you are about to switch off, and reconciling them by hand is the single most tedious part of any migration.
- 5
Export fresh, import, reconcile
Re-export balances immediately after the freeze so the file is current, then import into Yotpo. Reconcile with a sample: pick 20 customers across the balance range, including your top five, and verify each balance matches to the point.
- 6
Rewire integrations
Point Klaviyo flows, helpdesk macros, and any custom API calls at the new platform. Loyalty emails referencing balances break silently, so send yourself a test through every flow before enabling them.
- 7
Swap the widget, then remove old code
Enable the Yotpo widget and disable the LoyaltyLion one in the same session. Then remove leftover LoyaltyLion script tags and theme snippets — an uninstalled app frequently leaves code behind that still ships bytes to every visitor.
- 8
Tell customers what changed
One email covering: balances carried over, what the new widget looks like, which rules changed, and what happens to old reward codes. Migrations that skip this step generate a spike in "where did my points go" tickets even when nothing was lost.
Know what you are migrating into
LoyaltyLion and Yotpo Loyalty price differently, and neither publishes a number you can plan around at scale. As of August 2026, LoyaltyLion has moved its paid tiers to custom quotes; the Small Business and Classic plans that used to be published are legacy and available to existing customers only. Yotpo Loyalty charges per order, roughly $0.08 to $0.20, with a free tier under 100 orders per month and quote-based pricing above 5,000.
Run the arithmetic before you commit. At 500 orders a month, per-order pricing lands somewhere between $40 and $100. At 5,000 it is $400 to $1,000, and past that you are back in a negotiation. If the reason you are leaving LoyaltyLion is unpredictable enterprise pricing, verify in writing that the destination is different, because a per-order model scales with your success in exactly the way a flat plan does not.
The third option: evaluate the field first
Migrating between two enterprise-priced platforms is a lot of work to end up with the same category of contract. If the trigger for this move is cost or complexity rather than a specific missing feature, price the whole field before you commit, because the migration effort is identical whichever destination you pick.
Our evaluation framework scores seven criteria including true cost at your order volume and migration path in and out, and the tested ranking of eight apps has the current pricing for each.
Full disclosure: we build Anchor Loyalty, which is one of the options that framework covers. It is $14.99 a month flat regardless of order volume, imports point balances from CSV matched on customer email, and ships a 14 KB widget. We rank it against the alternatives on the same measured criteria as everyone else — judge the data, not us.
shopping_bagInstall Anchor free on ShopifyFrequently asked questions
Do customer point balances transfer from LoyaltyLion to Yotpo Loyalty?
Yes. Export customers with their point balances to CSV from LoyaltyLion, and Yotpo Loyalty can import those balances matched on customer email. What does not transfer: redemption history, activity ledgers, issued-but-unredeemed reward codes, and referral attribution chains. Balances move as a single opening number, not as a history.
How long does a LoyaltyLion to Yotpo migration take?
Plan one to two weeks of calendar time with roughly 8 to 15 hours of hands-on work for a typical single-store program: one to two days to export and document the LoyaltyLion program, two to three days to rebuild earning rules and VIP tiers in Yotpo and run both apps in parallel with the Yotpo widget hidden, then a cutover day for the balance import, spot-check reconciliation, and widget swap. Programs with custom API integrations or multiple storefronts take longer.
What happens to outstanding LoyaltyLion reward codes after I uninstall?
Reward vouchers that LoyaltyLion issued exist as Shopify discount codes, so they remain redeemable at checkout after you uninstall the app unless you deactivate them. Before cutover, export the list of active discount codes from Shopify Admin, decide which outstanding rewards you will honor, and set an expiration date or deactivate the rest. Skipping this step means carrying an unbudgeted discount liability into the new program.
Smile.io to Yotpo Loyalty
The same migration from the other common starting point.
All migration guides
Switching from Smile.io, Yotpo, or LoyaltyLion to Anchor.