TL;DR
- Migration is expensive — configurator rebuild, compatibility-rule re-encoding, 3D pipeline reverification.
- Staying is usually rational when Kickflip is working and the per-item fee is absorbed cleanly at your AOV and volume.
- Migrating pays back when per-item fees outweigh the rebuild cost (typically high-volume stores) or when the use case has shifted from configurator to personalizer.
- Past orders carry over via Shopify line item properties regardless of which app you switch to.
- Parallel-run principle: keep Kickflip live while you rebuild and test elsewhere — no downtime, low risk.
The migration decision frame
Kickflip migration is more involved than swapping an options app or personalizer. The configurator IP — component models, compatibility rules, pricing logic, conditional flows — represents real investment. Moving means rebuilding that in the new app. Before deciding to migrate, the honest question is whether the migration cost pays back. The math has three parts:
- Rebuild cost: hours to recreate the configurator + 3D pipeline + rule set in the new app. Often 40-200 hours for a moderately complex configurator.
- Per-item-fee savings: the difference between Kickflip's per-item fee (1.95% starting per Kickflip's Shopify App Store dev response) and the new app's pricing, multiplied by your annual custom-order volume.
- Capability gap: whether the new app actually does what you need. If the new app can't handle your compatibility logic at the required depth, the migration isn't a migration — it's a downgrade.
When staying is rational
- Kickflip is working and your AOV absorbs the per-item fee cleanly. At $1500+ custom-bike AOV with 1.95% (starting) per-item, the fee is $29+ per order — meaningful in dollars but proportional to the high-AOV order.
- Your configurator has real depth (3D models, compatibility rules, multi-step assembly). Recreating it elsewhere is a meaningful investment.
- No better alternative exists at your tier. For genuinely build-your-own configurator products, Kickflip is purpose-built; Shopify-app alternatives often don't match the configurator-first depth.
- Your fulfillment team is trained on the current line-item-property payload. Changing the app changes the payload shape and means retraining.
When migrating pays back
- High-volume stores where per-item fees substantially exceed what flat-fee alternatives would charge. Run the math on annual per-item-fee total vs alternative pricing.
- Use case has shifted from configurator to personalizer (you used to need real assembly logic, now your products are mostly text/photo on a fixed shape). A configurator-first app for a personalizer use case is paying for capability you don't use.
- Kickflip can't do something specific you need — a particular integration, a particular workflow, vendor handoff. Verify the gap is real before deciding.
- Cost structure has shifted at Kickflip in a way that makes the math not work anymore. Pricing changes are real for any app; reassess.
If you do migrate — the parallel-run principle
- Pick the target app based on your use case. For configurator use cases, options are Zakeke (personalizer with 3D), Threekit (enterprise), or simpler 2D personalizers if the use case has shifted. For 2D personalizer use cases, flat-fee alternatives like PIMW.
- Document the current Kickflip setup: component models, compatibility rules, pricing logic, conditional flows. Screenshots and rule-set exports.
- Rebuild in the target app on a test product. Verify the configurator behaves correctly: components compose, rules enforce, pricing computes.
- Place test orders through the new app. Confirm the line-item-property payload flows correctly to your fulfillment team and any POD vendor.
- Parallel-run on production: assign new products to the new app, keep existing products on Kickflip. Migrate product by product as confidence builds.
- Uninstall Kickflip only after all products are migrated and you've confirmed the new app handles everything. Past orders are preserved via Shopify line item properties; no historical-data loss.
Use case shifted to 2D personalization?
If your configurator use case has shifted to fundamentally 2D personalization (text, photo, monogram on fixed products), a flat-fee 2D personalizer is the right tool — no configurator overhead, no per-item fee. Print It My Way runs free.
Install Print It My Way — Free See Kickflip pricing in 2026 →Frequently asked questions
Should I migrate off Kickflip?
Usually no, if Kickflip is working and your AOV absorbs the per-item fee (1.95% starting per the App Store dev response). Migration means rebuilding the configurator — component models, compatibility rules, pricing logic — in the new app, which is real investment. The cases where migration pays back: high-volume stores where annual per-item-fee total substantially exceeds what flat-fee alternatives would charge, use cases that have shifted from configurator to personalizer, or capability gaps Kickflip genuinely can't close. For most working Kickflip stores, the rebuild cost outweighs the per-item-fee savings unless one of those conditions applies. Run the math at your specific volume.
What does Kickflip migration actually involve?
Three significant chunks. (1) Configurator rebuild: recreating component models, compatibility rules, pricing logic, and conditional flows in the new app. For moderately complex configurators this is typically 40-200 hours of work. (2) 3D pipeline reverification: confirming the new app's 3D model handling matches your existing setup, or commissioning new model work if the format differs. (3) Fulfillment-team retraining: the new app's line-item-property payload shape differs from Kickflip's, and your fulfillment team needs to read the new format correctly. Plan for these costs alongside any per-item-fee savings.
Will I lose past Kickflip orders if I migrate?
No. Configuration selections on past orders are stored on the Shopify order itself as line item properties, so they remain intact and viewable after you uninstall Kickflip or install a new app. Your Shopify products are untouched. What doesn't transfer automatically is the per-product configurator setup — component models, rules, pricing logic — because that lives in Kickflip's system. Plan a parallel run: keep Kickflip installed while you rebuild and test in the new app, switch products gradually, and only uninstall once everything is working in the new app.
When does per-item-fee savings justify migration?
Run the math: estimate annual custom-order volume × AOV × Kickflip's per-item fee rate at your volume tier = annual fee total. Compare to the same calculation under the alternative app's pricing model. If the alternative is flat-fee with no per-item fees (like PIMW), the comparison is straightforward — annual Kickflip fees vs annual flat-fee plan cost. The migration pays back when the savings exceed rebuild cost amortized over your expected stay on the new app (typically 2-3 years). For low-volume stores, the savings rarely cover rebuild. For high-volume stores at thinner margins, the math can shift fast.
What if the use case has shifted to personalization?
This is one of the strongest migration cases. If you used to need real assembly-configurator logic (build-your-own-bike, modular furniture) but your current catalog is mostly text/photo personalization on fixed products, you're paying configurator-app pricing for personalizer-app capabilities. A 2D personalizer fits the actual use case at lower cost and simpler setup. The migration is also simpler because personalizer configurations rebuild faster than configurator-with-compatibility-rules. Audit your last 6 months of orders: are they predominantly configurator-style assembly orders or personalization orders? If personalization, evaluate the move.
How long does Kickflip migration take?
Highly variable based on configurator complexity. Simple configurators (a handful of components, basic compatibility) migrate in 2-4 weeks parallel-run. Moderately complex configurators (custom-bike-scale, 8-12 components with 10-30 compatibility rules) take 6-12 weeks. Complex configurators (custom-PC-scale, 30-50 compatibility rules) can take 3-6 months including verification. The parallel-run principle keeps you from facing downtime risk — Kickflip stays live until the new app is verified working — so the migration timeline affects effort, not store uptime. Plan accordingly.