Move from Gadget to NocoDB

Take it out

1. 1

   Step 1

   Read the dates before you look for a download button

   Mo and Harry's November 9, 2026 post says existing apps keep running until March 31, 2027. New applications cannot be started. A first production deploy is allowed until the end of November. Support stays through the end of the year. The post says migration guides are coming and will be emailed. It does not name a file, a format, or an export screen. This guide did not find one in the docs checked on November 12, 2026.

2. 2

   Step 2

   Write down the models while the editor still opens

   The docs describe Postgres-backed models, actions and queues, a generated API, and built-in authentication. Copy the field names, the field types, and any action you still need into a file on a disk you control. That file is the rollback. The post does not say the database file can be downloaded.

3. 3

   Step 3

   Keep a small sample aside

   Pick one model and a handful of records. Leave the full notes untouched until that sample exists as a table somewhere else.

Put it in

1. 1

   Step 1

   Install NocoDB

   NocoDB's listing on this site points at Docker Compose, or SQLite for a trial, against Postgres or MySQL if you already run one. The license is the Sustainable Use License. Running it for your own team is free. Selling NocoDB itself as a service needs a paid license. This guide did not run the installer.

2. 2

   Step 2

   Create the table from the notes

   Add a table for the model you copied. Use the field names you wrote down. NocoDB's own description is a grid, views, and an API on that database. It does not read a Gadget project file. Load the sample records first. Stop if the names or the types are wrong.

3. 3

   Step 3

   Point a new screen at the API if you still need one

   The generated Gadget client does not move. Appsmith and ToolJet are the screen builders on the same checklist. They connect to SQL or HTTP. They do not import Gadget's frontend. Build the one screen people open, and leave the rest until that screen matches the sample.

What you lose

• What the shutdown post leaves out

  Queues, authentication settings, environment variables, and the hosted URL are not in an export the post describes. A Shopify connection and a BigCommerce connection are in the Gadget docs. NocoDB does not replace those connections.

• Guides that are not published yet

  The post says the team will email when migration guides and tools are ready, and that a community takeover can be discussed at future@gadget.dev. Neither line is a file you can import today. Check the post again before you treat this copy as the only path.

• The license is not the open-source grant

  NocoDB moved from AGPL-3.0 to a Sustainable Use License on January 9, 2026. Your own team's install stays free. Reselling the product as a service does not.