Switching from Smile.io to Roadmap: A Complete Migration Guide

Switching from Smile.io to Roadmap: A Complete Migration Guide
April 5, 2026
•
5 min read

If you're running Smile.io and starting to feel the limits — paying for loyalty in one place, reviews in another, subscriptions somewhere else — you've probably wondered whether consolidating makes sense. This guide covers exactly what's involved in migrating from Smile.io to Roadmap, what data moves, what needs reconfiguring, and how to make the switch without disrupting your customers or losing a single point balance.

We've helped brands through this migration more times than we can count. Here's what the process actually looks like, from the moment you decide to move through to verifying success on the other side.

Why Brands Switch from Smile.io to Roadmap

Smile.io is a solid loyalty app. It does one thing — loyalty programs — and it does it competently. But as brands grow, the cracks in a loyalty-only tool start to show. The most common reasons brands evaluate moving off Smile.io aren't about loyalty itself. They're about everything around it.

  • App stack sprawl: Smile.io handles loyalty, but you still need a separate reviews app (Judge.me, Okendo, Loox), a separate subscriptions app (Recharge, Skio, Loop), and often a separate discounts tool. That's four apps, four billing relationships, four Klaviyo integrations, and four support contacts. When something goes wrong, you're playing pass-the-parcel between support teams who all point at each other.
  • Fragmented customer data: Your loyalty data lives in Smile.io. Your review data lives in Okendo. Your subscription data lives in Recharge. None of these systems talk to each other natively. A customer who subscribes, leaves reviews, and earns loyalty points is three separate profiles across three separate tools. You can't see the full picture in one place, and neither can your team.
  • Klaviyo integration complexity: Each app sends events to Klaviyo independently, with different schemas, different customer identifiers, and different event naming conventions. Building flows that reference loyalty status, review activity, and subscription behaviour means stitching together data from three sources — and every time one of those apps updates their integration, you're rebuilding something.
  • Rising costs at scale: Smile.io's active member pricing means your bill grows as your loyalty program succeeds. Add Okendo at $99–199/month and Recharge at $99/month plus transaction fees, and you're looking at $400–800+/month across three tools. That's before you factor in the developer time needed to keep integrations working.
  • POS limitations: Smile.io's in-store loyalty capabilities are limited. Brands with physical retail often find that online and offline loyalty experiences don't connect properly — customers who buy in-store expect their points to show up online, and they're not wrong to expect that.
  • B2B gaps: If you sell wholesale, Smile.io doesn't cover trade accounts. That's yet another tool to manage, yet another integration to maintain.

Roadmap replaces this entire stack. Loyalty, reviews, subscriptions, discounts, B2B wholesale, POS, and Klaviyo — all on one platform, sharing one customer data layer. That's the core reason brands make the move.

Pre-Migration Checklist

Before you do anything else, get this list sorted. Brands that skip this step end up discovering mid-migration that they've missed something important. Thirty minutes of preparation saves days of cleanup.

Audit your current Smile.io setup

  • Document your current points earn rate (points per dollar/pound spent)
  • List all your VIP tier names, thresholds, and the specific benefits at each tier
  • Document all earn actions (purchases, reviews, referrals, birthdays, social follows, account creation)
  • List all active reward options and their redemption values
  • Note whether you have points expiry enabled and the timeframe
  • Check if you have referral programme active and what the referrer/referee reward split is
  • List all Klaviyo flows currently triggered by Smile.io events
  • Identify all locations where Smile.io widgets appear in your theme

Understand your data volume

  • Total number of loyalty members with a non-zero point balance
  • Number of active VIP tier members by tier
  • Number of active referral links in circulation
  • Any customers with unusually high balances that need manual verification

Choose your migration window

  • Avoid Black Friday, Cyber Monday, and Christmas trading periods
  • Avoid major planned sales or promotional periods
  • Choose a Tuesday–Thursday window — lower traffic than Monday/Friday, easier to get support if needed
  • Confirm your development/marketing team has capacity during the migration week

Prepare your communications

  • Draft your loyalty member email (more on this below)
  • Update any loyalty-related content in your email templates
  • Check your FAQ or help pages for any Smile.io-specific references that will need updating

What You're Moving: The Migration Inventory

Before switching, get clear on exactly what needs to move. This isn't just about transferring point balances — it's about understanding the full scope of what you'll be configuring in Roadmap and what our team handles for you.

