Case Studies Articles Services Discuss implementation
EN DE
All articles

Gadget.dev is shutting down: migrate your Shopify app before 31 March 2027

What your app needs after Gadget: compare migration paths, move the data, rebuild background work and test the replacement before cutover.

Discuss your Shopify implementation

Gadget shuts down in

Detailed dark 3D illustration of a server module being transferred from an old rack to a new green-lit rack

Gadget is shutting down on 31 March 2027. If your Shopify app runs on it, the backend, data and background processes need a new home before that date. The store can stay on Shopify; the work is replacing the services Gadget runs for your app.

What the shutdown means for your app

Gadget announced its wind-down on 9 November 2026. Existing apps remain operational until 31 March 2027. New app creation has stopped, first production deploys are allowed through the end of November, and regular support continues through the end of 2026. Gadget says migration guides and tools will follow (official announcement).

Use the remaining support window to settle export access, stored credentials and behaviour you cannot reproduce. Do not base a delivery date on an export you have never restored.

Start by finding out what you can export and proving that a real merchant workflow runs elsewhere. Use that evidence to choose the target, estimate the rebuild and set the cutover date.

Stormdev provides Shopify app migration and development services. This guide describes how we would scope the move, including the work that stays with the app owner after launch.

What has to move, and who owns the work

Inventory models, actions, connected shops, files, extensions and external integrations. Trace a merchant operation from its trigger to its final write. Assign an owner and an acceptance check to each component.

Gadget component Replacement Work the app owner must cover
Custom models Database and migrations Preserve IDs, relationships and shop boundaries.
Model and global actions Routes, functions or workers Port validation, permissions and side effects.
Shopify connection Authentication and API client Recover credentials, verify sessions and handle renewal.
Shopify data sync API reads, webhooks and reconciliation Choose copied fields, backfill and repair missed changes.
Scheduled and queued actions Scheduler and durable jobs Retries, duplicate protection and recovery after downtime.
Files and embedded frontend Object storage and app host Copy files and references; rebuild and test the interface.

A database host covers only part of this table. Test whether scheduled work wakes a sleeping service and how missed runs are recovered. A configured schedule proves neither.

Compare three migration paths

The choice depends on who will maintain the app after the move. Rewriting in another language is an implementation decision within these paths, with its own schedule cost.

Path Suitable when Responsibility after launch Trade-off
Rebuild and host it yourself Your team can maintain production operations. Your team owns code, backups, monitoring and incidents. More control, with continuing operating work.
Rebuild on another hosted platform Its runtime and data model fit the app. The platform operates its service; your team owns application behaviour. Less infrastructure work, with new limits and vendor dependency.
Hire a migration and maintenance provider Your team needs delivery or operating support. Split duties explicitly in the agreement. Implementation support, with an ongoing supplier relationship.

For every option, ask who controls the repository, how data can be exported and restored, and how hosting can be transferred later. Get written answers for incident handling and API upgrades. Choose a target that can be proven before shutdown.

Budget for the complete replacement

Estimate the build separately from monthly operations. Active-shop count alone does not describe a workload: a catalogue backfill may dominate API calls, database writes and queue usage.

Measure a normal day and a full resync. Include compute, database and backups, files, transfer, queues, scheduled work, logs, email and maintenance. Check spending limits and alert behaviour with the selected providers. An alert is not a spending cap.

Keep contingency for unknown export formats and platform-specific actions. Quote the migration after an export rehearsal and a working end-to-end flow, then price the operating responsibilities separately.

Map Gadget concepts and make the losses explicit

Search the codebase for platform dependencies before estimating the rebuild.

In Gadget In a replacement stack
Model actions and global actions Application functions called by routes or workers.
Generated frontend API An authenticated API and client maintained in your repository.
connections.shopify.current An API client bound to a shop from verified authentication.
Access controls Authorization checks and shop-scoped queries.
Enqueued actions Durable job records and workers with observable completion.
Environment configuration Deployment configuration and protected secret storage.

Check which conveniences the destination actually replaces. You may lose generated APIs, the schema editor, hosted previews and managed Shopify sync. A document database also changes relationships and queries. Managed hosting does not automatically restore these features.

For Shopify data, choose the smallest justified copy. Read on demand if no local dataset is needed. For local filtering, store the required fields and reconcile them. A full mirror needs backfill, updates and a repair process, each with an owner.

Rehearse the export and protect live writes

Confirm the export options with Gadget support. Do not assume raw database access, a complete SQL dump or portable encrypted credentials.

Import into a disposable target. Check relationship counts, original IDs, representative records, file references and separation between shops. Restore a backup of the target as well. Keep the results as cutover evidence.

The production app keeps changing during the rehearsal. Choose a controlled write pause for the final export, or test a catch-up process. Record the checkpoint and prove that changes after the first export reach the replacement. Reconcile before enabling production writes.

