How does white-label Gadget app migration work?
You keep the client and sell the move. We read each app, rebuild it on native Shopify code and run switch day, and we report to you.
- We never pitch your clients or contact them for our own work.
- Your brand on the work if you want it, and our name stays off.
- One point of contact for your team.
- Each client's Gadget app stays live until switch day.
- The app runs on a database and hosting in your client's name. Your client owns the code, the data and the accounts.
What do you need to know about each client app?
Six questions for each client app:
Is the Shopify app in your client's own Partner or Dev Dashboard account, or in yours?
Is it a public App Store app or a custom app?
What does the app do, and roughly how many models and records does it keep in Gadget?
How many stores have it installed, and does it charge merchants through Shopify billing?
Which Shopify API version is the app on, 2026-04 or older?
Which Gadget framework version is the app on, 1.7 or 1.6 and below? (Not sure is fine, we read it in the code.)
If you can, also give us read access to the Gadget app, or send a ggt pull of the code. Then we read it ourselves instead of asking more.
For most apps, that's enough for a fixed price in writing and a dated plan.
What do I keep as the agency?
The client, the relationship and the billing.
You quote your client, we quote you a fixed price per app. Partner pricing, agreed with you.
Who does the work?
Rolling Pandas, a Shopify team that builds native Shopify apps and runs one of its own.
Our own public app, Carded, is submitted to the Shopify App Store. Blago Bonchev leads it: 10 years building websites.
What are the partner terms?
The same as all our agency work: agency partners. Nothing on this page changes them.
Not the right fit
We work on Shopify only. If your Gadget apps are for another platform, we're not the team for them.