Yotpo Loyalty Migration from Smile.io: 7 Things That Don’t Transfer

Four Shopify stores moved off Smile.io to Yotpo Loyalty in the first 90 days of 2026. Sizes ranged from $80K to $310K MRR. Three did it because Yotpo Reviews was already in their stack, one because the SMS-loyalty story still sells well to founders even after Yotpo deprecated its own SMS product in December 2025. None of the migrations were ugly. All of them had the same seven things that didn’t carry over cleanly.

This is the operator’s notebook on what gets built fresh and the order to do it in. If you’re still trying to decide between platforms first, the data we have on that question is in Smile vs Yotpo — 90 days of Shopify data.

1. Points balances — partial transfer, not API sync

There is no live points sync between the two apps. Smile gives you a CSV with customer email, current points balance, and lifetime points earned. Yotpo Pro and Premium plans have a migration team that bulk-loads that CSV. On the Free plan or if you’re self-serving, you import it yourself through the admin import tool.

The trap: Smile records two numbers per customer (current balance and lifetime), Yotpo wants three (current balance, lifetime earned, lifetime redeemed). The third gets reconstructed from order-history if you don’t pre-compute it. Customers don’t notice, but if your VIP tiers are based on lifetime spend and your CSV is missing redemption history, anyone who has cashed out a lot looks lower-tier than they are.

The fix is one extra column in your export. We pull lifetime redeemed from Smile’s rewards-redeemed report and merge it into the points CSV before handing it to Yotpo. Half a day of work that prevents a week of support tickets.

2. VIP tier history — the names don’t match

Smile.io ships with three tier names by default: Member, VIP, Elite. Yotpo asks you to name them yourself. If you import the Smile customer file before you’ve created tiers in Yotpo, the import either errors out or assigns everyone to the lowest tier silently. We’ve had it happen both ways depending on which Yotpo admin tool you use.

The order matters: build the tiers in Yotpo first, name them identically to Smile (or to whatever your customers see in your branded program page), then import the customer file with a tier column matching the new names. Then run Yotpo’s tier-recalculation so anyone whose lifetime spend has changed since their last Smile-tier assignment lands in the right bucket on day one.

The whole exercise takes under an hour if you do it in the right order. It takes a day and a service-desk apology email if you don’t.

3. Referral codes — the lookup table is not portable

Smile and Yotpo both generate per-customer referral codes. They use different formats and different uniqueness rules. A customer’s old Smile code stops working on day-one of the migration whether you announce it or not, because Smile’s referral webhook is now disconnected.

Two paths. The fast one: let old Smile referral codes die quietly, generate Yotpo codes for everyone, and announce in the migration email that codes have been refreshed. Most stores lose under 10% of in-flight referrals doing this. The careful one: export the active Smile codes, import them as static promo codes in Shopify with a 14-day expiry, and give people a clean window to redeem before they’re replaced. We’ve done both and the careful path saved one store about $1,800 in expected referral signups that would have churned on a broken code.

4. Email triggers and automations — zero transfer, expect a rebuild

Smile’s email layer (welcome, points-earned, points-expiring, redemption available, VIP tier-up) is rebuilt from scratch in Yotpo. The mechanics are similar but the trigger names, conditional logic, and template editors are different products entirely. None of the copy carries.

Where this gets expensive: stores that had spent six months tuning Smile email subject lines find themselves rewriting from a blank template. The right play is to export Smile email metrics first (open rates, click-through rates, redemption-from-email), pick the top five performers, port the copy and subject lines into Yotpo, and let everything else rebuild on Yotpo defaults. We don’t try to recreate every Smile flow on the new platform — it’s wasted effort if the Yotpo template is meaningfully different.

Build the points-earned and redemption-available emails first. They drive the time-to- first-redemption number, and that’s the lagging indicator your CFO will track on whether the migration paid off.

5. Branded UI — Smile’s CSS doesn’t move

