How to Migrate from Smile.io to Yuko: Step-by-Step Guide

If you’re ready to migrate from Smile.io to Yuko, then know that you can move your entire loyalty program without your customers losing a single point they’ve earned. Switching loyalty apps is risky because a single issue can lead to many support tickets. However, with the right preparation, none of that has to happen.

If your store has outgrown Smile.io, but you’re worried that switching may be hard, then know that every week you delay is just putting off the inevitable. So the question isn’t whether to move. It’s how to do it cleanly. 

With this guide, you’ll know how to do loyalty app migration while preserving what you have built with the trust of your customers.

Why migrate from Smile.io to Yuko?

Loyalty programs, in short, are not one-size-fits-all. A program that worked well when you had 500 customers may not hold up once you’ve got 10,000 active members, layered VIP tiers, and referral campaigns running alongside email automations. So it makes sense that your needs would eventually outpace the tool.

Smile.io is a well-known Shopify loyalty app, and yet merchants outgrow it for predictable reasons. Here’s what typically drives the loyalty program migration decision:

• Pricing scales quickly: Smile.io’s pricing is tied to monthly orders, and costs climb fast as your store grows. Many merchants end up paying for tiers of features they never use.
• Limited automation: Smile.io handles points and tiers well, but building workflows like a points-expiry email or a VIP upgrade message means connecting third-party tools.
• Separate apps for referrals and memberships: Smile.io focuses on points and tiers, so referrals, memberships, and reviews mean stitching together multiple apps.
• Widget customization constraints: Some merchants find it hard to match Smile.io’s storefront widgets to their brand without custom development.

Before you start any Smile.io migration, therefore, answer these four questions:

• How many active loyalty customers do you have, and what are their current points balances?
• Do you have VIP tiers in Smile.io, and how are they structured?
• Are there active referral rewards or pending discount codes customers haven’t used yet?
• What’s your planned go-live date, and do you have a communication plan ready?

Answering these upfront saves hours of cleanup work later, and it sets up everything that follows in this Smile.io migration guide.

Smile.io migration without losing customer points

You can migrate from Smile.io without losing customer points by preparing your data and rules before you uninstall the app.

What customer data can be migrated?

When you migrate from Smile.io to Yuko, the following typically transfers:

• Customer email addresses and names
• Current Smile.io points balances
• Smile.io VIP tiers, mapped to their Yuko equivalents
• Points transaction history (for reference, not always imported directly)
• Referral records, where applicable

What happens to points, tiers, and accounts

Points balances are the most critical piece of data, and Yuko’s customer management system lets you import them via CSV, so customers keep exactly what they earned. VIP tiers, meanwhile, require manual mapping, since Smile.io and Yuko use different tier structures.

For example, if Smile.io has a “Gold” tier at $500 lifetime spend, you’ll create a matching Gold tier in Yuko at the same threshold before importing. Customer accounts in Shopify stay completely untouched throughout, because Yuko reads from the same Shopify customer records Smile.io used, so there’s no disruption to login credentials or order history.

What you’ll need to rebuild

On the other hand, a few things don’t transfer automatically:

• Earning rules: Your points-per-dollar rate, signup bonuses, and birthday rewards
• Redemption rewards: Discount codes, free shipping, and store credit options
• Email templates: Yuko has its own notification system to customize
• Storefront widgets: The floating launcher, cart earn, and cart redeem placements

None of this is technically complex, because it is configuration work and not related to development. With that disambiguation in place, what transfers automatically versus what you rebuild, you’re ready to gather the actual data.

If you are confused about the switch, then read our comparison of Smile.io alternatives to know what you can improve by migrating.

What data should you export from Smile.io before migration?

A clean export is the foundation of any smooth Smile.io migration, so export everything before you touch a single setting.

Customer information and points balances: From your Smile.io dashboard, export the full customer list, including email address, first and last name, current points balance, lifetime points earned, and date joined. This file becomes your primary import source, since every customer in it will have their balance recreated in Yuko.

VIP tier and loyalty status data: Following that, export your tier data separately, including customer email, current tier name, tier entry date, and qualifying spend or points total. So you can assign customers to the correct tier after import.

Referral, reward, and program data: Finally, export pending referral rewards, issued discount codes that haven’t been redeemed, and any active birthday or anniversary reward records. Pending rewards need manual handling: you’ll either honor them in Yuko by issuing equivalent codes, or communicate to affected customers that their reward will be reissued.

Create a complete Smile.io migration checklist: Before you close the export screen, confirm you have:

