Replacing Airtable with custom software: from flexible base to scalable application

Airtable was an excellent choice for digitising a process quickly: a lightweight CRM, a content calendar, a product roadmap or a supplier register. But as soon as your team grows, the number of records passes tens of thousands or your business logic hits the limits of no-code, that same flexibility becomes a brake. We build custom software that replaces your Airtable bases without you losing your way of working or your data.

Migration from Airtable Custom web app Custom business logic EU hosting For scale-ups and SMEs
Discuss your migration See the limits
+ 24.812 records Limiet bereikt

When Airtable can no longer keep up with your team's growth

Airtable markets itself as the "spreadsheet with superpowers" for good reason. For modelling a workflow in an afternoon, little can compete with it. But the same qualities that make Airtable so well suited to getting started become limitations as your business grows.

You probably recognise the signs. A base that started out tidy now has forty fields, half of which are no longer used. An automation that syncs customer orders every night stopped twice by the last audit because it ran out of its run budget. A new colleague asks why your "interface" has no mobile version, and why a discount calculation that would work perfectly well as an Excel formula has been rewritten three times in Airtable Scripting and is still prone to bugs.

This isn't a failure of Airtable. It's the normal point at which a no-code platform has played its part. Airtable bases are ideal for MVPs, for experiments and for teams that want to validate something quickly. But for a process that is central to your business, such as a CRM with a hundred thousand leads, an operations platform your field staff use every day, or a product register that syncs with several web shops, it makes sense to move to custom software. Not because it's fashionable, but because at a certain point Airtable's cost curve, combined with its ceilings on business logic and user management, becomes structurally more expensive and more fragile than your own application.

On this page you'll read which features make Airtable strong in the early stages, which six limits scale-ups, agencies and modern SMEs typically run into, what a migration path looks like in practice and which use cases are best suited to a custom web application. We don't claim that custom software is always the answer. We do claim that at some point it becomes the sensible answer, and that the switch can be planned and low-risk, provided you choose the right partner.

What makes Airtable strong, and why you chose it in the first place

Before we get to the limits, it's only fair to acknowledge Airtable's strengths. We would never advise you to replace something that is still serving you well. The decision to migrate away should be backed by measurable problems, not by technology trends.

โšก

Getting started fast without development

You can create a base in minutes. Fields, column types, formulas and linked records are visualised in a spreadsheet-style interface. For validating a process that's unbeatable: no sprint planning, no tickets, you just get on with it.

๐Ÿงฉ

No-code automations

Airtable Automations link triggers (record changed, form submitted, date reached) to actions (send an email, update a record, post a Slack message). For lightweight workflows it's powerful enough, and it works without anyone having to write code.

๐Ÿ‘€

Multiple views on the same data

Grid, Kanban, Gallery, Calendar, Gantt, Timeline and Form views on the same table. Sales looks at the pipeline in a Kanban view, marketing at content planning in a Calendar, and operations in a filtered Grid. One source, several perspectives.

๐Ÿ”—

Linked records and lookups

Tables can be connected through linked records, with automatic lookup, count and rollup fields. It's a lightweight relational structure without having to write SQL. For projects with clients, tasks with deadlines and products with categories, that works fine.

๐Ÿงช

Interface Designer and Apps

With Interface Designer you build a lightweight UI on top of your base so end users don't see the raw tables. The Marketplace offers extensions, such as charts, Gantt and page designer, that add to the standard toolkit.

๐Ÿ”Œ

Official API and Sync

A REST API lets external systems read and write records. Sync sources pull in data from Salesforce, Zendesk, Google Drive and other bases. For lightweight integrations the barrier to entry is low.

All of this is true. And that is exactly why Airtable works well in the first phase of a process. The problem is not the tool itself, but the assumption that the same tool must also serve the second and third phases. At some point the nature of what you need changes: from "something that works quickly" to "something that always works, for 80 people, on 14,000 records, with our own logic". Airtable was not built for that.

Six limits that scale-ups and growing SMEs run into