Customer Data (Migrated by Roadmap Team)

Data Type Migrates? Notes
Customer point balances Yes — full transfer Every customer's current balance is imported
VIP tier status Yes — full transfer Tier membership maps to equivalent Roadmap tiers
Referral history (completed) Yes Historical referral completions are preserved
Active referral links Yes Links remain active and tracked post-migration
Pending referral rewards Yes Flagged for manual review during import
Full activity history Partial Summary-level history; granular transaction log varies
Reviews data Conditional If migrating from Judge.me/Okendo simultaneously, reviews transfer

Program Configuration (Rebuilt in Roadmap)

These elements don't "migrate" in the traditional sense — they're rebuilt in Roadmap's admin to match or improve your current setup. This is actually an advantage: it's the perfect moment to fix anything that wasn't quite right in your Smile.io configuration.

  • Loyalty earn rules: Points earn rate, bonus earn events, earn multipliers for VIP tiers, category-specific earn rates if applicable
  • VIP tier thresholds: Spend or points required to reach each level, plus the specific benefits at each tier
  • Reward catalogue: Discount codes, free shipping thresholds, free products, percentage-off rewards, exclusive access rewards
  • Non-purchase earn actions: Review submissions, referrals, birthday rewards, social follows, account creation
  • Widget placement and styling: Where your loyalty widget appears and how it's branded to match your store
  • Klaviyo event triggers: Which loyalty events fire into Klaviyo and what flows they feed
  • Points expiry rules: If you run expiry, these are configured to match your current setup

Additional Modules You Can Activate in Roadmap

Migrating from Smile.io is also the ideal time to consolidate other tools you're currently running separately. You don't have to do this on day one — but it's worth planning for.

  • Product reviews module: Replace Judge.me, Okendo, or Loox. Review submissions earn loyalty points natively, without any integration work — because they're on the same platform.
  • Subscriptions module: Replace Recharge or Skio, with subscriber tenure and subscription value automatically feeding into tier logic.
  • B2B wholesale module: Trade account management and wholesale pricing if you sell to business customers.
  • POS integration: Connect in-store loyalty to online so physical store purchases earn and redeem the same points.
  • Unified Klaviyo integration: All modules — loyalty, reviews, subscriptions — send events through one integration with consistent schemas and customer identifiers.

Timeline Expectations

Most Smile.io to Roadmap migrations are complete within two weeks from kickoff to go-live. Here's how that typically breaks down:

Phase What Happens Duration
Kickoff and audit Roadmap team reviews your current Smile.io setup, documents requirements Day 1–2
Data export Export customer data from Smile.io; Roadmap team receives and processes Day 2–3
Roadmap configuration Loyalty rules, tiers, rewards, earn actions all built in Roadmap Day 3–6
Data import Customer balances and tier status imported into Roadmap Day 4–5 (runs parallel to config)
Widget replacement Smile.io widgets removed; Roadmap widgets installed and styled Day 5–7
Klaviyo reconnection Existing Klaviyo flows updated to trigger from Roadmap events Day 6–8
Testing Full end-to-end testing: earn, redeem, tier logic, Klaviyo events Day 8–10
Go-live Smile.io deactivated; Roadmap goes live; customer communication sent Day 10–14

For larger programmes with tens of thousands of loyalty members or complex tier structures, add a few extra days for data validation. For simpler setups, the whole thing can be done in a week.

The Migration Process: Step by Step

Step 1: Export Your Smile.io Data

Smile.io allows export of customer point balances and tier data through their admin dashboard. Before you start configuring anything in Roadmap, export a clean CSV with the following fields:

  • Customer email address (this is the primary identifier used to match records)
  • Current point balance
  • Current tier status
  • Points earned lifetime (if available)
  • Referral data — active referral links, completed referrals, any pending rewards

Do this export before you deactivate Smile.io. You want a complete snapshot of your loyalty programme state at the moment of transition. Run this export during a low-traffic period. You want to minimise the gap between export and import — any points earned by customers between export and import would need manual reconciliation. Early morning on a weekday typically works well.

Save the export files somewhere accessible and share them directly with the Roadmap onboarding team. They handle the import, not you.

Step 2: Configure Roadmap Loyalty

