Pages for Airtable customers moving bases, records and attachments to self-hosted Baserow or Grist.
Airtable's bases, views, interfaces and automations compared with Baserow's MIT-licensed database, application builder and automations, including which Baserow features need a Premium, Advanced or Enterprise license when self-hosted.
Airtable compared with Apache-licensed Grist for teams whose bases lean on formulas: Grist's Python formulas and SQLite-based documents against Airtable's formula fields, and what single sign-on and automations cost in Grist's full edition.
Running Baserow's Airtable importer from a public share link, one base at a time: what comes across (records, attachments, relationships, grid views) and what has to be rebuilt, such as formula, lookup and rollup fields, automations and interfaces.
Moving Airtable bases into self-hosted Grist with its Airtable import, using personal access tokens or an OAuth2 integration registered with Airtable, then recreating formulas in Python and rebuilding views and forms.
Airtable's per-seat Team, Business and Enterprise Scale plans, with their record and API caps, compared with self-hosting Baserow or Grist: free community editions, paid licenses for single sign-on, hosting, migration and administration.
What Airtable lets you take out: CSV downloads per view and table with no whole-base export, attachment links that expire after a few hours, no comments or field descriptions, and the Web API with its per-base rate limit for a complete extract.
Why Airtable's Europe region only comes with Enterprise Scale and still keeps metadata and user data in the US, and how a self-hosted Baserow or Grist instance in an EU data center keeps all base data, metadata and accounts in one jurisdiction.
Comparing Airtable with Teable, which runs on PostgreSQL and is AGPL-3.0 licensed in its community edition: views, formulas and automations, what paid self-hosted plans unlock, SQL access to the data, and the work of moving bases without a built-in importer.
For teams that want their Airtable data in a real database: exporting each table as CSV, designing PostgreSQL tables and relationships, importing, re-linking attachments, and putting Teable or Mathesar on top as the spreadsheet interface.
Replacing Airtable Interfaces with Baserow's application builder: rebuilding dashboards, record review pages and portals on self-hosted Baserow, permissions for external users, and which interface patterns need custom work.
Replacing Airtable Automations, which no importer carries over: Baserow automations, webhooks to n8n for multi-step workflows, Grist automations in its full edition, and how to rebuild and test triggers before cutover.
For bases hitting Airtable's per-base record and attachment caps on Free, Team or Business: how self-hosted Baserow, Grist and Teable store data, where their practical limits come from instead, and what to size when records grow into the hundreds of thousands.
For integrations throttled by Airtable's 5 requests per second per base and monthly call caps: how the REST APIs of self-hosted Baserow, Grist and Teable are limited only by the servers you run, and how to size and protect them.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.