• Full customer list with points balances (CSV)
• VIP tier assignments (CSV)
• Pending referral rewards (CSV or manual list)
• Unredeemed discount codes (CSV)
• Notes on your current earning rules, redemption rewards, and tier thresholds

Save everything to a dedicated folder, since you’ll reference these files throughout the migration. Once your exports are in hand, the next step is to make sure you have everything else needed to start the process.

If you want to increase your loyalty program success, then read our guide: Ultimate loyalty programs guide .

What you need before you start migration

Before beginning, confirm you have the following in place; otherwise, you’ll end up pausing mid-migration to track something down:

• Smile.io merchant account access: Admin-level login to export customer data
• Shopify admin access: To install Yuko, edit themes, and manage discount codes
• Spreadsheet tool: Google Sheets or Microsoft Excel for data cleaning
• Yuko installed or ready to install: Available free on the Shopify App Store
• 2 to 8 hours of uninterrupted time: Depending on your customer list size
• A test Shopify customer account: For end-to-end testing before go-live

Fortunately, no coding knowledge is required, as every step here can be completed through dashboards and spreadsheets. With that checklist covered, you’re ready to move into the core of this Smile.io migration guide: the step-by-step process itself.

How to migrate from Smile.io to Yuko: Step-by-step

This section walks through how to migrate from Smile.io to Yuko, from your first audit through go-live. Follow the steps in order, since each one builds on the last.

Step 1: Audit your existing Smile.io loyalty program

Before exporting anything, document what you currently have. Log into Smile.io and record your total active loyalty customers, points balances (highest, lowest, average), number of VIP tiers and thresholds, active earning campaigns, active redemption rewards, and any scheduled expiry dates.

This audit becomes your reference document, and you’ll use it later to verify Yuko is configured identically before you go live.

Expected result: A written record of your full Smile.io program configuration, kept open in a separate tab throughout the migration.

Step 2: Export your customer data from Smile.io

Log into your Smile.io merchant dashboard and navigate to the customer export section. Then, download the full customer list as a CSV, including at minimum email address, points balance, VIP tier, and date joined.

If Smile.io offers a separate points-history export, then download that too, since it’s useful for auditing after import.

Expected result: One or more CSV files saved locally with all customer loyalty data.

Step 3: Clean and prepare your customer data

Raw exports often contain formatting issues that cause import errors, so clean the file before importing into Yuko. Specifically:

1. Open the CSV in a spreadsheet tool.
2. Remove any rows with blank email addresses.
3. Then, remove duplicate emails. Keep the row with the higher points balance.
4. Set any negative points balances to zero.
5. Standardize the points column as whole numbers.
6. Finally, confirm the VIP tier column uses consistent naming (“Gold,” not “gold” or “GOLD”).

Pro tip: Run your cleaned CSV through a free email validation tool, such as Hunter.io’s bulk verifier or NeverBounce, before importing it. Otherwise, invalid addresses can cause silent import failures. As a result, the row simply won’t match a Shopify customer and gets skipped without an obvious error.

Expected result: A clean CSV with one row per customer, valid emails, and whole-number balances.

Step 4: Set up your loyalty program in Yuko

Install Yuko from the Shopify App Store and complete onboarding. Before importing anything, configure your points label, conversion ratio, VIP tiers (matching Smile.io’s thresholds exactly), earning campaigns, and redemption rewards.

For instance, if Smile.io had tiers at $0, $200, and $500 lifetime spend, recreate those same thresholds in Yuko first. Learn more about how to set up a loyalty program in Yuko.

Expected result: A fully configured Yuko loyalty program mirroring your Smile.io setup, with no customers imported yet.

Step 5: Map Smile.io data to Yuko

Yuko’s customer import expects a specific CSV format, so you’ll need to map your Smile.io export columns to Yuko’s required fields:

Smile.io column	Yuko import field
email	email
points_balance	points
tier_name	vip_tier
first_name	first_name
last_name	last_name

Rename your CSV headers to match Yuko’s expected fields, and check Yuko’s import documentation at docs.yuko.so beforehand, since field names can change.

Expected result: A CSV with headers that match Yuko’s import format exactly.

Step 6: Import your customer points and loyalty data

Navigate to Apps > Yuko Loyalty > Loyalty > Customers and use the import function to upload your cleaned CSV. Once Yuko matches imported records to existing Shopify customers by email address, it credits the points balance and assigns the specified tier.

Watch the import log closely, since common issues at this stage include an email not found in Shopify, a non-whole-number points value, or a tier name that doesn’t match a configured Yuko tier. Fix any flagged rows and re-import them.

Expected result: All customers from your Smile.io export appear in Yuko with correct balances and tiers.