The six limits below are the most common reasons why organisations decide to migrate away from Airtable. Not all six need to apply; two or three are often enough to make the business case add up.

  • 01
    Per-record pricing that suddenly spikes

    Airtable charges per seat and per record cap within a base or workspace. As soon as your operations team grows from five to thirty users, or your customer database passes the Pro plan limit, your annual bill shoots up. We see organisations ending up at enterprise level with invoices that are four or five times higher within a few years, while the underlying database volume is still modest in absolute terms. Self-hosting with PostgreSQL or MySQL and your own front end costs a fraction of that seat pricing once you go beyond a dozen or so users.

  • 02
    Automation limits at tier level

    Automations have a monthly runs budget per workspace. On a tier without a generous budget, it is used up quickly as soon as you run nightly syncs or receive webhook triggers from an external application. Automations are also limited in steps, condition logic and error handling: a failure halfway through a chain is not always visibly logged, and complex branching quickly becomes unreadable. For business-critical orchestration, that is too fragile.

  • 03
    Complex relationships and data integrity

    Linked records work for light relationships, but they are no substitute for a true relational database. Cascading deletes, transactional consistency, foreign key constraints and complex joins are missing. A change to a linked record can cause rollups to be recalculated incorrectly, a duplicate entry can sit unnoticed next to a correct one, and a report that joins tables together quickly requires a Script or an external BI tool. For a serious relational domain, such as orders with lines, products and discount tiers, you will not get away with it.

  • 04
    Mobile app UX that can't keep up

    The Airtable mobile app and Interface Designer offer a functional view, but not a native experience. For a field worker who needs to quickly fill in a form with poor reception, attach a photo and add a GPS location, that is too slow and too sensitive to connectivity. A Progressive Web App (PWA) or custom native mobile app, with offline caching, camera integration and push notifications, is incomparably more productive in these scenarios.

  • 05
    Custom business logic limited by Scripting

    Airtable Scripting (JavaScript) and the Scripting app in extensions give you some room to program, but within strict sandboxing and without real unit tests, version control or CI/CD. A complex pricing model, an approval workflow with SLA monitoring, or an integration that needs headers, OAuth tokens and pagination logic: you cannot build that robustly in a Script block. At some point you end up programming anyway, just in the most difficult environment there is. A custom backend in Node.js, Python or another modern stack is then easier to maintain, test and document.

  • 06
    Vendor lock-in and EU residency

    Airtable is a US SaaS provider and your data sits on their infrastructure. For the public sector, healthcare, legal services, or organisations that must be able to demonstrate EU residency under GDPR or industry guidelines, that is a fact you cannot negotiate away. What's more, the more logic, automations and interfaces you build on Airtable, the more expensive any eventual migration becomes. It is a form of debt that grows over time. In such contexts, moving early to custom software with EU hosting is not a luxury but a compliance necessity.

How a migration from Airtable to custom software works

The biggest fear with a migration is unplanned loss: lost records, lost views that nobody recognises any more, lost automations that suddenly stop running. That is why our approach is transparent and step by step. We don't switch Airtable off until the custom software is in production and has been validated by your end users.

In practice we follow four phases, each delivering a concrete, verifiable result.

1. Data inventory and API export

We begin with a full inventory of your Airtable workspace. Which bases are there, which tables, fields and views, which linked records, which automations, which external integrations? The Airtable REST API returns JSON records per table, which we export in batches to a staging database (PostgreSQL or MySQL) where we remodel the relational structure. We retrieve file attachments via the file URLs the API returns and migrate them to S3-compatible object storage in an EU region. For every field type we create a mapping rule: a single select becomes an enum, a linked record becomes a foreign key, and a multiple select becomes a join table.

2. Automation and business logic redesign

Automations are often the trickiest part. In Airtable, an automation is a fixed chain of triggers and actions, sometimes supplemented with scripting steps. We document each automation as a use case ("when X happens, then Y, unless Z") and translate it into back-end code in your new application. Some automations we replace with database triggers, some with background workers (queues), and some with event-driven services. The result is more robust and testable, with no failures you only notice when a customer calls.

3. Views become pages: UI redesign

A Grid view, Kanban view or Calendar view in Airtable becomes a dedicated page or dashboard in a custom build, using the same mental structure your team already knows. We deliberately reuse the filters, grouping and columns that exist in Airtable, so the switch is as little disruption as possible for your staff. Where Airtable had limitations, such as no tailored mobile UX, no role-based access and no built-in reporting, we build it in properly from the start. That is exactly what a custom frontend in React, Vue or Svelte makes possible.

4. Running in parallel, validating, switching over

During the final phase, your new application runs in parallel with Airtable. Records sync in both directions via a temporary sync layer, and end users are migrated in batches (first one department, then a team, then the whole company). Only once all workflows have been validated do we switch Airtable off. Your historical data is retained, and we set the Airtable workspace to read-only so there is a fallback during the first few weeks. This sounds cautious, and it is. Business-critical work deserves that caution.

Use cases where custom software pays for itself quickly

Not every Airtable base needs replacing. A departmental tool with fifty records and three users that plans a monthly newsletter can stay where it is. But for the following patterns, custom software is usually cheaper and stronger than the Airtable version within twelve to eighteen months.

A CRM-light that grows into a real CRM

You started with a base for leads and deals. Now it holds twenty thousand contacts, twenty-five sales staff work in it, and you want email tracking, call logs, automatic lead scoring and integrations with your accounting and marketing automation. At that point, a custom CRM built on your exact sales process and integrated with your email tool and invoicing software is substantially cheaper than a Pro or Enterprise tier, and finally gives you the reports your management team is looking for. Read more about building custom CRM software.

Project or task tracker with SLAs

You use a base as a project management tool. Three departments, twenty active projects, deadlines with dependencies. By now your process is complex enough that you want resource planning, capacity management, time tracking and SLA monitoring, and those are exactly the areas where Airtable starts to creak. A custom workflow web app with state machines, audit trails and role-based permissions gives your team the backbone it needs.

