Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I want to move my business off Airtable onto a real database

Short answer

An Airtable move is more than copying rows. Linked records, formulas, attachments, forms, views and automations each need their own plan, and Airtable's record limits are per base, not per table. Export a backup, list what the base does, and run the new database beside the old base until your team has checked it.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I have hit Airtable's record limit or the base has become slow.
  • My data is split over several bases that I copy between by hand.
  • I need a real login system, customer access or reports Airtable cannot do.
  • Someone suggested Postgres, and I do not know what the move involves.
  • I am afraid my team will lose a day or more of work during the switch.

Why does this happen?

  1. A base mixes data and rules

    Rows are the easy part. Formulas, rollups, linked-record fields, forms, views, interfaces and automations hold business rules, and they do not copy over as data. Each has to be rebuilt in the new system, and the list has to be written down first.

  2. Record limits are per base and shared between tables

    Airtable states the record limit for each plan per base and says it is cumulative across all tables in the base. Teams that cross it often split a base into several, which makes linking and reporting harder and is a common reason for moving.

  3. Automation limits push logic out of the tool

    Airtable caps automation runs per workspace per month and the number of automations per base. Logic that outgrows those caps usually has to live in code or a workflow service.

  4. Integrations talk to Airtable's API

    Anything that reads or writes Airtable through its API, including old API keys, needs reworking. Airtable states that user API keys can no longer access its API, so those integrations were already moved to tokens.

  5. Data is looser than a database expects

    Airtable lets a text field hold a number in one row and a name in the next. A database column is stricter, so the move turns up blanks, duplicates, odd dates and inconsistent spellings.

What can I do about it today?

  1. Export each table as a CSV fileKeep the files in a folder you control. It changes nothing in Airtable and is your safety copy.
  2. Write down what the base doesFor each table: what it holds, who changes it, which other tables it links to. Add the automations and forms.
  3. Take screenshots of the views and interfaces your team usesThey show what the new screens must do, and they are easy to lose.
  4. Ask the team what they do every dayThe daily actions, such as adding an order or changing a status, decide what the new interface must do first.
  5. Do not start deleting or restructuring in AirtableKeep it exactly as it is until the new system has been tested.

When should I bring someone in?

  • The base holds orders, customers or money and cannot be offline.
  • You rely on linked records, formulas and automations nobody fully understands.
  • Customers, suppliers or contractors will need to log in to the new system.

How do I handle it?

  1. Inventory firstTables, links, formulas, attachments, automations and integrations are listed in writing, with who uses each.
  2. Design the database from the work, not the layoutI propose tables and relationships that match how the business works, with checks that stop bad data getting in.
  3. Import, then reconcileData is loaded from the exports and counted against the originals, with a list of rows that did not fit and why.
  4. Run side by sideYour team tests the new system on real tasks while Airtable stays untouched. Corrections are made before the switch.
  5. Switch on a date you pick, keep the old baseA final copy of changes is taken on switch day, and Airtable is kept as a read-only fallback until you decide to close it.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Do my attachments and images move too?

They have to be downloaded and stored somewhere on purpose, because a database row holds only a link. Plan for storage and for checking that every file arrived.

Can the team keep a spreadsheet-like view?

Yes. A simple grid interface can sit on top of the database, so people who liked Airtable's look are not forced into something unfamiliar.

Will there be downtime?

It can be kept very short or none, because the new system is tested beside the old one and only switched on a day you choose.

Is a real database always better than Airtable?

No. For a small team with modest data, Airtable can be the right tool. A move is worth it when limits, access or integrations are the problem.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.