Recharge to Skio Migration: The Operator Walkthrough

A platform migration is a data migration that happens to look like a product migration

The 2025 Shopify checkout extensibility deadline pushed hundreds of Recharge brands into a platform decision they were not planning to make. For many, Skio has become the answer. We have run these migrations for brands ranging from 3,000 to 120,000 active subscribers. The work that actually matters is not on the Skio side. It is in the data you carry across.

TL;DR ▸ Plan for six to ten weeks from kickoff to full cutover, longer if gift subs or prepaid are in scope ▸ 80 percent of migration risk lives in data mapping, not integration ▸ Run parallel for at least two shipment cycles before deprecating the old platform ▸ The subscriber communication plan is not optional, it is the determinant of churn during migration

This post is the step-by-step we follow on every migration. It is written for operators who have done a platform migration before and know where bodies get buried. The subscription migration service page covers the commercial version. This is the technical detail.

Phase one: decision validation

Before touching any tooling, validate the platform decision. The Recharge vs Skio comparison covers the feature delta. The operator-level questions are different.

Ask:

1. Is my current churn problem caused by the platform or by my program design
2. What custom integrations exist that I will have to rebuild
3. Which third-party apps depend on my current subscription events
4. What is my portal customization depth and can the new platform match

A platform migration does not fix a program that is losing subscribers because the product and cadence are wrong. If your month one churn sits at 40 percent, read how to fix the first month churn cliff before you decide the platform is the issue.

Phase two: data audit in the source

The source data audit happens before anyone touches Skio. Export everything.

Required exports from Recharge:

• Full subscriber list with sign up date, next charge date, status, and cadence
• Subscription line items with SKU, quantity, price, and discount
• Customer records with billing and shipping addresses
• Payment method metadata, tokens handled through gateway portability
• Order history for at least 24 months
• Discount codes and their usage history
• Prepaid balances and remaining shipment counts
• Gift subscription records with recipient data
• Custom fields on subscriptions and customers

Run a data hygiene pass. You will find subscribers with missing next charge dates, duplicate customer records, orphaned subscriptions, and failed payment states that never resolved. Clean these in Recharge first. Migrating garbage into Skio multiplies the garbage.

A hygiene checklist we use: ▸ Every active subscription has a valid next charge date in the future ▸ No subscription has a status of failed for more than 14 days ▸ Every customer has a matching Shopify customer record ▸ Prepaid ledger balances to zero across all accounts ▸ Gift subscriptions have valid recipient emails

This audit typically finds 2 to 5 percent of records need intervention. On a 30,000 subscriber base that is 600 to 1,500 records to manually resolve.

Phase three: gateway portability

Payment token portability is the single largest unknown at migration start. Both Recharge and Skio support Shopify Payments tokens through Shopify native channels. If you are on Stripe or Braintree directly, confirm token portability with your gateway rep in writing before commiting to a migration date.

The tokens move as metadata. Customers do not need to re-enter payment information. But the metadata has to arrive at Skio with every field intact. A single missing billing postal code will fail the charge. Test with 10 real subscribers before the full import.

Phase four: Skio build in parallel

While the data work runs, stand up Skio in parallel to Recharge. The install does not conflict. The customer-facing portal and checkout integration stays off until cutover.

Build steps in Skio before cutover:

1. Install the app and connect to Shopify
2. Configure subscription products that match your Recharge catalog exactly, SKU for SKU
3. Set up discount rules that mirror existing Recharge rules
4. Build the customer portal to match your current Recharge portal design
5. Configure email notifications to match or improve on current templates
6. Set up the Klaviyo integration and map the subscription events
7. Test the full subscribe flow on a staging product
8. Run a test charge end to end on a real product

Our subscription development team handles this phase as a standalone project before migration day. The goal is that Skio is production-ready and sitting idle, waiting for the import.

Phase five: parallel testing

With Skio built and the data exports in hand, run a parallel test. Pick 25 to 100 subscribers across cohorts. Import their records into Skio as active subscriptions. Do not process charges yet. Verify every field landed correctly.

Spot check:

• Next charge date matches Recharge exactly
• Cadence and frequency are identical
• Discount terms carry over with correct percentages and durations
• Shipping address and billing address are both present
• Payment token is attached and validates

