How to migrate from LoyaltyLion Shopify is a controlled transfer of customer balances, tier status, and loyalty history into a new program. The work changes when you use Mage’s direct connector, because the main import should not begin with a spreadsheet.
A Shopify loyalty program includes points, rewards, tier logic, referral messaging, storefront placements, and connected email or SMS events. A migration succeeds only when those parts work together after launch. If you are evaluating the switch itself, see Mage’s LoyaltyLion alternative.
Short answer: Document the current program, create matching VIP tiers in Mage, then go to Settings > Data Migration > Import Data and connect the provider import. Use Manual CSV Import only for data the connector does not cover. Test balances, tiers, earning, redemption, refunds, and storefront surfaces before removing the old app.
“I looked into so many different integrations for loyalty and referrals for our Shopify Store, but no one impressed me more than Mage on human connection, customer service, and value.”
Read the Reelie case study →
How to migrate from LoyaltyLion Shopify: document the program first
Create a migration inventory
Start with a written record of the live program. Include earning rules, point value, reward types, reward costs, minimum spends, expiry settings, VIP tier names and thresholds, referral rules, customer-facing copy, and every place customers interact with loyalty.
Also list connected email, SMS, reviews, subscription, support, returns, and storefront tools. Capture theme edits, app embeds, custom CSS, and landing pages.
Shopify warns that app data may not be recoverable after uninstalling an app, so export important records before making changes. Shopify’s uninstall guidance also notes that theme code and dependent features may need separate review.
Capture a baseline
Record active members, total points liability, points issued and redeemed, redemption rate, member revenue, repeat purchase rate, average order value, VIP distribution, referral activity, and recent refunds.
Use this as your comparison record after launch. Shopify’s loyalty analytics guide can help define the baseline, but your own pre-migration data is the number that matters.
Decide what should be copied versus redesigned
Review reward thresholds, expiry, tier qualification, and referral incentives before rebuilding them. Preserve balances first. Change program economics only when you can explain the customer impact.
This is also the right time to decide whether the existing currency model still makes sense. Read loyalty points versus store credit before changing it, then document the decision.
Map LoyaltyLion data to Mage before connecting the accounts
| Data area | Primary migration path | Validation requirement | Manual follow-up |
|---|---|---|---|
| Current points balance | Direct provider connector | Compare sample balances and total liability | Correct exceptions only after review |
| VIP tier | Direct provider connector | Check base, middle, and highest tiers | Create matching tier names first |
| Points history | Direct provider connector | Review selected earning and redemption records | Use CSV only for documented gaps |
| Reward history | Confirm in the provider import result | Check recent redemptions | Manual review if not included |
| Referral records | Confirm in the provider import result | Test attribution and customer messaging | Manual review if not included |
| Wishlists | Manual CSV Import if unsupported | Check saved item counts and customer matching | Import only if needed |
| Earning rules and rewards | Configuration work | Test live earning and redemption | Rebuild or redesign |
| Customizations and communications | Configuration work | Check customer-facing surfaces | Recreate branding and messages |
What the direct connector carries
Mage’s direct provider connector is the primary migration route. In the Mage admin, go to Settings > Data Migration > Import Data, select Migrate from a provider, choose LoyaltyLion, then select Continue with LoyaltyLion. See the Mage migration help centre for the documented migration process.
The connector imports points, tiers, and history automatically. Do not assume that every legacy rule, referral message, reward, landing page, or visual customization transfers with the data. Those are program configuration decisions that need separate review.
Create matching VIP tiers first
Create your VIP tiers in Mage before starting the import. The tier names need to match the existing names, although matching is case-insensitive.
For example, “Gold” and “gold” match. “Gold Member” and “Gold” do not. Customers whose tier does not match can import without the intended tier.
Connect LoyaltyLion to Mage and import the core loyalty data
Use Migrate from a provider
Open your Shopify admin, then open the Mage Loyalty app. Go to Settings > Data Migration > Import Data.
Under Migrate from a provider, choose LoyaltyLion and select Continue with LoyaltyLion. Follow the connection flow to connect the existing account. Mage then imports points, tiers, and history automatically.
Do not build a CSV for the main migration when the direct connector is available. Use a manual import only for missing data that you have confirmed was not included in the provider import.
Validate the import before changing the storefront
Start with counts and totals. Check total current points balance against your pre-migration liability record, then sample customers from several situations:
- A customer with no VIP tier
- A customer in the base, middle, and highest tier
- A recent purchaser
- A customer with a high points balance
- A customer with a recent redemption
- A customer with a refunded order
Compare points, tier assignment, and visible history against your baseline. Document exceptions in one place before enabling the new widget, loyalty page, referral surfaces, or checkout rewards.
Use Manual CSV Import only for data the connector does not cover
Choose the correct import type
Use Manual CSV Import as a supplement, not the default route. In Mage, return to Settings > Data Migration > Import Data and choose the relevant import type.
The available import types are Loyalty Members, Points Logs, Rewards History, and Wishlists. Import one data set at a time and only when you can confirm it has not already been brought in through the connector.
Prepare supplemental data carefully
Save the original export as an immutable backup. Work from a duplicate file so you can record cleanup or corrections without changing the source record.
For a Loyalty Members CSV, email is required. Review duplicate, inconsistent, or missing emails before importing. If the file includes tier data, confirm tier names match the tiers you created in Mage.
Troubleshooting check: Review unmatched tier names, duplicate customer emails, missing Shopify customers, and incomplete records before attempting another upload. Keep a log of manual decisions so support can answer questions after launch.
Rebuild and test the customer experience before launch
Recreate earning and redemption rules
Rebuild the program logic from your migration inventory. This includes purchase earning, signup bonuses, birthday rules, rewards, minimum spends, points expiry, VIP benefits, and referral communications.
Points expiry is off by default in Mage. If you enable it, choose the expiry mode deliberately and verify that customer reminders are configured through the relevant email or SMS connection.
Test storefront and checkout surfaces
Use Mage Canvas to configure the loyalty page, Rewards Widget, customer account sidebar, referral surfaces, wishlist surfaces, colors, typography, spacing, and layout.
Enable the Mage app embed on the live theme before launch. Then test the same theme configuration customers will use.
Run a new signup, a purchase that earns points, a reward redemption at Shopify Checkout, VIP tier progress, referral attribution where applicable, account login, and wishlist earning if enabled.
Test refunds and VIP progression
Test partial and full refunds before going live. Mage reverses points from partial refunds proportionally and rounds down. It also adjusts spend-based VIP totals when refunded value affects tier qualification.
Use a test order with an amount that produces a non-round point calculation. Then verify the remaining balance and tier progress. Read how Mage helps merchants handle returns and refunds in a Shopify loyalty program before deciding how to communicate reward reversals.
Plan the cutover, customer communication, and old-app removal
| Check | Owner | Evidence | Pass or fail |
|---|---|---|---|
| Points liability reconciled | Loyalty owner | Pre-launch totals and sample records | |
| VIP tiers match | Program owner | Base, middle, and top-tier customer checks | |
| Theme and app embed verified | Storefront owner | Live-theme screenshots | |
| Checkout redemption tested | Ecommerce owner | Test order and redemption record | |
| Refund behavior tested | Support owner | Partial and full refund results | |
| Integrations reviewed | Marketing owner | Event and profile checks | |
| Customer communication approved | Support owner | Final email or help copy | |
| Old app cleanup documented | Technical owner | Theme, workflow, and billing review |
Choose a cutover window
Pick a lower-risk trading window and assign one owner for final balance checks, storefront checks, customer-support checks, and rollback decisions.
If you keep the old app active briefly for validation, pause earning and redemption where possible and avoid running two live reward engines for an extended period. Pause major promotions, large point campaigns, and referral pushes while you reconcile imported data.
Tell customers what changes
Explain where customers can see points, how rewards work at checkout, whether the loyalty page or account experience has moved, and where to ask for help if a balance appears wrong.
Do not promise that every historical interaction will appear exactly as it did before. Give support a clear escalation process for balance questions and outstanding rewards.
Uninstall only after validation
Keep exports, screenshots, configuration notes, and pre-launch totals before removing the old app. Review Mage integrations alongside your own stack to make sure relevant workflows are connected.
Shopify warns that uninstalling an app can leave theme code behind and can stop dependent workflows, integrations, or storefront features. Uninstall only after the new program is live, tested, and supported by your team.
Monitor the first 30 days after switching from LoyaltyLion
Review points issued, points redeemed, reward errors, refund reversals, VIP tier distribution, referral conversions, account logins, and tickets about missing balances daily during the first week.
Then move to a weekly review and compare results with your pre-migration baseline. Use Mage analytics for loyalty, VIP, referral, wishlist, and saved-for-later behavior where those features are enabled.
Fix balance errors, broken surfaces, missing events, and confusing redemption flows first. Once the program is stable, optimize one variable at a time. Review the loyalty program metrics that matter to keep the review focused.
Frequently asked questions
Can I migrate LoyaltyLion points to Mage?
LoyaltyLion points can migrate to Mage through the direct provider connector. In Mage, go to Settings > Data Migration > Import Data, choose LoyaltyLion under Migrate from a provider, and select Continue with LoyaltyLion. Check a representative customer sample and reconcile your total points liability before launching the new program.
What LoyaltyLion data transfers to Mage?
LoyaltyLion data that transfers through Mage’s direct connector includes points, tiers, and history. Earning rules, rewards, branding, customer-facing layouts, referral messaging, and unsupported data sets should be reviewed separately. Confirm reward history and referral records in the provider import result before relying on them.
Do I need a CSV to migrate from LoyaltyLion to Mage?
A CSV is not required for the primary LoyaltyLion migration to Mage. Use the direct provider connector first, then use Manual CSV Import only for unsupported data, such as wishlists, or for a carefully reviewed correction.
How do I migrate LoyaltyLion VIP tiers?
Create matching tier names in Mage before the import. Tier matching is case-insensitive, but names must otherwise match. After importing, check customers in the base, middle, and highest tiers to make sure their status transferred as intended.
Can I run LoyaltyLion and Mage at the same time?
If you keep the old app active briefly for validation, pause earning and redemption where possible and avoid running two live reward engines for an extended period. Parallel earning and redemption can create duplicate rewards, conflicting rules, and inconsistent balances.
When should I uninstall LoyaltyLion from Shopify?
Uninstall only after exports, configuration notes, import validation, storefront tests, integration checks, and customer communications are complete. Shopify warns that app data can become unrecoverable after uninstall and that theme code, automations, integrations, or dependent storefront features may require separate cleanup.
Ready to see Mage in action? Book a demo.
Graeme is the co-founder at Mage Loyalty. He heads product development, from complex loyalty migrations and large-scale data handling to building the features shaping the future of loyalty on Shopify.