Also read: Best Email Marketing Apps for Shopify to connect your loyalty data to email campaigns after migration.

Step 7: Verify points, tiers, and customer records

After import, spot-check at least 10 customers across different tiers and points ranges: search for each in Yuko’s customer list, confirm their balance and tier match the export, and check that their activity feed shows the imported balance. Then verify your totals. The sum of all points in Yuko should match the sum in your Smile.io export.

A Yuko merchant with 4,200 loyalty customers completed the full migration in six hours, with data cleaning taking three of them. Their verification step caught 14 customers whose emails had changed since joining Smile.io, and those were corrected manually before go-live.

Expected result: Spot-checked customers have correct balances and tiers, and totals reconcile.

Step 8: Test earning and redemption before launch

Before switching customers over, test the full flow end-to-end with a test Shopify customer account:

• Place a test order and confirm points are awarded correctly
• Then, check the VIP multiplier applies for a non-base tier, redeem points for a discount
• Confirm if redeeming works at checkout
• Verify the floating launcher widget and account hub display correctly.

If you’re migrating referrals, then test that flow too by sharing a referral link, placing a qualifying order, and confirming both sides receive their reward. For better results, read our guide on referral programs for ecommerce .

Expected result: Every loyalty action works correctly before a single real customer sees the change.

Step 9: Switch your loyalty program from Smile.io to Yuko

Once testing is complete, it’s time to go live:

1. Disable Smile.io’s storefront widgets in your Shopify theme editor.
2. Enable Yuko’s storefront widgets , such as floating launcher, cart earn, cart redeem, and any others you’ve configured.
3. Activate Yuko’s email notifications.
4. Pause, but don’t uninstall Smile.io’s loyalty program, yet. Use it as a reference for 30 days.
5. Finally, send your customer communication email announcing the switch.

Expected result: Yuko widgets are live, Smile.io widgets are removed, and customers can earn and redeem through Yuko immediately.

With go-live complete, the next priority is making sure the points transfer itself held up under scrutiny. After all, this is where most migrations actually go wrong.

How to transfer Smile.io points to Yuko without errors

Here’s how to transfer Smile.io points to Yuko cleanly, since this step is where the majority of migration problems originate.

Matching customer records. Yuko matches imported customers to Shopify accounts by email. If a customer’s Smile.io email doesn’t match their Shopify account, that row fails to import. Cross-reference your export against your Shopify customer list beforehand, and fix mismatches by updating the file or crediting the customer manually afterward. Email changes after signup are a common cause of these mismatches, so don’t skip this check.

Verifying balances. Before and after the import, compare the total number of customers, total points issued, and top-tier customer counts between Smile.io and Yuko. The numbers should match. If they don’t, track down the discrepancy before going live.

Pro tip: Run a test import on five customers first. It takes two minutes and catches formatting issues before they touch your full list. So, pick customers from different tiers and point ranges to cover edge cases.

Avoiding duplicates and double-crediting. Two errors come up repeatedly: duplicate customers due to inconsistent email formatting, and double-crediting, which occurs when you import the same file twice (Yuko adds to existing balances rather than replacing them). Clean duplicates before importing, and test on one customer before running the full file.

What happens to your Smile.io rules after migration?

Earning rules and redemption rewards don’t transfer automatically. They stay in Smile.io and need to be rebuilt in Yuko. However, you can improve them by simplifying overly complex rules, adding earning actions Smile.io didn’t support (daily visits, anniversaries, reviews), automating expiry reminders and win-back campaigns, or connecting Yuko to Klaviyo for loyalty-based email segments.

Test your Yuko loyalty program before going live

Testing is non-negotiable, as a broken redemption flow discovered after launch costs you customer trust, while the same issue found during testing costs you nothing.

• Customer account and points tests: Log in as a test customer, confirm the floating launcher shows the correct balance, check the account hub displays balance, tier, and activity correctly, and manually credit 100 points to confirm the balance updates immediately.
• Reward redemption tests: Redeem a discount reward and confirm a valid Shopify discount code is issued, apply it at checkout to confirm the correct deduction, and check that the points balance decreases afterward.
• VIP tier and referral tests: Confirm a Gold-tier test customer earns at the correct multiplier, run a referral end-to-end across two test accounts, and then check that the tier progress bar updates after a purchase.
• Storefront and checkout tests: Visit your store as a logged-in customer to confirm the launcher appears on every page, and add items to the cart to confirm the cart earn widget is accurate. If you’re on Shopify Plus, then confirm the checkout earn widget appears.

Once every test passes, you’re genuinely ready to go live.

How to tell customers about your Smile.io to Yuko migration