The Roadmap team sets up your loyalty programme configuration based on the audit from Step 1 of the kickoff. This covers:

  • Earn rules: Your points-per-dollar rate, any bonus multipliers for VIP tiers, different earn rates by product category if applicable. If you want to change your earn rate during the migration, now's the time.
  • Tier thresholds: Your VIP tier names, the spend or points required for each level, and the specific benefits at each tier — discount percentages, early access windows, free shipping thresholds, dedicated support, exclusive product access.
  • Reward options: Percentage discounts, fixed-amount discounts, free shipping, free products, exclusive access rewards. Add anything you wanted in Smile.io but couldn't configure.
  • Earn actions: Non-purchase earn events — review submissions, referrals, birthdays, account creation, social follows. In Roadmap, if you activate the reviews module, review-earn becomes native rather than an integration.

This is also the right time to improve your programme. Most brands switching from Smile.io take the opportunity to refine their tier structure, add more compelling tier benefits, or adjust earn rates based on what they've learned from running the programme. Don't feel locked into replicating your Smile.io setup exactly — replicate what worked, improve what didn't.

Step 3: Import Customer Balances

The Roadmap onboarding team handles the data import. They match customer records by email address and apply historical balances, so customers see their existing points reflected in Roadmap from day one.

What happens during import:

  • Point balances are mapped to each customer's Shopify account by email match
  • Tier status is applied based on either historical spend or imported tier data from Smile.io
  • Customers who were Gold tier in Smile.io land in the equivalent Roadmap tier
  • Active referral links are preserved so existing referrers don't lose their links
  • Pending referral rewards are flagged for manual review before going live
  • Any discrepancies or unmatched records are flagged and reviewed before the import completes

The import typically takes 24–48 hours depending on the size of your customer base. During this period, you can continue running Smile.io — the switch happens when you're ready to go live, not when the import runs. The two processes run in parallel.

Step 4: Replace Widgets

Smile.io's loyalty widget needs to be swapped out for Roadmap's equivalent. This is a theme edit — removing the Smile.io widget code and placing Roadmap's widgets in the correct positions.

Key placements to update:

  • Customer account page: Loyalty balance, tier status, available rewards, points history. This is the most important placement — it's where engaged customers go to check their status.
  • Product pages: Points earn indication ("Earn 50 points with this purchase"). This is a conversion driver — customers with points are more likely to buy when they can see what they'll earn.
  • Cart or checkout page: Points redemption option, available rewards display. Make it easy for customers to redeem at the moment of purchase.
  • Standalone rewards page: If you have a dedicated /rewards or /loyalty page, this needs to pull from Roadmap instead of Smile.io. Update any navigation links pointing to it.
  • Floating widget: The persistent loyalty widget that appears across your store. This is often the most visible placement — make sure styling matches your brand before going live.

Roadmap's widgets are built with premium brands in mind. Most brands find the visual quality improves compared to Smile.io's default widget styling. The Roadmap team customises colours, fonts, and positioning during onboarding — you don't have to do this yourself.

Step 5: Reconnect Klaviyo

This is where the consolidation benefit becomes most tangible. Klaviyo flows currently triggered by Smile.io loyalty events need to be updated to trigger from Roadmap events instead. Roadmap fires equivalent events with detailed properties.

Event Type Smile.io Event Name Roadmap Event Name
Points earned smile/points_earned Roadmap Points Earned
Tier upgrade smile/tier_changed Roadmap Tier Changed
Reward redeemed smile/reward_redeemed Roadmap Reward Redeemed
Referral completed smile/referral_completed Roadmap Referral Completed
Points expiry warning smile/points_expiring Roadmap Points Expiring
Reward created (for member) smile/reward_created Roadmap Reward Created
VIP tier downgrade smile/tier_changed (downgrade) Roadmap Tier Changed (downgrade property)

Common Klaviyo flows to update during migration:

  • Points earned after purchase: Update trigger from Smile.io event to Roadmap event. The event properties are equivalent, so flow logic should mostly carry over.
  • Tier upgrade notification: Update trigger and consider enriching the flow with additional Roadmap data — review count, subscription status — now that they're on the same platform.
  • Points expiry reminder: If you run points expiration, update the trigger source and verify the expiry date property name in the new event.
  • Reward redemption confirmation: Update trigger and flow content. Consider adding a "use your reward" prompt if you don't already have one.
  • Referral invite and reward: Update triggers for both the referrer and the referred customer flows.
  • Welcome series loyalty mention: If your welcome series references Smile.io or uses Smile.io-specific event data to personalise, update these references.

