Case study · Group travel
A group travel company moves off Airtable onto Supabase and Retool
This Los Angeles company runs complex group travel: touring, corporate and leisure trips. Its operations lived in Airtable, including every traveler’s passport and driver’s licence details. We designed a relational database on Supabase, migrated the data and about 1,300 file attachments, kept Airtable and Supabase in sync during the move, and built the Retool apps the team now uses every day.
The challenge
What wasn’t working
Group travel runs on details: who is travelling, for which client, and whether each person’s passport and licence are valid for the trip.
All of it sat in an Airtable base whose structure carried the company’s business logic, plus about 1,300 attached files. Moving it couldn’t lose any of that.
The team also needed honest numbers. Their client list showed eight clients, but the figure that mattered was how many had at least one active traveler.
The solution
What we built
A schema that fits the business
A relational PostgreSQL schema on Supabase, designed from how the Airtable base was really used, not just how its tables looked.
Data and file migration
Records and about 1,300 file attachments moved from Airtable into Supabase.
Incremental sync
Airtable and Supabase stayed in sync during the switch, so the team could keep working while the new system came in.
Traveler and document app
Retool screens for traveler records and passport and driver’s licence updates. A form only resets and closes once every update has saved; if one fails, nothing is lost and the user can retry.
Operations dashboard
Total travelers, passports waiting for review, passports expiring in the next 90 days and active clients, all counted from active, non-deleted records and each traveler’s latest passport.
Written handoff
Documentation and a walkthrough at the end, so the team knows how the system works and how to change it.
How it works
How the move was run
- 1
Learn the base
We mapped how the business used Airtable before designing anything.
- 2
Design the schema
A relational schema on Supabase, reviewed with the client.
- 3
Migrate and sync
Data and files moved across, with incremental sync running during the switch.
- 4
Build the apps
Retool apps for traveler documents and the operations dashboard.
- 5
Hand over
Each of the five milestones was approved, then documentation and a walkthrough.
Screens
Inside the build
Real screenshots from the project. Client names, logos and personal details are blurred.

The result
What changed
- All five milestones completed and approved by the client
- About 1,300 file attachments migrated from Airtable
- The Retool apps are in daily use
- Dashboard figures follow written rules, so the counts match how the business thinks about its clients
“What stood out most was how well they understood the shape of our business, not just the technical ask.”
More work
More case studies
House Of Sylas: from a backlog of Google Sheets to apps for the team and its partners
Read the case study →Finance operationsAI invoice and expense automation that files itself
Read the case study →Operations & dataTurning a drive full of PDFs, scans and spreadsheets into clean data
Read the case study →Have a project like this?
Tell us what you need to build. In 30 minutes we’ll map what to build first and follow up with a fixed-scope estimate.
Official Retool Agency Partner5.0 on Clutch, 9 reviewsBuilding software since 2015Reply within one business day