Gadget is closing: deadlines for Shopify app teams

Gadget closes on 31 March 2027, but deployment and support milestones arrive sooner. What Shopify developers and merchants should plan now.

Will Slatton2 min read

Gadget is closing its hosted app platform on 31 March 2027. Shopify merchants whose apps depend on it should ask their suppliers for a migration plan; developers have nearer milestones to address before that final shutdown.

In its 9 November announcement, Gadget says existing apps will continue operating normally until the closure date. New apps can no longer be started, while first production deployments are permitted only through the end of November 2026.

Support changes before hosting ends

Gadget says support remains available through the end of 2026. After that, its team will concentrate on critical issues and keeping the service running. It promises migration guides and tools in the coming weeks; the announcement does not provide a completed migration procedure.

The company cites financial constraints and the challenge of maintaining a broad platform as development tools change. It is willing to discuss a community takeover, but that is not a confirmed continuation of the service.

Ask for a plan tied to your store’s workflows

Our recommendation is to start with a list of apps and the work each performs: order processing, stock updates, reporting or customer communications. Ask each supplier whether Gadget hosts any part of that work. A merchant should not have to infer the answer from an app’s branding.

For an affected app, request a named migration owner, a target cutover date and a description of how the supplier will check that the same work succeeds afterwards. Keep the response alongside the app’s support contact. An existing app remaining online today does not establish that its replacement is ready.

Rehearse the move before committing to a date

For developers and agencies, we recommend a written inventory of code, stored data, credentials, scheduled tasks and incoming integrations before choosing replacement hosting. Decide how to compare results during testing, how to avoid duplicate work during cutover and when the old deployment can safely stop.

Use a low-risk workflow for the first rehearsal. Record what must be rebuilt and what can be transferred, then revise the estimate for the remaining apps. Treat a successful deployment as one checkpoint: background processing and recovery from failed jobs also need evidence.

Review the separate Shopify app allowlist requirements and offline-token migration guidance with the team responsible for the new backend. A hosting move should have one coordinated security and authentication plan, rather than leaving those checks until launch.

These are planning recommendations, not a tested Gadget export recipe. Use Gadget’s eventual migration tools and the destination platform’s documentation to validate the actual move.

📅
Three planning dates: first production deployments end in November 2026; ordinary support ends with 2026; hosting closes on 31 March 2027.
Filed underNews

More from News

See all →