Smile lets you push a fair amount of CSS into the on-site widget and the rewards page. Yotpo gives you more out-of-the-box customization but the CSS overrides don’t carry over. Anyone who handed Smile to a designer for a custom look is rebuilding it.

The good news: Yotpo’s branded program page is a richer template than Smile’s, which means most of the design work that took custom CSS in Smile is configurable in Yotpo without code. We’ve had three out of four migrations come out with a better program page than the Smile original. The fourth was a heavily-styled Shopify Plus theme where the designer wanted exact pixel parity — that one took two days of CSS.

Plan a half-day of branded-page setup. Have your hex codes, font names, and any logo files ready before you start.

6. SMS opt-ins — TCPA re-consent gotcha

This is the one that catches people. Yotpo deprecated Yotpo SMS in December 2025. If your Smile install was talking to a separate SMS app (Postscript, Klaviyo SMS, Attentive), the SMS subscriber list itself is fine — it lives in the SMS app, not in Smile. The migration doesn’t touch it.

But if you’re building net-new SMS automations in Yotpo Loyalty post-migration that weren’t running before, anyone receiving them is, technically, a new subscriber under TCPA. You need explicit consent for the new sender, even if it’s the same store. The clean way: a single “we moved our loyalty SMS to Yotpo, opt back in here” message before any automated point-balance reminder fires. The dirty way: assume implicit consent and hope no one complains. We’ve seen one store get a TCPA letter on a post-migration broadcast. The cost of the cure was small. The cost of the disease wasn’t.

7. The 14-day customer-comms cutover

The biggest single variable on whether a migration goes quiet or loud is the customer comms. We use a three-email arc, day -7, day 0, day +3.

Day -7: “We’re upgrading our rewards program. Your points are safe, your VIP tier is safe, here’s what’s changing.” Three bullets. No marketing copy. The CTR on this email predicts whether the rest of the migration is calm or noisy.

Day 0: “Your rewards account just moved. Log in here, your points balance is X.” One link. The link goes to the Yotpo branded rewards page, with the customer’s Shopify session pre-authenticated.

Day +3: “Two new things you can do with your points.” Anchor on what got better. New redemption tiers, new VIP perks, anything Yotpo has that Smile didn’t. This is the email that drives the first wave of redemptions on the new platform and gives you clean attribution for the migration’s lift.

Average open rate across the four migrations: 38% on day -7, 51% on day 0, 22% on day +3. The day-0 number is the one to chase. People want to confirm their balance is intact.

The pre-migration checklist we run before kickoff

Before the rebuild week starts, we get six exports from Smile and two snapshots from Yotpo. Without these, day five is a panic.

Smile customer points export (with lifetime redeemed merged in).
Smile VIP tier roster (current tier per customer, last assigned date).
Smile active referral code list (only codes used in last 90 days).
Smile email-performance pull (open + click + redemption-attribution by template).
Smile rewards-redeemed report (last 12 months).
Smile branding kit screenshots (widget, program page, redemption screen).
Yotpo program-design draft (tier names, points-per-dollar, sign-up bonus).
Yotpo email-template draft (subject lines, copy, send timing).

Cost math: when the migration is worth it

Smile Growth and Yotpo Pro both sit at $199/mo. Same headline price. The migration question is rarely about the loyalty bill itself — it’s about whether consolidating reviews + loyalty on one vendor saves more than it costs.

Stores already on Yotpo Reviews: migration usually pays for itself in a single quarter. Stack consolidation, one dashboard, one CSM at the Premium tier, and the loyalty side now feeds Yotpo’s reviews-with-points incentive flow that Smile can’t plug into.

Stores on Loox or Judge.me for reviews: the migration math is harder to defend. You’re paying $199 for Yotpo Loyalty when Smile Growth would cost the same and your review tool already works. Don’t move just because Yotpo’s sales team asked.