Only one system should perform each external side effect. During comparison runs, suppress emails, billing and external writes on the replacement unless a tested ownership mechanism prevents duplication. Record unfinished work for safe replay.

Keep the Shopify app, replace the backend

Plan to retain the existing app identity and installations. Check who controls the app in Shopify's Dev Dashboard, its configuration and its credentials. Creating a replacement app can introduce reinstalls, billing changes and review work that an infrastructure move may avoid.

Make a routing inventory: app URL, redirect URLs, app proxy, extension endpoints and webhook addresses. Record which settings belong to Shopify and which are controlled by Gadget. Keep a copy of the working configuration so the cutover can be reviewed and reversed while the old platform is available.

Build the replacement against a development app first. Prove that a merchant can install it, open the embedded interface and complete its main task. Then confirm that background work can run without the merchant leaving the app open.

For existing shops, establish what access credentials can be exported and used by the new backend. Ask Gadget support to confirm the supported transfer process. If access cannot be carried over, plan reauthorization and explain the required action to merchants before switching.

An app URL change affects the app configuration. To trial the replacement with selected production merchants, use authenticated routing that deliberately selects a backend for each shop. Keep other shops on the old system until the trial passes.

Acceptance tests before switching traffic

Agree expected results and retain evidence from these tests on the target:

  • Initial backfill: compare required records, relationships and totals against the source, including a large shop and an empty shop.
  • Duplicate webhook: deliver the same event twice and confirm a single business effect.
  • Delayed event: replay an older event after a newer update and confirm the intended final state.
  • Failed API request: simulate throttling and a worker restart; unfinished work must remain recoverable without duplicate effects.
  • Uninstall: stop work for that shop, handle revoked access and prove the deletion workflow reaches the relevant datastores.

Also test installation, authorization and rejected cross-shop access on the replacement. Have the owner sign off on the embedded interface and a representative merchant workflow. A homepage load or database import cannot establish that background processing works.

Run in parallel, then cut over with a rollback deadline

Run the replacement alongside Gadget using controlled event forwarding or a replayable event log. Compare results automatically, investigate mismatches and obtain user acceptance before switching. Keep production side effects under a single owner.

Write the runbook: final catch-up or write pause, traffic switch, smoke checks, monitoring owner and abort criteria. Reconcile subscriptions individually. Shopify distinguishes app-specific TOML configuration from shop-specific Admin API subscriptions; changing one does not update the other (subscription types).

If rolling back after the replacement accepted writes, reconcile those writes before returning traffic. Confirm that the old backend still has valid access and can resume the work before treating it as a rollback option.

Keep compliance endpoints working across the transition. Shopify sends shop/redact 48 hours after uninstall; test that delayed delivery reaches the responsible system (Shopify requirements). Data retention needs a separate policy; this operational checklist is not legal advice.

Rollback to Gadget ends when its service ends on 31 March 2027. Retained DNS, logs and backups do not extend that window. Afterwards, recovery depends on replacement infrastructure and tested restores.

Finish the handover before the shutdown

After the traffic switch, run a complete business cycle on the replacement. Check scheduled exports, overnight jobs, subscription handling and the reports merchants actually use. Watch failed deliveries and unfinished jobs, then reconcile the results with the source systems.

Hand over the repository, deployment instructions, restore procedure and operating contacts. Remove obsolete routes and access only after the new service is accepted and the agreed retention and deletion work is complete. A migration is finished when the responsible team can run and recover the app without Gadget.

A schedule for leaving Gadget

Use these planning targets, adjusted after the rehearsal:

  • November: resolve export and credential access; prove a development-store workflow.
  • December: complete the rehearsal and a controlled production trial while regular Gadget support remains available.
  • By the end of February: finish production cutover, recovery tests and owner sign-off.
  • March: monitor, reconcile remaining work and complete handover before shutdown.

Stormdev can scope the rebuild, data transfer, authentication, webhooks and cutover. The assessment should produce a component inventory, architecture, open risks, acceptance tests, responsibilities and an app-specific estimate.

The proposal should state who owns the repository, hosting account and backups, who watches the app during cutover, and who maintains it afterwards. Agree the export method and access constraints before committing to a production date.

Discuss your Gadget migration with Stormdev. Bring the app's purpose, connected-shop count, integrations and export constraints so the first conversation can establish what needs to move.

Shopify implementation

Need help implementing this in your store?

Send me your store and the specific problem. I’ll review the current setup and recommend the smallest reliable next step.

  • Direct discussion with the developer who implements the solution
  • Clear technical assessment without unnecessary complexity
  • Implementation aligned with your store, systems, and operations
Please complete this field.
Please enter a valid email address.
Please complete this field.