Fix mapping issues in the import script before scaling to full population. Most issues surface on the first 25 records. The scripts that work for 25 work for 25,000.

Phase six: the cutover plan

The cutover plan is a minute by minute runbook. Write it in a shared doc with every team member assigned to a task.

Sample cutover timeline for a Tuesday 10pm ET cutover:

• 9:45pm: Freeze new subscribe checkouts at the theme level
• 9:50pm: Pause Recharge charge queue
• 9:55pm: Take final Recharge data export including last hour of activity
• 10:00pm: Run delta import into Skio for any subscribers created in the final day
• 10:15pm: Validate total subscriber count matches source exactly
• 10:30pm: Flip the Skio portal live and deprecate the Recharge widgets
• 10:45pm: Remove Recharge scripts from theme
• 11:00pm: Unfreeze new subscribe checkouts, now routing to Skio
• 11:15pm: Send migration email to subscribers
• 11:30pm: Begin monitoring support inbox

Pick a low-traffic window. Have someone on-call for the next 24 hours. Have the Skio success team on standby.

Phase seven: subscriber communication

Communication is the retention variable during migration. Silent migrations lose 3 to 8 percent of the subscriber base to confusion-driven cancels. Explicit migrations lose under 2 percent.

The migration email sequence:

1. Pre-announcement 14 days before cutover: explain the change and why
2. Day before cutover: set expectations for the portal URL change
3. Migration day: confirm the change is complete, here is your new portal
4. Three days after: reminder of the new portal, FAQ link
5. First charge on new platform: confirmation with new platform branding

Use Klaviyo to segment the migration messaging. Our Klaviyo implementation service builds the sequence as reusable templates for brands running repeated platform changes.

Tone matters. Do not apologize for the migration. Position it as an upgrade. Frame the benefits: better portal, faster checkout, easier swaps. Customers follow the tone you set.

Phase eight: post-cutover monitoring

The first 14 days after cutover determine whether the migration is a win or a churn event. Monitor these metrics daily:

If any metric hits red flag territory, pause and diagnose before taking more traffic. Most red flags resolve within the first 72 hours as the long tail of subscribers log in for the first time.

What breaks most often

From 14 migrations we have shipped:

▸ Discount codes with complex stacking rules need manual rebuild, import scripts do not handle nested conditions ▸ Prepaid gift subscriptions need ledger reconciliation before import, or balances arrive wrong ▸ Skip and swap history does not always carry over, customers see a reset subscription history ▸ Klaviyo events switch from Recharge event names to Skio event names, all flows that reference old names need updating ▸ Google Analytics and Meta pixel events need reconfiguration, subscription purchase tracking often breaks silently for a week

The Klaviyo event rename is the one that burns brands. An automated winback flow listening for a Recharge-specific event will go silent on migration day. The revenue impact is invisible for weeks. Audit every Klaviyo flow before cutover and update the event names.

Read Klaviyo flows that move revenue for the list of subscription-specific flows that need attention during migration.

Cost of delay

Every month a brand delays a Recharge to Skio migration past the point of decision is a month of accumulating switching cost. New flows built on Recharge have to be rebuilt. New integrations add surface area. New subscribers acquired onto the old platform are subscribers to migrate later.

If the decision is made, move. The full subscription development service ships migrations in the six to ten week window. The churn reduction program can run in parallel so the new platform launches with an improved program design.

What to do this week

▸ Run the data hygiene audit on your current Recharge data ▸ Export the full dataset and tag records that need manual resolution ▸ Confirm payment token portability with your gateway in writing ▸ Pick your cutover window at least six weeks out, on a low-traffic night ▸ Draft the subscriber communication sequence and get it into Klaviyo ▸ Identify every Klaviyo flow that depends on Recharge event names ▸ Schedule parallel testing with 25 to 100 real subscribers before full cutover

A Recharge to Skio migration is not a checkbox project. It is a full-spectrum subscription program replatform with legal, operational, and customer-facing risk. Planned right, it is an uneventful weekend. Planned wrong, it is a quarter of recovery. The sequence above keeps it in the first category.