Migration guide
Replacing SAP Build Apps after its deprecation
SAP deprecated SAP Build Apps (the former AppGyver) on 23 March 2026 and removes it from its eligible services list on 30 September 2026. SAP has said existing apps cannot be migrated and must be rebuilt. If you built a departmental tool on it, you need a new home for it now.
Emberblocks fits the kind of app most teams built there: forms, lists, approvals and trackers over business data. This guide covers what maps, what does not, and how to get the rebuild done in a few days.
Builders are always free. Facts about SAP Build Apps on this page were last checked on against SAP Build Apps's own site. Tell us if something is out of date: hello@emberblocks.com.
What SAP announced
The deprecation was published on 23 March 2026 as part of a portfolio simplification. The product leaves the eligible services list on 30 September 2026. SAP offered no automated migration; apps are to be rebuilt on other SAP Build tooling or elsewhere.
That leaves teams with two kinds of app: integrations into SAP systems, which belong on SAP's remaining tools, and ordinary business apps over a database, which is where Emberblocks comes in.
Does your app fit?
| Capability | Emberblocks | Notes |
|---|---|---|
| Forms, lists, detail pages over a database | Yes | the core of Emberblocks |
| Approvals and status workflows | Yes | workflows on row changes, buttons and schedules |
| Role-based access | Yes | views and fields per role |
| Data in Postgres or HANA Cloud (Postgres-compatible) | Postgres, yes | connect it directly |
| Data in SAP S/4HANA via OData | No | no OData connector; replicate to Postgres first |
| Native iOS and Android builds | No | web app that installs to the home screen |
| Custom JavaScript components | partial | custom blocks and a run-code workflow step |
| SAP BTP authentication | No | email, password and Google sign-in |
Rebuild in Emberblocks
- 1
Export the data model
List the entities your app read and wrote. If they live in a Postgres-compatible database, connect it. Otherwise export them as CSV and import them into built-in tables.
- 2
Describe the app to Ember
A paragraph describing the screens and who uses them is enough for a first draft of tables, views and workflows, which you review before creation.
- 3
Rebuild pages as views
Each SAP Build Apps page becomes a view of blocks. Lists become table or card blocks, detail pages record blocks, dashboards stat and chart blocks, and forms form views.
- 4
Recreate logic as formulas and workflows
Formula fields replace computed properties. Workflows replace logic flows for approvals, notifications and updates.
- 5
Set roles and publish
Assign users to roles, publish a versioned snapshot and send the link. Roll back in one click if needed.
What you get in Emberblocks
Your data, live
Start on a built-in database, your own Postgres (Supabase, Neon, RDS, anything that speaks Postgres) or an Airtable base. Apps read and write live rows, so there are no exports to keep in sync.
Blocks on a grid
Drag tables, cards, record pages, kanban boards, calendars, maps, timelines, charts, stats, forms, buttons, comments, activity feeds, file viewers, signatures, barcodes and embeds onto a grid and wire them to tables. What you arrange is exactly what your team gets.
Real field types
Fields include text, email, phone, URL, number, boolean, date, date-time, time, duration, select, multi-select, reference, multi-reference, image, file, signature, address and JSON. Barcode scanning and signatures work in the browser without a native app.
Workflows
Workflows run when a row is created, updated or deleted, on a schedule, or from a button; steps update records, send email, call webhooks, branch on conditions and run code.
Roles and permissions
Roles decide which views a user sees and which fields they can read or edit; app users can be loaded from a table in your own data.
Publishing like software
Every publish is a versioned snapshot you can inspect and roll back, with a stable and a latest channel.
Phones and offline
Published apps are responsive, install on a phone's home screen, and queue edits made offline until the connection is back.
AI where it helps
Ember drafts a first version of an app from a plain-language description, and end users can ask questions of the data in plain language when you turn it on.
Questions
- Can Emberblocks connect to SAP systems?
- Not directly. There is no OData or RFC connector. If the app's data lives in a Postgres-compatible database, connect that; otherwise replicate the tables to Postgres or import CSV.
- How long does a rebuild take?
- A departmental app of a handful of screens is typically rebuilt in a few days including data import and testing, because the blocks already handle lists, filters, forms and permissions.
- Where does my data live?
- Wherever you want it. Use the built-in database, connect your own Postgres so rows never leave your server, or point an app at an Airtable base. Airtable bases are mirrored into Postgres and kept in sync both ways.
- Do I need to write code?
- No. Blocks, a spreadsheet-style formula language and visual workflows cover most internal tools. A run-code workflow step is there when you want it, and an MCP server lets AI assistants build and query apps for you.
- How is Emberblocks priced?
- Builders are always free. Paid plans are priced by the number of people who sign in to your published apps: Starter $29, Pro $79 and Business $199 a month billed yearly. Every new workspace starts with a 14-day Pro trial, no card needed, and there is a free plan after that. Full details on the pricing page.
- What does Emberblocks not do yet?
- Custom domains, SSO and an Enterprise plan are not available yet. There is no live Google Sheets connector (import the sheet as CSV instead). Apps run in the browser and install to the home screen; there are no App Store or Play Store builds.
Try it on your own data.
Every workspace starts with a 14-day Pro trial without a card. You can also open a template in the editor first and sign up only when you want to keep it.