Skip to content

Met us at AccessAbilities Expo? Your gift is open until 30 November

Last reviewed November 10, 2026. By Blago Bonchev.

We move your Gadget app to native Shopify code

Gadget shuts down on March 31, 2027, and its support ends at the end of 2026. Rolling Pandas moves Shopify apps off Gadget to native code, with your own database and hosting, and keeps your Gadget app live until switch day.

Why move your Gadget app before the end of 2026?

Your app runs as it does today until March 31, 2027.

After that the platform behind it is gone: the database, the install, the webhooks and the hosting. Each of them needs a new home before that date. Moving before the end of 2026 means Gadget support still answers while you move.

A public app has an earlier date. On January 1, 2027, Shopify delists public apps that still use its older, non-expiring tokens and blocks their new installs. If we move your app before then, we switch its tokens in the same step.

Dates and a move checklist: Gadget is shutting down: what to do.

What did Gadget do for my app, and what replaces it?

  • Database and models

    What runs it after the move
    Postgres with a schema and migrations you own
  • The API Gadget generated for your models

    What runs it after the move
    Server routes written for your app
  • Install and sessions for merchants

    What runs it after the move
    Shopify's app framework with managed install
  • Webhooks

    What runs it after the move
    Webhooks declared in your app config, each call checked
  • Shopify data copied into Gadget

    What runs it after the move
    Only the data your app needs, pulled fresh from Shopify
  • Background actions

    What runs it after the move
    A job queue or scheduled jobs, with Shopify rate limits handled
  • Hosting and logs

    What runs it after the move
    Staging and production hosting with logs and alerts
  • File storage

    What runs it after the move
    Your own file storage
  • Privacy (GDPR) webhooks

    What runs it after the move
    Three privacy routes, answering from the first minute

Will my merchants have to reinstall?

If the Shopify app is in your own Partner or Dev Dashboard account, merchants don't reinstall.

We keep the same app and point it at the new server, so its reviews stay too.

That holds for public and custom apps that open inside Shopify admin, on any Shopify API version. If your app doesn't open inside Shopify admin, we test this on a development store first and tell you in writing.

On a public app with tokens that renew every hour, we move each store's tokens during the switch, so background jobs start again right after it. Only a store with no usable token waits until its merchant next opens the app. We check your app's case and tell you in writing before we quote.

If the app sits in someone else's account, it becomes a new app and every merchant installs again. That's the first thing we check.

How does the move work?

  1. We read your app: models, actions, webhooks, extensions, the screens merchants use and how much data you keep.

  2. You get a fixed price in writing. No hourly billing.

  3. We rebuild it on Shopify's app framework and keep your business logic. Your app runs on a database and hosting in your own name. You own the code, the data and the accounts.

  4. Gadget has no database dump today, so we write the script that moves your app's data, then check the record counts and spot-check records by hand.

  5. Switch day: a short freeze of up to an hour, then the app points at the new server. Your Gadget app stays live until that moment.

  6. Until March 31, 2027, we can switch back to Gadget if something goes wrong.

Should the developer who built it on Gadget move it?

Sometimes, yes. If they already ship native Shopify apps, they're a good choice.

Teams pick Gadget so they don't have to run the install, webhooks, data sync and hosting themselves. Moving off it means someone now builds and runs that part. It's a different job from building features.

Whoever you choose, ask one question: "Show me a native Shopify app you run today."

Who can migrate my Gadget app? Are there agencies that do it?

Rolling Pandas does. We're a Shopify team that builds native Shopify apps and runs one of our own.

  • Carded

    Our own public app for stores that sell age-restricted products: install, webhooks, Shopify billing, privacy routes, background jobs and tests, on our own stack. Submitted to the Shopify App Store.

More on our Shopify app development work.

Blago Bonchev leads it: 10 years building websites. One point of contact from the first message to switch day.

Not the right fit

We work on Shopify only.

If your Gadget app is for another platform, we're not the team for it. And if your developer already runs native Shopify apps, they may be your fastest route.

Questions about leaving Gadget

When does Gadget shut down?

March 31, 2027. Gadget support ends at the end of 2026, and first-time production deploys are allowed until the end of November 2026.

Will my merchants have to reinstall the app?

No, if the Shopify app is in your own Partner or Dev Dashboard account. That holds for public and custom apps that open inside Shopify admin, on any Shopify API version. For an app that doesn't open inside Shopify admin, we test this on a development store first and tell you in writing. If the app is in someone else's account, it becomes a new app and merchants install again. Background jobs are a separate question, below.

Will my app go down during the move?

Briefly. Switch day has a short freeze of up to an hour. Shopify retries webhooks it couldn't deliver, and a nightly check against Shopify catches anything missed.

Will background jobs keep running after the switch?

Yes, when the tokens move with the app. Gadget support confirmed in November 2026 that you, the app owner, can export each store's Shopify tokens. We move them during the switch-day freeze, and background jobs start again after the switch for every store with a usable token. Apps on API 2026-04 use tokens that renew every hour. On January 1, 2027, Shopify delists public apps that still use the older tokens and blocks their new installs. If your app's stores still hold Shopify's older tokens and we switch before that date, we move them to the new tokens ourselves during the freeze, with nothing for merchants to do. If a store has no usable token, its background jobs wait until its merchant next opens the app. We check which case your app is in before we quote.

Can I go back to Gadget if something breaks?

Yes, until March 31, 2027. That's one more reason not to wait until March.

How much does it cost to migrate off Gadget?

It depends on what your app does. We read it first, then send a fixed price in writing.

What happens after the move?

You own the code, the data and the accounts, so your team or any developer can run the app. Until March 31, 2027, we can switch back to Gadget if something goes wrong.

Do you move Gadget apps that aren't for Shopify?

No. We work on Shopify only.

How long does a Gadget migration take?

It depends on your app's size and what Gadget runs for it. We read the app first and send a dated plan with the fixed price.

Do you work with agencies that built client apps on Gadget?

Yes. We work white-label for agencies, and your clients stay yours. How it works, what we need for each client app and the partner terms: white-label Gadget app migration for agencies.

Send us your app while Gadget support still answers

Tell us what your app does and how many stores use it. We read it and send a fixed price in writing.

We use your details only to answer you. Privacy policy

London --:--
Varna --:--