Content calendar with publication workflow

An editorial or marketing team plans articles, podcasts, videos and social posts. An editorial workflow with versions, review rounds, deadline monitoring and multi-channel distribution quickly becomes unwieldy in Airtable. A custom content platform, often linked to your CMS, video platform and social media tooling, automates the entire chain from briefing to going live and keeps track of what is in which phase.

Inventory and product register

You manage thousands of products, suppliers and SKUs in a single base. By now you are syncing manually with several webshops, running overnight stock updates and relying on Automations that fail at peak times. At that point, a dedicated inventory management web app with real-time sync to Shopify, WooCommerce or your own webshop is not a luxury but an operational necessity.

The technology we use to build Airtable replacements

The stack depends on your use case, but the pattern is usually the same: a relational database as the source of truth, an API layer that all clients (web, mobile, integrations) rely on, and a modern frontend that replaces the Airtable views with dedicated pages.

For the database we use PostgreSQL or MySQL by default, hosted in the EU. For the backend we choose Node.js (NestJS), Python (Django, FastAPI) or, in some cases, .NET, depending on your existing ecosystem. We build the frontend with React, Vue or Svelte, depending on the complexity of the UI and which skills suit your own team. Background workers and queues run via Redis with BullMQ or via a message broker such as RabbitMQ. For object storage (the Airtable attachments) we use S3-compatible providers with EU residency.

Importantly, we stay as close as possible to open standards, so that this stack can also be migrated later if your scale or context changes. No vendor lock-in 2.0.

PostgreSQL MySQL Node.js / NestJS Python / Django FastAPI React Vue Svelte REST & GraphQL Redis / BullMQ Docker S3-compatible (EU) OAuth2 / SSO

Why Appfront for your Airtable migration

Honest about when you should not migrate yet

A migration is an investment. We are the first to tell you that a base with thirty records and two users can happily stay in Airtable for years. Our advice follows your business case, not our revenue.

Hands-on data migration

Not a theoretical migration plan, but actual export pipelines, mapping scripts and validation reports. We show that every record in the old world has been found in the new one, before you cancel Airtable.

EU hosting as standard

Our clients host in the EU by default: the Netherlands, Frankfurt or Dublin. For the public sector, healthcare or legal services, we explicitly configure setups without US subprocessors wherever possible.

Frequently asked questions about replacing Airtable

When is it sensible to replace Airtable?
Usually when two or more of these signals coincide: more than fifteen active users per workspace, a base with tens of thousands of records, repeated Automation failures, EU data residency requirements, or mobile workplaces that lack a native experience. A single pain point is rarely enough, but two or three at once make the business case. We are happy to work through it with you in an initial conversation.
Can we keep our Airtable data during the migration?
Yes. All data, including records, attachments, metadata such as created/modified timestamps, user roles and view configurations, is exported via the Airtable REST API and loaded into a new relational database. We migrate file attachments to EU S3-compatible object storage. Validation reports show that the number of records and files matches exactly between old and new before you cancel Airtable.
How long does a typical migration take?
For a small base (1-3 tables, few Automations, around 10 users), typically six to ten weeks. For a complex workspace (10+ tables, dozens of Automations, integrations with external systems, 25+ users), three to six months. We work in sprints so you see interim results after every iteration.
Do we have to rebuild our Automations?
Not from scratch. We document every Automation as a use case and re-implement it as backend code (database triggers, background workers or event-driven services). The end result is more robust and testable: a failure condition shows up in monitoring instead of only when a customer calls.
What happens to our Interface Designer pages?
These are replaced by dedicated pages in your new application. Where possible we keep the mental structure (which filters, which groupings, which columns) identical, so your end users have as little to get used to as possible. Where Interface Designer had limitations, such as no native mobile UX, limited role permissions and no built-in reporting, we improve things straight away.
Can we run both systems in parallel for a while?
Yes, and we recommend it. During the final phase, we synchronise records in both directions via a temporary sync layer. We migrate end users in batches (first one department, then a team, then the whole company). Only once everything has been validated do we switch Airtable off, keeping a read-only copy as a fallback.
How do you handle integrations that currently run to Airtable via Zapier or Make?
We document every integration and, depending on volume and complexity, replace it with direct API integrations, webhooks or (for simple flows) the same Zapier/Make scenarios pointing at updated endpoints. For business-critical integrations we build natively: faster, cheaper at volume and with better monitoring.
What if we want to change something again later?
Our stack is deliberately open: PostgreSQL, REST/GraphQL APIs, Docker and standard frameworks. If you want to switch to another solution in three years' time, or bring a team in-house, you can do so without vendor lock-in. The code and database are yours, and we provide documentation so that another team can take over.

Hitting the limits of Airtable?

Talk through your situation with us. Together we'll map out which bases, Automations and users add the most value when migrated, and which can happily stay in Airtable. No obligation.

Book a migration call

Edit content