If you're also activating Roadmap's reviews or subscriptions modules, configure those Klaviyo events at the same time. Having all retention events arrive through one integration — with consistent customer identification — is one of the biggest operational wins of the whole migration. One customer ID, one event schema, one place to look when something isn't firing.

Step 6: Test Before Going Live

Before deactivating Smile.io, run a structured testing phase. Don't skip this. Most migration hiccups are caught here rather than discovered by customers.

  • Verify point balances match for a sample of customers — check high-value members, recently active members, and dormant members
  • Test the full earn-and-redeem flow: make a test purchase, earn points, redeem a reward, confirm the discount applies correctly
  • Confirm Klaviyo events are firing with the right properties — check event properties against what your flows expect
  • Check widget display across desktop, mobile, and tablet on your key landing pages
  • Test tier logic — create test accounts at each tier threshold and verify that tier benefits and earn rates apply correctly
  • Test referral flow end-to-end if you run an active referral programme
  • Verify points earn for any non-purchase actions you've configured (reviews, account creation, birthday, social)
  • Check that your standalone loyalty/rewards page displays correctly and that navigation links are working

Run this testing with someone from your team who uses the store as a customer would — not just a developer looking at the backend. The customer-facing experience is what matters.

Step 7: Go Live and Deactivate Smile.io

