For $5M+ DTC brands with active loyalty programs, the migration scope is concrete: points balances, tier assignments, redemption history, and any time-based mechanics (streaks, anniversaries, milestone rewards). The technical work is moderate; the customer-experience work around the migration is where outcomes are determined.
This page is the operator playbook: what data must transfer, how to handle the inevitable edge cases, and what proactive customer comms prevent the loyalty migration from becoming a churn event.
Symptoms
How the problem surfaces
High-tier customers lose status post-migration
The clearest failure mode. Customer was VIP-tier on the source platform but shows as base-tier in Shopify because the tier rules did not migrate accurately. Triggers immediate complaints from the most valuable customer segment.
Points balances differ from customer expectations
Customer checks their balance and sees a different number than what they remembered. Sometimes higher (manageable), often lower (problematic). Either way, trust in the program drops.
Reward redemption history disappears
Customers cannot see past redemptions in the new loyalty app. Generates support tickets specifically about whether previous rewards were honoured, especially around return-related point adjustments.
Time-based mechanics break
Streaks reset, anniversary dates drift, milestone progress restarts. Customers who were close to a milestone reward on the source platform may need to start over, which produces the largest churn risk.
Solution
The operator playbook
Inventory the loyalty program before migration
During discovery, build the explicit inventory: points balances per customer, tier assignments, redemption history, time-based mechanic progress (streaks, anniversaries, milestones), and the rules that govern point earning and tier transitions. Most of this lives in the source loyalty app, but some lives in customer metadata that the loyalty app references.
The inventory exercise often surfaces program complexity the team has lost track of — bonus point promotions that ran years ago and still affect specific customers, custom tier rules for specific customer segments, exemption flags. Surface these in discovery; treating them as edge cases at migration time consistently produces incidents.
Pick the Shopify loyalty target and migrate to its model
Shopify's loyalty app ecosystem (Smile.io, Yotpo Loyalty, LoyaltyLion, Stamped Loyalty, Marsello) each model loyalty slightly differently. The right pick depends on program complexity and brand size. Lock the decision in discovery so the migration target is fixed.
Brands often discover that the source program's complexity does not translate cleanly into any Shopify-side app. The realistic answer is policy simplification — migrate the customer-facing aspects (points, tiers, recent redemptions) cleanly, and retire or restructure the long-tail mechanics that do not translate. Communicate the changes openly; trust the customer base to understand the transition.
Send proactive customer comms before launch
Loyalty members are the brand's most engaged customers, and they should hear about the migration before launch. A proactive email 7-14 days pre-launch explaining the change, the new app, and any policy adjustments dramatically reduces post-launch support load and preserves trust in the program.
For high-tier customers specifically (top 5-10% by engagement), consider a personalised email from a named human acknowledging the change and offering direct support during the transition. The personal touch on the highest-value segment prevents churn that the generic email cannot.
Validate balances and tier assignments before cutover
Before flipping the loyalty app at cutover, run a validation pass: sample 50-100 customers across tier levels, verify their points balance and tier match between source and target systems, and resolve any discrepancies. The sampling catches systematic errors before they surface as customer complaints.
Tier assignment validation matters more than balance validation because tier benefits (free shipping, discount tiers, exclusive product access) immediately affect the next purchase. A miscalculated balance is recoverable; a missing tier benefit at purchase time produces an immediate customer-facing incident.
Cost
Cost range: $10K-$50K (inside the broader replatforming engagement)
| Cost line | Range |
|---|---|
| Loyalty program inventory and audit | $2K-$8K |
| Shopify loyalty app selection and configuration | $3K-$15K |
| Points and tier data migration | $3K-$15K |
| Customer comms (proactive + personalised) | $1K-$5K |
| Pre-cutover validation and reconciliation | $1K-$7K |
Cost scales with active loyalty member count and program complexity. Brands with under 10K members land near the lower end; brands with hundreds of thousands of members or with complex multi-tier programs land at the upper end. Vendor-managed migration tiers (Smile.io, Yotpo) often add $2K-$10K for migration support but materially reduce risk.
Timeline
Timeline: 5-9 weeks (parallel to broader replatforming)
Discovery and audit
Weeks 1-2
Loyalty program inventory, member-base analysis, policy decisions
App selection
Weeks 2-3
Shopify loyalty app shortlist, selection, target model alignment
Migration build
Weeks 3-6
Points balance migration, tier assignment, redemption history load
Validation
Weeks 5-7
Sample validation pass, reconciliation, customer comms send
Cutover and monitoring
Weeks 7-9
App switch, tier-benefit validation at purchase, support monitoring