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 AppSheet can go
There is rarely one right answer. On the call we pick the path that keeps your team working the whole way through.
Import the app definition
The importer reads AppSheet's Application Documentation file and shows a coverage report before anything is created, so you know the gaps up front.
Bring the rows
Export each table as CSV into the matching Emberblocks table, or connect the Postgres database the data already lives in.
Rebuild what did not carry over
Bots become workflows, untranslated expressions get rewritten, and you run both apps side by side for a week before switching.
What we go through on the call
The coverage report
Which tables, views, slices and actions import cleanly and which expressions need rewriting.
Bots and automations
Which bots become workflows on row changes or schedules, and which are no longer needed.
Security filters and roles
How your users table, roles and per-user filters map to Emberblocks roles and record filters.
Phones in the field
Home-screen install, offline edits, barcode scanning and signatures in the browser, checked against how your team works.
When we will tell you to stay on AppSheet
An honest fit check means saying no sometimes. These are the usual reasons.
- Your app depends on Apps Script or Google-only integrations. There is no equivalent.
- Your data must stay in Google Sheets and be edited there by other tools. Emberblocks has no live Sheets connector.
- You need native App Store or Play Store apps. Emberblocks apps install from the browser.
Rather do it yourself?
The step-by-step guide covers the same ground. You can book the call later if you get stuck.
Questions
- Can I just run the importer myself?
- Yes. The importer is self-serve and most single apps move in an afternoon. The call is for when the app is large, business-critical, or you want a second pair of eyes on the plan.
- 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
- Guide: migrate from AppSheet
- AppSheet alternative
- Emberblocks vs AppSheet
- Migration help: Airtable
- Migration help: Google Sheets
Facts on this page were last checked on . Tell us if something is out of date: hello@emberblocks.com.