When testing is complete and you're confident everything is working:

  1. Send your customer communication email (see below) — or schedule it to send the morning you go live
  2. Set Roadmap to active/live status
  3. Deactivate Smile.io (don't delete it yet — wait 30 days in case you need to reference any historical data)
  4. Monitor customer support for the first 48 hours — the vast majority of queries, if any, will be customers checking that their points transferred
  5. Confirm with your team that all Klaviyo flows are triggering as expected in the first 24 hours of live traffic

Customer Communication Strategy

Your active loyalty members should hear about the change before — or at the same time as — they encounter it. Get this right and most customers won't notice the transition. Get it wrong and your support inbox fills up with "where did my points go?"

What to communicate

Keep it to three things:

  1. The transition is happening: "We've upgraded our loyalty platform to give you a better experience." You don't need to name Smile.io or Roadmap — customers don't care about the technology, they care about their rewards.
  2. Their points are safe: Say this explicitly. "Your point balance and tier status have been fully transferred." This is the only thing most loyalty members actually want to know.
  3. What's improved: Highlight one or two concrete improvements relevant to your customers. Better rewards page, earning points for reviews, in-store points if you have retail, a new rewards option they didn't have before.

Timing

Send the email the day of go-live or the day before. Don't send it a week in advance — that just gives customers seven days to worry about it before anything has actually changed. Don't send it after go-live without first making sure everything is working.

Tone

Keep it short. One email. This isn't a major announcement — it's a reassurance. Customers who are active loyalty members care about their points. Write to that concern directly, confirm it's handled, and show them something positive. Don't over-communicate or turn this into a big deal. It isn't one.

What not to do

  • Don't mention the names of the apps involved — customers don't need that level of detail
  • Don't send multiple emails building anticipation for the transition
  • Don't send a follow-up email after go-live unless there was a specific issue
  • Don't use the email as a marketing moment — it should feel like a service update, not a campaign

Customer support prep

Brief your customer support team before go-live. Give them:

  • A clear answer to "where are my points?" — "Your points transferred in full. Log in at [account page link] to see your balance."
  • A way to look up customer balances in Roadmap's admin so they can verify on the spot
  • Awareness of any known edge cases from the import (e.g., customers who had points that needed manual reconciliation)

Common Migration Concerns Addressed

Will customers lose their points?

No. Every customer's point balance is imported in full before Roadmap goes live. Customers land on the same balance they had in Smile.io. The import is validated before go-live — any discrepancies are caught and resolved during testing, not discovered by customers.

Will my VIP tier members lose their status?

No. Tier status is imported as part of the migration. Customers who were Gold tier in Smile.io land in the equivalent Roadmap tier from day one. Tier benefits carry over because you configure them to match during setup.

Will my reviews transfer?

If you're migrating your reviews platform at the same time (from Judge.me, Okendo, or Loox), yes — reviews can be transferred. If you're keeping your existing reviews app and only migrating loyalty, your review data stays where it is. The Roadmap team will clarify the right approach based on your current setup during the kickoff call.

Will referral links still work after migration?

Yes. Active referral links are preserved during the migration. Customers who have shared referral links don't need to generate new ones. Historical referral completions are also preserved, and pending rewards are reviewed to make sure they apply correctly.

What happens if a customer earns points in the gap between export and import?

This is the main technical risk of the migration, and it's why we recommend running the export during low-traffic periods. The Roadmap team monitors for this and reconciles any gap-period transactions. In practice, for most brands the volume of transactions during a 24–48 hour import window is small enough to handle manually if needed.

Do I need a developer to do this?

No. The Roadmap team handles the data migration, Roadmap configuration, and widget installation. You'll need some developer access for Klaviyo flow updates if you want to do those yourself — or the Roadmap team can guide you through those changes. Most brands complete this migration without involving an external developer.

Will this break my Klaviyo flows?

Your existing Smile.io-triggered flows will stop receiving triggers once Smile.io is deactivated. That's why reconnecting Klaviyo flows to Roadmap events is a required step before go-live, not an afterthought. Follow the migration table above for event name mapping, and test that flows are firing correctly during the testing phase.

Can I change my programme structure during the migration?

Yes — and this is often the best time to do it. Many brands use the migration as an opportunity to restructure tiers, adjust earn rates, add new reward types, or simplify their programme. It's easier to make changes during setup than to retrofit them later. Just be clear with the Roadmap team about what you want to change vs. what you want to replicate exactly.

What if something goes wrong post-launch?

Don't deactivate your Smile.io account for 30 days after go-live. You won't need it, but it's good insurance. The Roadmap team remains hands-on through the go-live period — this isn't a "here's your login, good luck" handover. Most issues, if any arise, surface in the first 48 hours and are resolved quickly.

What Changes After Switching

What stays the same

  • Point balances — migrated in full
  • VIP tier status — migrated
  • Core earn-and-redeem mechanics — customers still earn points on purchases and redeem for rewards
  • Active referral links — preserved
  • The customer's fundamental experience of loyalty membership

What gets better

  • Loyalty connected to reviews: Review submissions earn points natively — no integration required, no data passing between apps, no sync delays.
  • Loyalty connected to subscriptions: Subscriber tenure and subscription value feed into tier logic automatically. Your best subscribers can become your highest loyalty tier members without any manual logic.
  • In-store points: POS integration means physical store purchases earn the same loyalty points as online. One programme, not two.
  • Single Klaviyo integration: All retention events — loyalty, reviews, subscriptions, discounts — arrive through one source with consistent schemas. Build richer flows with cleaner data.
  • Consolidated billing: One platform, one invoice, one support relationship.
  • Unified customer view: See loyalty, reviews, subscriptions, and purchase history in one admin profile. No more switching between four tabs to understand who your best customers are.
  • Redemption experience: Roadmap's customer-facing redemption flow is built specifically to make it easy for customers to see and use their rewards — which means higher reward uptake and more repeat purchases.

What's different (but not worse)

  • Admin interface: Roadmap's dashboard vs Smile.io's. Most brands find Roadmap's interface cleaner, though any new interface takes a few sessions to feel natural.
  • Reporting layout: Different data presentation, though the same underlying metrics are available. Some reports are more detailed in Roadmap; a few Smile.io-specific views won't exist in the same format.
  • Widget styling: New widget design that's customised to match your brand. Better looking than Smile.io's defaults for most brands.
  • Event naming in Klaviyo: Different event names and property schemas. Documented in the migration table above — not a hard problem, just a task to work through.

Post-Migration Verification Steps

Once you're live on Roadmap, run this checklist in the first 48–72 hours. Don't wait for something to go wrong before checking — be proactive.

Day 1 (go-live day)

  • Confirm widgets display correctly on account page, product pages, cart, and the floating widget
  • Verify a live purchase earns points correctly — check the customer's account and confirm the Klaviyo event fired
  • Check that at least one Klaviyo flow has triggered from a real Roadmap event (not just test events)
  • Scan customer support inbox for any loyalty-related queries — respond promptly and use them as signal
  • Confirm Smile.io is fully deactivated and no longer showing any widget elements

Days 2–3

  • Spot-check five to ten customer accounts for correct point balances — prioritise your highest-value loyalty members
  • Verify tier logic is working correctly: place a test order that would trigger a tier upgrade and confirm the tier change fires in Klaviyo
  • If referral programme is active, verify a new referral completes correctly end-to-end
  • Check that reviews earn points if you've activated the reviews module
  • Review Roadmap's dashboard for any anomalies in earn activity volume vs your typical Smile.io baseline

Week 2

  • Review Klaviyo flow performance — open rates and click rates should be in a similar range to pre-migration if flows are working correctly
  • Check in with your customer support team on loyalty-related query volume — should be back to normal or lower by week two
  • Review your first Roadmap reporting period and confirm metrics make sense relative to your historical baseline
  • Confirm any reward redemptions that occurred in the first week processed correctly

How to Measure Success After Switching

Migration success isn't just "everything works" — it's whether the switch actually improved programme performance. Set up these metrics before you migrate so you have a pre-migration baseline to compare against.

Programme engagement metrics

  • Loyalty member active rate: Percentage of loyalty members who have earned or redeemed in the last 90 days. If this drops post-migration, investigate — it could mean a flow isn't triggering or a widget isn't displaying correctly.
  • Redemption rate: Percentage of rewards issued that are actually redeemed. This should improve with Roadmap's redemption experience — if it doesn't, check the redemption flow for friction.
  • Points earn per order: Average points earned per transaction. Should be consistent with your pre-migration earn rate immediately after launch.
  • VIP tier distribution: Number of members at each tier. Should be consistent with pre-migration immediately post-launch, then grow over time.

Revenue impact metrics

  • Loyalty member repeat purchase rate: How often loyalty members return for a second, third, or fourth purchase. The benchmark to beat is your Smile.io-era repeat rate.
  • Average order value by tier: VIP members should have a higher AOV than non-members. Track whether this relationship holds and strengthens post-migration.
  • Reward-influenced revenue: Revenue from orders that included a reward redemption. This measures whether rewards are driving purchases, not just being used on purchases that would have happened anyway.

Operational metrics

  • App spend: Your combined monthly spend on retention tools post-migration vs pre-migration. This should decrease.
  • Support ticket volume: Loyalty-related support queries should return to baseline within two weeks of go-live and potentially decrease as the programme becomes clearer for customers.
  • Klaviyo flow performance: Open and click rates on loyalty-triggered flows should be consistent or higher vs pre-migration benchmarks.

Give yourself 60–90 days post-migration before drawing conclusions on programme performance. The first 30 days reflect the transition; the 60–90 day window gives you a cleaner read on whether the switch has improved things.

The Cost Comparison

For most brands switching from Smile.io, the financial picture improves because the migration eliminates separate tools. Here's what the before and after typically looks like:

Before (Smile.io + typical stack) Approx. Monthly Cost
Smile.io Growth plan ~$199/month
Judge.me or Okendo (reviews) ~$99–199/month
Recharge or Skio (subscriptions) ~$99/month + transaction fees
Discounts tool ~$30–80/month
Total $427–577+/month
After (Roadmap) Monthly Cost
Roadmap (all modules) Single platform fee
Transaction fees on subscriptions $0
Total Typically lower than the combined stack

Beyond the direct cost savings, there's the operational cost: one admin dashboard, one support contact, one Klaviyo integration, one billing relationship. The time your team saves managing fewer tools is real — even if it's hard to put a dollar figure on it. Add the developer time saved not maintaining broken integrations, and the picture gets even clearer.

Is Now the Right Time to Switch?

The migration makes most sense if:

  • You're approaching a Smile.io billing increase or plan renewal and want to evaluate alternatives before committing to another year
  • You're planning to launch a reviews programme or subscriptions and want them on the same platform as loyalty
  • You have physical retail and need better POS loyalty integration
  • Your team is actively feeling the friction of managing loyalty, reviews, and subscriptions as separate tools
  • Your Klaviyo flows are becoming hard to maintain with multiple event sources and schemas
  • You're paying $300+/month across separate retention tools
  • Your current Smile.io plan doesn't give you the reporting or flexibility you need at your current scale

It's worth deferring if:

  • You're in peak trading period — Black Friday through January sales is not the time to change loyalty platforms
  • Your team doesn't have capacity for even a low-effort migration project in the near term
  • You've recently made significant custom development to your Smile.io setup that would need careful documentation before rebuilding
  • Your current stack is genuinely working well, cost isn't a concern, and fragmentation isn't causing you problems

Frequently Asked Questions

How do I migrate from Smile.io to Roadmap?

The migration is handled by the Roadmap team. You export your customer data from Smile.io (point balances, tier status, referral data), share it with Roadmap during onboarding, and the team handles the import, programme configuration, widget installation, and Klaviyo reconnection. Most brands don't need a developer. The full process typically takes one to two weeks from kickoff to go-live.

What data transfers when switching from Smile.io to Roadmap?

Customer point balances, VIP tier status, active referral links, and completed referral history all transfer. Programme configuration (earn rules, tier thresholds, reward options) is rebuilt in Roadmap during onboarding — usually an improvement on what was in Smile.io. Review data can also migrate if you're moving from a reviews app like Judge.me or Okendo at the same time.

Will my customers lose their loyalty points during migration?

No. Point balances are imported in full before Roadmap goes live. Customers see their existing balance reflected in Roadmap from day one. The import is validated before go-live, so any discrepancies are caught and resolved before customers see anything.

How long does it take to switch loyalty apps on Shopify?

For a Smile.io to Roadmap migration specifically, most brands are live within one to two weeks. Data import takes 24–48 hours. Programme configuration, widget replacement, and Klaviyo reconnection typically take three to five business days. Testing adds two to three days. Total elapsed time from decision to go-live is usually under two weeks.

Can I switch loyalty programmes without disrupting my customers?

Yes. The migration is transparent to customers when handled correctly. Points transfer, tier status transfers, and the loyalty experience continues. The main thing that prevents disruption is a simple email telling active loyalty members their points are safe — that one message eliminates the vast majority of potential confusion.

Does Roadmap work with Klaviyo after migrating from Smile.io?

Yes. Roadmap has a native Klaviyo integration that fires equivalent events to Smile.io's, with detailed properties. Your existing Klaviyo flows are updated to trigger from Roadmap events instead of Smile.io events as part of the migration. If you also activate Roadmap's reviews or subscriptions modules, those events come through the same integration — so you end up with one clean event source instead of three.

Is there a cost to migrate from Smile.io to Roadmap?

There's no startup fee to get started with Roadmap, and migration from Smile.io is covered by the Roadmap team. You're not paying a setup fee or migration fee on top of your platform subscription. The cost comparison is simply your current combined stack cost vs Roadmap's single platform fee — which for most brands running loyalty, reviews, and subscriptions separately works out in Roadmap's favour.

What's the best time of year to switch loyalty apps?

Avoid peak trading periods: Black Friday, Cyber Monday, Christmas, and January sales. The best migration windows are typically February, late spring (May–June), or early autumn (August–September) — periods with steady but not peak order volume. Mid-week go-lives (Tuesday–Thursday) are preferable to end-of-week in case you need support during the first 24 hours.

Bottom Line

Switching from Smile.io to Roadmap is a well-defined project with a predictable timeline. The Roadmap team handles the heavy lifting — data transfer, configuration, widget installation — so you're not doing this yourself. The main payoff is consolidation and connection: loyalty that works with reviews, subscriptions, and POS, with one Klaviyo integration and one support relationship.

If your brand has outgrown Smile.io's loyalty-only scope, or if you're tired of managing three or four separate apps to do what one platform should handle, the migration investment is typically worth making. Most brands complete it in under two weeks and see cleaner data, simpler operations, and a better customer experience from day one.

Why Roadmap Stands Out

  • There's no startup fee to get started with Roadmap — unlike some platforms that charge an onboarding or setup fee upfront.
  • Migration from another platform is covered by the Roadmap team — they handle the data transfer and setup so you don't have to.
  • Setup is handled by the Roadmap team — brands don't have to configure everything from scratch, which significantly reduces the time-to-value compared to self-serve platforms.
  • Roadmap's redeeming experience is the best in the market — the customer-facing redemption flow is designed to maximise reward uptake and repeat purchase conversion.

Thinking about switching from Smile.io? Talk to the Roadmap team about your specific migration. Book a conversation.

Share this post
Tag one
Tag two
Tag three
Tag four
Full name
Job title, Company name

Citations (17)

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique.

Question text goes here

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Question text goes here

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Question text goes here

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Question text goes here

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Question text goes here

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Question text goes here

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Still have questions?

Lorem ipsum dolor sit amet, consectetur adipiscing elit.