9 Things To Know Before Switching From Airtable

Your Airtable base has fifteen tables, six interfaces, and three automations that only one person on the team actually understands. Last month a subcontractor filled out the wrong form, a client saw a view meant for internal eyes only, and the monthly bill went up again because two more field techs got added as editors.

And with Airtable's acquisition by Bending Spoons this August, more teams may be taking the opportunity to reassess the systems they rely on.

None of that means Airtable failed you. It means your business grew past what a single base was built to handle: more teams, more job sites, more clients asking for their own view of the work. That's when a database starts needing an operational layer around it.

Here is what to check before you commit to switching, so the move fixes the actual problem instead of just moving it somewhere new.

TL;DR

• Airtable charges per editor. Once field staff, subcontractors, and clients all need access, that bill grows faster than your headcount.
• Airtable caps records and attachment storage by plan. Job photos, inspection logs, and asset histories fill that up faster than most teams expect.
• Switching does not have to mean deleting your base. Most teams keep Airtable as the data layer and build a better app around it, or move the data over gradually.
• Permissions, who can see what across sites, clients, and vendors, are usually the real trigger, not Airtable itself being "bad."
• A well-scoped switch takes weeks, not months, because your data does not have to move on day one.

1. How much does Airtable actually cost once your teams, subcontractors, and clients all need access?

Airtable prices by seat. A handful of internal editors is cheap. The moment you add field technicians, subcontractors, and client contacts who need to log or view real data, not just look at a shared link, the bill scales with every person you add, not with the value they get from it.

This is the exact wall Redrock Entertainment hit. Jesse VanDenKooy, their Technology Solutions Architect, put it plainly: "We needed a simpler way to keep Airtable as the source of truth while giving employees, vendors, and clients controlled access to it. Noloco gave us a more robust front end to unlock new capabilities and reduce costs. We've probably cut our annual software cost by about 60%."

The fix is not to limit who gets access. It is to separate the cost of adding a person from the cost of adding a seat. A full breakdown of what different team sizes actually pay is in our Airtable pricing guide.

2. What limits will you hit first: records, attachments, or automation runs?

Every Airtable plan has a ceiling. For a construction, logistics, or industrial team logging jobs, assets, and site photos every day, you hit these limits faster than a typical office team does.

Source: Airtable plan limits, verified August 2026.

Attachment storage is usually the first thing to go for field-heavy teams. Every job site photo, signed work order, and inspection PDF counts against that base limit. Once a team is uploading photos from every site visit, 1 to 20 GB disappears faster than most people plan for.

Record count catches up next. If you are logging every job, asset, or maintenance visit as its own row, and keeping the history instead of archiving it, 50,000 rows is not as far away as it sounds two years in.

3. Can Airtable's permissions handle who sees what across sites, clients, and vendors?

Permissions get harder when more than one type of person needs access.

Your field team may need to update a job. A contractor may only need to see their assigned sites. A client may need to check progress without seeing internal notes. Leadership may need the full picture.

Once all of those people are working from the same underlying data, controlling who sees and changes what becomes part of the system itself.

In practice, this can mean duplicate interfaces built just to hide certain fields from certain people. Or clients seeing internal notes they were never meant to see. Or having to rebuild a view just to make sure someone can only access records for a specific site or job.

These challenges sit alongside a broader data problem for field service teams. A 2025 field service industry survey found that 68% of field service leaders are concerned about data quality issues or siloed data. When information needs to be shared across teams, sites, clients, and vendors, controlling who can access and update it becomes an important part of keeping that data useful. (The 2025 State of Field Service Report, Geotab and Field Service Insights, 2025).

This is often where a simple internal tool starts to feel harder to manage. Your data may still work, but more people now need to interact with it in different ways. Your team update the work, contractors see their assigned sites, clients check progress, and leadership needs the full picture.

Noloco lets you build around those roles, so each person gets what they need to do their part without getting access to everything else.

And if you need more control, Noloco's permission model applies access rules at the data level, so the same rules follow the data wherever it appears instead of being rebuilt screen by screen.

This is usually the real reason teams look at switching, because permission logic that holds up when it is your data, your teams, and your clients in the same system is a different job than sharing a spreadsheet.

4. Does switching mean replacing Airtable, or keeping it as your data layer?

This is the decision most teams skip, and it changes everything about how disruptive the switch feels.

Both are valid, and you do not have to decide on day one. Noloco connects directly to your existing Airtable base, so the first move is changing how people work with the data, not a data migration. Plenty of teams run this way indefinitely. Others use it as a bridge while they move records over gradually, table by table.

5. What actually happens to your existing automations and workflows?

Automations built in Airtable do not transfer automatically, and Airtable's own automation runs are capped by plan, which becomes a real constraint once job scheduling, client notifications, and internal alerts are all running through the same base.

PFE Limited, a reliability engineering firm that runs vibration analysis and alignment services for industrial clients, ran into this using Airtable Interfaces. Jake Ford, a CAT IV Vibration Analyst on the team, used to spend nearly a full day preparing a single client report. "I can trim that to say three or four hours with Noloco," he said, a 50% drop in report time that let the team take on roughly one extra job per month without adding headcount.

