- For one team with a clear process, Airtable or Smartsheet is often all you need. Use it.
- Every plan sets hard limits on records, sheet size, automation runs and history. Know yours before you reach them.
- The real warning signs are visibility rules, outside users and logic spread across dozens of automations.
- A custom tool earns its cost when many roles, rules and systems meet in one place.
- You can move one workflow at a time and keep the database tool for what it does well.
Where they shine
Airtable is a database that feels like a spreadsheet. Smartsheet is a spreadsheet built for projects and work tracking. Both give teams real field types, forms, shared views and simple automations, with no developer involved.
That's a big step up from a shared spreadsheet, and for many teams it's the right place to stop. They shine when:
- One team or department owns the process.
- Records number in the thousands or tens of thousands.
- The people using it are mostly inside your organization.
- The rules fit in a sentence or two.
- The process is still changing while you figure it out.
That last point is underrated. Early on, nobody knows the right fields. A tool where anyone can add a column in a minute is exactly what you want. Custom software that locks in the wrong process too early is worse than either.
The limits are real, and written down
Every plan has ceilings. Airtable caps records per base at 1,000 on its free plan, 50,000 on Team and 125,000 on Business. Automation runs are counted per workspace each month, and failed runs count too. Record revision history is kept from two weeks on the free plan to three years on Enterprise Scale.
Smartsheet caps a standard sheet at 20,000 rows and 500,000 cells. Larger sheets, up to 100,000 rows, are available on Enterprise plans.
These limits are generous for most teams. The trouble is what teams do when they get close. They split one base into three, archive records they still need, or push old data back into a spreadsheet. Each workaround makes the next problem harder.
Signs you've outgrown them
You're working around the limits
Splitting bases, deleting history to make room, or planning the year around the next tier. The tool is now setting the shape of the work.
Visibility doesn't match your org chart
Both tools are good at controlling who can edit. Controlling who can see what is harder. Airtable's own help notes that field and table editing permissions "do not affect who can see information in the base". If sales shouldn't see margins, or one region shouldn't see another's customers, you end up with separate bases or synced copies, and copies drift.
Automations have multiplied
Twenty small automations, each set up by a different person, each firing on a field change. Nobody knows the order they run in. A change to one field sets off three of them, and one of them emails a customer.
People join tables by hand
Linked records help. But when someone exports two tables every Monday to match them in Excel, the tool has stopped modeling how the business works.
Outside people need access
Customers, suppliers, contractors. Seat-based pricing and permission models built for internal teams get awkward fast when the users are outside your walls. A portal built for them is a different product.
You need a real audit trail
"Who changed this price, and what was it before?" Revision history helps, but its retention window depends on your plan. Some disputes and some customers need a longer, uneditable record.
It has to work with your core systems
Accounting, inventory, your customer database. Sync tools exist, but once the base becomes the hub between three systems, you're running a connection project inside a database tool. Our guide to replacing spreadsheets covers the earlier rungs of this ladder.
Side by side
| Question | Airtable or Smartsheet | Custom internal tool |
|---|---|---|
| Time to first version | Days | Weeks to months |
| Who can change it | Anyone with creator access, instantly | A developer, through a planned change |
| Data size | Plan-based caps on records or rows | Set by your database, not a plan |
| Who sees what | Strong on editing rights, weaker on visibility | Built around your roles, down to the field |
| Outside users | Possible, often costly and awkward | A portal designed for them |
| Rules and logic | Formulas and many small automations | Enforced in one place, with tests |
| Change history | Retention window set by plan | Kept as long as you decide |
| Cost shape | Per seat, rising with plan tier | Build cost up front, then hosting and upkeep |
| Best fit | One team, changing process, internal users | Many roles, outside users, money or long history |
Moving without stopping work
The base is live. People add records every day. You don't need a big switch-over weekend, and you shouldn't plan one. A few principles keep the move safe.
Map what the base actually does. Every view, filter, formula, automation and linked table encodes a rule. So does every person who opens it. The mapping always turns up something nobody mentioned.
Move one workflow first. Pick the one that hurts most: the visibility problem, the outside users, the automation that keeps misfiring. Leave the rest alone.
Run them side by side, briefly. Compare results for a few weeks. Each difference is either a bug or a rule nobody wrote down.
Decide what stays. Not everything has to move, and each kind of record should have exactly one home.
Two made-up examples show how this plays out.
An 80-person engineering firm tracks projects, staff assignments and client billing in one Airtable base with 14 tables and 30 automations. It's close to its record limit, and clients keep asking for project status. Billing and client access move to a custom tool connected to accounting. Staff scheduling stays in Airtable, where the team likes it, and feeds the new tool one way.
A manufacturer plans product launches in Smartsheet, and it works well. Its quality issues log, kept in other sheets, is near the row limit and needs a full change history for customer audits. Only quality tracking moves.
How long each step takes and how much history to bring over depends on your base. That's why the mapping comes first.
The middle path
Keeping Airtable or Smartsheet for some work while a custom tool handles the rest is common and sensible. The database tool stays great for fast-changing, team-owned work. The custom tool takes the parts with strict rules, outside users, money or long history. The one thing to avoid is the same record being edited in two places.
A common split looks like this. The custom tool owns customers, orders, prices and anything an outsider sees. The database tool keeps planning boards, internal trackers and experiments. Data flows one way between them, on a schedule everyone knows. When a new idea in the database tool proves itself and starts carrying real weight, it becomes a candidate for the custom tool. Until then, it stays where it's cheap to change.
What most guides miss
Flexibility is the feature you'll miss. People added a field whenever something new came up. If the new tool has no safe outlet for that, shadow bases appear within months.
Seat counts change the math. Occasional editors and outside users can cost more each year in a seat-based tool than a simple screen built for them.
Don't rebuild the base. A custom tool that copies every table and view keeps every workaround. Rebuild the process, not the layout.
Cleanup is half the value. The move is your best chance to merge duplicates and drop fields nobody uses.
How we do it
We start by mapping your base or sheets with the people who use them. If Airtable or Smartsheet is still the right home, we'll tell you, and help tidy it. When it isn't, we build a custom internal tool for the workflow that hurts most and leave the rest where it works. We also stay on after launch to support and extend the system as your team and process change. Tell us what your base does today and we'll tell you what should move.
