How it works
- 1
Tell us about the app
Two minutes: what it does today, roughly how many people use it and how soon you need to move. No account needed.
- 2
A 30-minute call
We look at your base, sheet or app together over a screen share and tell you straight whether Emberblocks is a good fit. If it is not, we say so and point you at what might be.
- 3
A written migration plan
What carries over on its own, what gets rebuilt, in which order, and a realistic time estimate. It is yours to keep whether you switch or not.
Ways a move from Airtable can go
There is rarely one right answer. On the call we pick the path that keeps your team working the whole way through.
Keep the base, replace the Interfaces
Connect the base as a data source. Emberblocks mirrors every table into Postgres with two-way sync, so your apps run on the same data while Airtable stays in place.
Move the data off Airtable
Bring the tables into Emberblocks' built-in database, or into your own Postgres, and retire the base once the apps are live.
Both, in that order
Start on the synced base so nobody's day changes, then switch the app's source to Postgres when you are ready. The screens stay as they are.
What we go through on the call
Tables and linked records
Which links become reference and multi-reference fields, and which lookups and rollups become formulas.
Interfaces and views
Each Interface page mapped to a block: tables, cards, record pages, kanban boards, calendars, charts and forms.
Automations
Which ones become Emberblocks workflows and which can keep running in Airtable while the sync carries their results.
Who sees what
Editor and commenter seats, current-user filters and client access mapped to roles, field permissions and public links.
When we will tell you to stay on Airtable
An honest fit check means saying no sometimes. These are the usual reasons.
- Your team mostly lives in the grid itself, editing like a spreadsheet, and rarely uses Interfaces. Airtable's grid is hard to beat for that.
- You depend on Airtable extensions or scripts that have no Emberblocks equivalent.
- You need SSO, custom domains or an Enterprise contract today.
Rather do it yourself?
The step-by-step guide covers the same ground. You can book the call later if you get stuck.
Questions
- Do I have to stop using Airtable to use Emberblocks?
- No. Emberblocks can run apps on your Airtable base with two-way sync. Many teams start there and only move the data later, or never.
- What does the call cost?
- Nothing. The call and the written plan are free, and there is no obligation to switch. Building in Emberblocks is free too; paid plans are priced by the people who use your published apps.
- Who will I talk to?
- Someone who builds Emberblocks, not a sales rep. Emberblocks is a small team, so the person on the call can answer the product questions directly and tell you what is and is not possible today.
- What should I have ready?
- Access to the thing you want to move, so you can share your screen, and a rough idea of who uses it and for what. A list of the parts people could not live without is the most useful thing you can bring.
- What does Emberblocks not do yet?
- Custom domains, SSO and an Enterprise plan are not available yet. There is no live Google Sheets connector, and apps run in the browser and install to the home screen rather than coming from the App Store or Play Store. We cover these on the call if they matter to you.
Thirty minutes, and you will know.
Whether Emberblocks fits, what the move involves and how long it takes. Or skip the call and start building: builders are always free and every workspace starts with a 14-day Pro trial.
Related
- Airtable alternative
- A front-end for Airtable
- Guide: moving off Airtable Interfaces
- Migration help: Google Sheets
- Migration help: AppSheet
Facts on this page were last checked on . Tell us if something is out of date: hello@emberblocks.com.