The workflows themselves usually get rebuilt in the new system rather than copied over, since the goal is fixing the automation, not just relocating it. Noloco's workflow builder reads and writes back to the same underlying data, so the logic does not have to start from zero.

6. What other tools does switching let you get rid of, not just Airtable?

Airtable is rarely the only thing holding the operation together. Most growing engineering, construction, and logistics teams also run a separate project tracker, a CRM or quoting tool, and a spreadsheet or invoicing tool for the money side, all stitched together with Zapier, Make, or someone remembering to update three places by hand.

Switching is a natural point to ask a bigger question: are you replacing Airtable, or actually cutting the number of places someone has to check to get one straight answer? Inside Noloco's own customer base, 83% of our customers use one app to run several of these functions together, tracking clients, jobs, and reporting in the same place instead of stitching separate tools together with automations.

Before you switch, list every tool that currently talks to your Airtable base through an automation, an export, or a copy-paste habit. That list is usually the real scope of the project, not just "moving Airtable.

7. How long does a realistic switch take, and what does it disrupt?

Because the data can stay in Airtable while the interface changes around it, most teams are not looking at a multi-month migration.

AI can also change how quickly you get started. Instead of beginning with a blank screen or building every interface from scratch, you can use AI to help create the first version of the system around your workflow.

But building version one is only the start. The system still needs to work when teams, clients, contractors, and other roles start using it every day.

Packaging On Demand, a contract packaging company that moved off manual, paper-based logs entirely, had a working system live in 6 weeks. It covered production scheduling, a searchable receiving log with photos and timestamps, and role-specific views for customer service, procurement, and leadership.

The disruption is usually smaller than teams expect because the switch can happen in parallel with the existing base rather than as a hard cutover. The riskiest week is often the first one, when people are learning a new way to complete tasks they used to do on muscle memory. Plan for that week specifically: a short walkthrough for teams, and one person available to answer "Where did that field go?" questions.

The goal is not just to build something faster. It's to end up with a system your team can actually run the operation on.

8. Will your team actually use the new system, or drift back to spreadsheets and group chats?

Adoption fails for a predictable reason: the new system is harder to use for the actual daily task than the workaround people already have, even if it is "better" on paper.

This is where permissions matter again, in a different way. When people can only see and edit what applies to their job, the system feels simpler to them, not more complex, even though more is happening underneath. At PFE Limited, 60 to 70% of regular customers migrated over to the new client-facing app once it replaced the static reports they were used to, because the new version gave them something Airtable's PDF exports never could: a live view they could check themselves instead of waiting on an email.

Build the field-facing and client-facing parts first, not the internal reporting dashboards. The people who feel the pain daily are the ones whose adoption decides whether the switch actually worked.

9. How do you know if the switch was worth it?

Decide what you are measuring before you switch, not after, or you will end up judging the new system on vibes.

The teams who get clean answers track a small number of concrete things: time spent on a specific recurring task before and after (Jake Ford's report prep dropped from most of a day to three or four hours), software cost per active user rather than per login (Redrock's 60% cut came from removing per-seat Airtable pricing, not from cutting people out), and how many manual double-entries or corrected mistakes happen in a normal week.

If none of those numbers move within the first month, that is a signal to look at what got carried over unchanged, not necessarily that the switch itself was wrong.

Final thoughts

Airtable is not necessarily the problem; your operation may simply have outgrown the way people access it.

What started as a base for your internal team may now need to support field staff, contractors, partners, and clients. They all need to do different things, see different information, and work through the same process without getting in each other's way.

That doesn't always mean replacing Airtable. You can keep it as your data layer and build an app around the way your operation actually works. Or, if you've hit several limits at once, you can gradually move toward one system.

Either way, don't just ask whether the new tool can hold your data: Ask whether your team, clients, and partners can actually run the operation on it.

Frequently asked questions

Do I have to delete my Airtable base to switch?
No. Most teams connect a new portal builder tool directly to their existing base first, then decide later whether to migrate records fully. The data does not have to move for the workflow and permissions to change.

How long does switching from Airtable usually take?
For a well-scoped project, weeks rather than months is typical, since the underlying data can stay put while the interface, permissions, and automations get rebuilt around it.

Will my team need to learn to code?
No. Tools built on top of Airtable, including Noloco, are built for people who set up their own bases and automations without an engineering background.

What happens to automations I already built in Airtable?
They stay in Airtable unless you turn them off. Most teams rebuild the automations that matter in the new system as part of the switch, since that is usually when the underlying logic gets fixed too, not just moved.

Is Airtable good enough for a growing field service or industrial business?
For a small team with a handful of internal editors, often yes. The pressure usually shows up once teams, subcontractors, and clients all need their own access, since that is when per-seat pricing, record limits, and permission gaps start compounding at the same time.

Does switching mean giving up Airtable's flexibility?
Not necessarily. Keeping Airtable as the data layer underneath and build a portal around the people who actually need to use the data preserves the flexibility of the base while fixing the parts that were never built for field teams or client access.

Related resources

• Airtable pricing 2026: plans, hidden costs, and the best app builder for portals
• Custom field service software built on your existing data
• How PFE Limited cut report time in half without adding headcount
• Transforming construction management with Noloco