Below $50K MRR: don’t do this migration. Run the numbers in our loyalty ROI calculator first — most stores at that size don’t have the repeat-purchase volume to justify the disruption.

What the four 2026 migrations cost

We charged a flat $1,400 per store. That covered the Yotpo build, the customer-comms sequence, branded-page rebuild, and 14 days of post-launch support. Three of the four owners did the Smile decommission themselves. The fourth had us shut Smile down on day +14 for an extra $200.

On the cost-savings side: the two stores moving from Smile Growth ($199) to Yotpo Pro ($199) were a wash on subscription cost. The savings were entirely in operational time — one dashboard for reviews + loyalty saved their merchandiser about three hours a week, which the owners valued at more than the migration cost in under three months.

Frequently asked

Do points balances transfer from Smile.io to Yotpo Loyalty?

Not via API. You export the balances CSV from Smile, hand it to Yotpo’s migration team during onboarding (Pro plan and up), and they bulk-load. Free and Starter customers without a CSM bulk-import the CSV themselves through Yotpo’s admin. Either way the platform doing the work is Yotpo, not a sync.

Will customers lose their VIP tier when we switch?

They lose the tier name unless you redefine it in Yotpo first. Smile uses Member / VIP / Elite by default. Yotpo asks you to name them whatever you want. We mirror the names, then run a tier-recalculation pass in Yotpo so anyone who would currently qualify gets re-bucketed by points or annual spend, not just by the row that came over.

How long does a Smile to Yotpo migration take?

On a typical Shopify store doing under $200K/month: 14 days. Days 1–3 export and audit. Days 4–7 Yotpo build (rules, tiers, branding, emails). Days 8–10 customer-comms script + soft-launch to a 10% sample. Days 11–14 full cutover and Smile decommission. Larger stores or anyone with subscription-billing integrations should plan 21–30 days.

Will Smile customers get a re-subscribe or re-consent email?

Email-marketing consent does carry from Shopify customer records, so Klaviyo or Mailchimp keeps working. Where you do need fresh consent: SMS, if you were running Smile alongside an SMS app and want Yotpo to talk to subscribers directly. TCPA in the US (and CASL in Canada) treats a platform change as new collection.

Can we do the migration without a Yotpo account manager?

Free and Pro plans don’t include a CSM. You can self-migrate by exporting the Smile CSV, building the Yotpo program, then importing through admin. The friction is rebuilding the email triggers and the branded UI from scratch. Plan two weekends of focused work or pay for the Premium plan ($799/mo) where the CSM owns the rebuild.

What does Yotpo Loyalty actually cost in 2026?

Free up to 100 orders/month. Pro $199/mo for up to 500 orders, plus $0.20 per order over the cap. Premium $799/mo for up to 3,000 orders. Smile is $49 Starter, $199 Growth, $599 Pro. The cost-equivalent move is Smile Growth to Yotpo Pro at $199 each — Yotpo’s overage and order-cap structure is what catches operators on the way up.

Should small Shopify stores even bother migrating?

No. Under $50K MRR neither platform moved repeat-purchase in our 8-store test. The migration is a real cost and a real risk to existing members. The strongest reason to migrate is that you also want Yotpo Reviews on the same dashboard. If you don’t, stay on Smile and revisit at $80K MRR.

How we verified this

Pricing verified against smile.io/pricing and yotpo.com/pricing on 2026-05-01. Yotpo SMS deprecation date confirmed via Yotpo product release notes (December 2025). Yotpo overage pattern ($0.20/order) confirmed via Capterra and ProPicked 2026 listings plus operator quotes from active deployments.

Sources

Smile.io Pricing (verified 2026-05-01)
Yotpo Pricing (verified 2026-05-01)
Yotpo — Loyalty & Referrals: Migrating Platforms
Smile.io — 4 Steps for a Loyalty Program Migration
ProPicked — Yotpo Loyalty Pricing 2026