Customers notice when their loyalty program changes, so a proactive communication plan helps prevent confusion and protect trust.

• Send an email before you switch, giving customers at least 5 to 7 days’ notice covering what’s changing, that their points are safe, what they need to do (usually nothing), and where to find their balance afterward.
• Update your loyalty landing page to reflect the new program name, earning rates, and redemption options.
• Add a site-wide banner or pop-up during the first week after launch to reach customers who missed the email.
• Brief your support team on the timeline, what changed, and how to look up a customer’s balance in Yuko.

In our experience, merchants who send a pre-migration email to their loyalty members see noticeably fewer loyalty-related support tickets in the first weeks after launch than merchants who make no announcement. Communicate early and clearly, and the switch becomes invisible to most customers.

Common Smile.io migration problems and how to fix them

Problem	Cause	Solution
Customers don’t appear in Yuko after import	Email in Smile.io export doesn’t match Shopify account email	Cross-reference both lists, correct the email, and re-import affected rows
Points balances are doubled after import	Import ran twice; Yuko added points on top of the existing balance	Find affected customers and manually debit the duplicate points with a reason note
VIP tier assignments are wrong after import	Tier name in CSV doesn’t exactly match the tier configured in Yuko	Fix capitalization or spacing in the CSV and re-import the tier column
Smile.io discount codes stopped working	Code expired or hit its usage limit in Shopify (not a migration issue)	Check code status in Shopify Admin > Discounts and reissue if needed
Yuko widgets aren’t showing on the storefront	Yuko Theme App Embed isn’t enabled	Go to Online Store > Themes > Customize > App Embeds and toggle “Yuko Loyalty” on

How long does it take to migrate from Smile.io?

The timeline depends primarily on the size of your customer base and how complex your current program is:

Store size	Estimated migration time
Under 1,000 loyalty customers	2 to 4 hours
1,000–10,000 customers	4 to 8 hours (spread over 1 to 2 days)
10,000+ customers	1 to 3 days (data cleaning takes longer)

These estimates cover export, cleaning, setup, import, and testing. They don’t include writing customer communication or updating your loyalty landing page, so budget a few extra hours for those.

In fact, data cleaning in Step 3 is almost always the most time-consuming part, since Smile.io exports can include formatting inconsistencies, duplicates, and customers who joined but never ordered.

A store with a few thousand loyalty customers can realistically finish in a single working day if the export is clean. Merchants who plan their migration with a documented checklist tend to complete the process noticeably faster than those who approach it ad hoc, which is exactly why the checklist below matters.

Smile.io to Yuko migration checklist

Before you start:

• Document your current Smile.io program (rules, tiers, rewards)
• Export as CSV: customer list with points balances, VIP tier assignments, pending referral rewards, and unredeemed discount codes
• Note your current earning rules, rewards, and tier thresholds

Yuko setup:

• Install Yuko from the Shopify App Store
• Configure points label and conversion ratio
• Create VIP tiers matching Smile.io thresholds
• Build earning campaigns and redemption rewards
• Enable Theme App Embed and place storefront widgets

Data migration:

• Clean CSV (remove blanks, duplicates, fix formatting)
• Map Smile.io columns to Yuko import fields
• Run a test import on 5–10 customers and verify results
• Run the full import and spot-check 10+ customers
• Verify total points sum matches the Smile.io export

Testing:

• Earning, VIP multiplier, and reward redemption
• Referral flow, if applicable
• Storefront widgets on desktop and mobile

Go-live:

• Remove Smile.io widgets and enable Yuko’s
• Activate Yuko email notifications
• Send your customer communication email and update your loyalty page
• Brief support team and keep Smile.io installed (not uninstalled) for 30 days

Conclusion

Ultimately, a Smile.io migration is a structured process, not a risky leap. Export your data carefully, clean it before importing, configure Yuko to mirror your existing program, and test everything before going live, and your customers keep their points, their tiers stay intact, and the switch becomes invisible to anyone who doesn’t read your announcement email.

The migration itself takes a few hours for most stores. In return, you get a customer loyalty software platform that combines points, VIP tiers, referrals, memberships, and workflow automation in one place, without the cost of stitching together multiple apps.

Your 6-step launch checklist:

1. Export and clean your Smile.io customer data
2. Set up Yuko with matching tiers, earning rules, and rewards
3. Import customer points and verify balances
4. Test earning, redemption, and widgets end-to-end
5. Remove Smile.io widgets and go live with Yuko
6. Send your customer communication and update your loyalty page

Related Reading

• Migrate From Judge Me
• How to migrate reviews from Junip
• Migrate from Loox

FAQs