Table of Contents
Most "tech stack consolidation" content is written for an executive approving a budget. This one is written for the operator who has to actually do the migration next Tuesday. The difference is real file names, real Klaviyo property changes, and a realistic accounting of the support tickets you'll see on go-live day.
Migrating from Yotpo Loyalty to Skio takes 2 to 4 weeks and requires data export, tier and reward mapping, customer communication, and parallel testing before cutover.
The reason supplements brands consolidate is the same reason any operator does: running loyalty and subscriptions as separate vendors means two support queues, two data exports, two logins, and two places for things to silently fall out of sync. Pulling loyalty into the same platform that runs subscriptions removes a whole category of operational drag.
Why Supplements Brands Consolidate
The average DTC brand juggles 8 to 12 tools across subscriptions, loyalty, email, SMS, reviews, and referrals. A separate loyalty app plus a separate subscription tool means two vendor relationships and two sets of data that have to agree with each other. Folding subscriptions, loyalty, and referrals into one platform means one login, one support team, and unified analytics. Tech stack consolidation means replacing multiple tools with one platform that handles subscriptions, loyalty, and referrals without data silos.
What Actually Moves When You Migrate
Not everything transfers, and knowing the difference up front prevents go-live surprises.
Data type | Moves how | Notes |
|---|---|---|
Customer point balances | CSV export from Yotpo | Maps to Skio credits |
Tier assignments | Manual mapping | VIP levels map to Skio tiers |
Redemption history | Optional | Most brands start fresh |
Referral links | Regenerated | Old Yotpo links break |
Reward catalog | Rebuilt | Discounts, free products, perks |
Loyalty platform migration transfers customer points, tier status, and reward rules via CSV export and API sync. The one thing to flag loudly: referral links don't carry over, so plan a one-time email to reissue them.
Pre-Migration Checklist (Week 1)
Week 1 is documentation, not setup. Export the full customer points ledger from Yotpo (Admin, then Customers, then Export). Document current tier thresholds, for example 500 points equals Silver. Screenshot every active reward in the Yotpo catalog. Audit which Klaviyo flows reference Yotpo properties like tier_name and points_balance. Identify custom integrations, Gorgias macros, Zendesk apps, Shopify Flow automations. Then set an internal cutover date, ideally mid-month, away from BFCM and holiday peaks.
Mapping Tiers and Rewards (Week 2)
The biggest conceptual shift is points to credits. Skio uses credits where 1 credit equals $1 by default, which is simpler for customers than an arbitrary points system that needs conversion math. If 100 Yotpo points equaled $5 off, that becomes 5 Skio credits.
Tiers map directly: Yotpo VIP levels become Skio Bronze, Silver, Gold, with customizable names. Most reward types translate cleanly, percentage discounts, fixed-amount discounts, free shipping. A few need workarounds: free products use Skio's product-based rewards, and early access uses custom embedded blocks. The referral program maps from Yotpo's advocate/friend structure to Skio's give-get model. Skio uses credits where 1 credit equals $1 by default, compared to Yotpo's points system that requires conversion math.
Setting Up Skio Loyalty (Weeks 2 to 3)
With the mapping documented, build it out. Configure tier thresholds in the Skio dashboard under Loyalty, then Tiers. Build the reward catalog to match your Yotpo perks. Set credit earning rules: purchase earns X credits, referral earns Y, subscription renewal earns Z. Enable the referral program with your advocate/friend rewards. Install the Skio Loyalty portal blocks in Customer Portal v3. Add the credit redemption block to Shopify Checkout, which requires Checkout Extensibility.
Importing Customer Data
Skio accepts CSV uploads for bulk credit assignment; contact support for the import template. The required columns are customer_email, credit_balance, and tier_name. Run the import about 48 hours before go-live to minimize discrepancies. Skio auto-matches customers by email, so the email must match the Shopify customer record exactly, and tier assignment happens automatically based on the credit thresholds you set. Test with 10 to 20 records first before the full import.
Updating Klaviyo Flows
This is the technical heart of the migration, and it's where a missed property quietly breaks an email flow. Yotpo sends loyalty events to Klaviyo (Points Earned, Tier Upgraded, Reward Unlocked). Skio sends equivalent events with different property names (integrating Skio Loyalty events in Klaviyo). Update your flow filters: Yotpo's tier_name becomes Skio's loyalty_tier. Update email copy from "points" to "credits," unless "points" is your brand language and you want to keep it. Skio's loyalty events are Credit Earned, Credit Redeemed, Tier Achieved, and Referral Completed. Test every flow in Klaviyo preview mode before enabling. The main technical tasks are updating Klaviyo flow properties, adding the Skio Checkout block, and removing Yotpo theme code, and most operators can handle this without developer help.
Customer Communication
Most customers won't notice the switch if you keep reward values equivalent, which is the goal. Send one email about a week before: "We're upgrading our rewards program." The key message is reassurance, your points are safe, same perks, better experience. Include an FAQ answering "how do I check my new balance" with a portal link (Loyalty Customer Portal settings). After launch, send a "your new rewards dashboard is live" email with a short tutorial. Prep your CX team with Gorgias or Zendesk macros for the predictable questions: where are my points, how do I redeem.
Parallel Testing (Week 3)
Run Yotpo and Skio side by side for 3 to 5 days, with Yotpo in read-only mode if possible. Test credit earning by placing a test subscription order and confirming credits appear in Skio. Test redemption by applying a credit discount at checkout. Test the referral flow end to end: generate a link, complete a friend purchase, confirm both sides get credits. Check Klaviyo event delivery by triggering a Skio loyalty event and confirming the flow fires. Verify the customer portal shows the correct tier and balance.
Go-Live and Yotpo Deprecation
On go-live day, disable the Yotpo Loyalty app in Shopify but don't uninstall it yet, you want it for data access. Remove Yotpo widgets from the theme (the loyalty launcher, points display on the account page). Enable Skio Loyalty in Customer Portal v3. Monitor the support queue for 48 hours and expect a 10 to 15% uptick in "where are my points" tickets. Have CX link customers straight to the new rewards page with their balance. About a week after launch, uninstall the Yotpo app and cancel the subscription.
What Breaks and How to Fix It
Issue | Fix |
|---|---|
Customers can't find loyalty dashboard | Prominent link in post-purchase email and account banner |
Klaviyo flow not triggering | Check event name spelling (case-sensitive); confirm OAuth connection |
Credits not applying at checkout | Ensure Checkout Extensibility is on and the redemption block is published |
Referral links not generating | Confirm referral program is toggled on in Skio Loyalty |
Tier displaying wrong | Re-import customer data with the correct |
Measuring Success
Track credit redemption rate, aiming for 25 to 40% of customers with credits redeeming within 90 days. Monitor referral conversion, which tends to run higher on Skio because referrals are tied directly to subscriptions. Compare loyalty-related support ticket volume, which should drop meaningfully after consolidation. Check subscription retention by tier, where top-tier members should show lower churn. And count the hours saved running one dashboard instead of two (Loyalty Analytics: Tiers).
FAQ
How long does a Yotpo to Skio Loyalty migration take?
2 to 4 weeks total: about a week for export and mapping, one to two weeks for setup and testing, 3 to 5 days of parallel testing, then go-live.
Will customers lose their points?
No. You export points from Yotpo as a CSV and import equivalent credits into Skio. Customers keep their balances and tier status.
Can I run Yotpo and Skio Loyalty at the same time?
For testing, yes, but not long-term, two loyalty dashboards confuse customers. Use parallel testing for 3 to 5 days max.
Do I need a developer?
Minimal dev work. The main tasks are Klaviyo property updates, adding the Skio Checkout block, and removing Yotpo theme code. Most operators handle it.
What happens to my Yotpo referral links?
They break. Generate new Skio referral links and send customers a one-time email with their updated link.
How do Skio credits compare to Yotpo points?
Skio uses 1 credit equals $1 by default, which is simpler for customers. Convert Yotpo points by dividing by your points-to-dollar ratio.
The Bottom Line
Loyalty migration isn't the nightmare the two-vendor status quo makes it feel like. Document the mapping, run the import 48 hours early, update your Klaviyo properties, and test in parallel before cutover. Do that and customers keep their balances, your CX team keeps its sanity, and you're running one platform instead of two.
