Airtable to Supabase migration

Your business runs on Airtable, with years of tables, links, formulas and automations, and maybe a Softr or Glide app on top for your team or your customers. The bill grows with every seat, and in September 2026 Bending Spoons bought Airtable, which said a month later that it was parting ways with a large part of its team.

Source Airtable, Back to bases, 12 October 2026

• Your bases moved into a Supabase database in your name, which you can reach and back up whenever you want.
• Every linked record kept linked, so the connections between your tables come across as they are.
• Every file and image copied across before Airtable's download links run out.
• Your formulas, lookups and rollups working the same way in the new database.
• Your automations, and the Zapier or Make flows hooked to them, rebuilt so the work they did carries on.
• The app your team or your customers use rebuilt on the new database, in code you own.
• A recorded walkthrough of the new setup, for you or whoever runs it.

1. You share your bases, and I map every table, link, formula and automation, including the ones nobody remembers setting up.
2. A rehearsal runs first, into a fresh Supabase project, with your data checked against Airtable table by table.
3. Your app is rebuilt on the new database and tested by the people who use it.
4. On the day of the switch your data syncs one last time and your team moves across.

Airtable exports one table at a time, as a spreadsheet file from a grid view, and only the rows that view shows. Linked records come out as plain text, so the connections between your tables are lost, comments are left behind, and a whole base can only be exported in one go on Airtable's top enterprise plan.

Files are the trap. The export holds a link to each file rather than the file itself, and Airtable's download links expire after a few hours, so every file is copied into the new project's own storage before its link runs out.

Source Airtable, Attachment URL behavior

Everything that runs is rebuilt rather than exported. Formulas, lookups and rollups become part of the database, automations and scripts become scheduled jobs, and the interfaces your team clicks through become pages in your own app. A Softr or Glide app on top of Airtable comes across the same way, rebuilt on the new database, with each user signing in again on the new app.