Syntica
Pricing
About
Get started
OverviewAgentsConsultancies and agenciesInternal teamsPricingDocsGuidesBlogSecurityAbout
Migration: SAP Build Apps

SAP Build Apps retired 23 March 2026.
The applications still have to run somewhere.

SAP Build Apps is no longer maintained. SAP already told you what happens to the frontend. This is what happens after: where the converted application runs, who patches it, and what you own when the migration is done.

What SAP's tool does, and what it leaves undone

SAP's own migration path converts the pieces it can see. It does not extend to the pieces around your application.
SAP's official migration tool
Here
Converts the Build Apps frontend into React or SAPUI5 source
Nothing to convert: we don't touch the frontend, that part is SAP's tool
Hands you back source files, not a running application
A real environment per project the converted frontend can actually run on
Says nothing about a backend, a database, or where either lives
Your agent builds what the low-code backend used to do, in a repository you own
No answer for who hosts, patches or backs up the result
We run the instance. Backups and machine tier are yours to choose per environment
SAP's tool is the right first step for the frontend. It was never meant to answer where the application lives afterward: that's the part we do.

How the first one goes

The first application is the one that teaches the team the pattern. The rest go faster.
01
Inventory what is actually used
Most retiring platforms carry applications nobody opens. Decide what gets rebuilt, what gets archived, and what quietly stops.
02
Rebuild one, in code
Start with a single application your team knows well. Build it with the coding agent your team already uses (we support Claude Code, Codex, and Copilot CLI today) or by hand, in a repository you own.
03
Run it side by side
Deploy to a dev environment, then staging, then production when the people who need it are ready. The old platform keeps running until you switch over.

What teams ask first

What happens to the code if we leave you too?
The repository is always yours. Delete the application and the git repo is untouched: clone it, move it, self-host it, or hand it to the client. That is the whole point of the exercise.
Can someone else hold the repository instead of us?
Yes. Ownership is organisation-scoped, so the work can run in the client's or the business's own organisation with your people as members, or in yours, and be handed over later.
What does it cost per application?
A development environment is free. Beyond that you pay for the machine tier each environment runs, plus backups and outbound traffic. We're in early beta and are not publishing per-tier rates yet. Pricing will be usage-based, never metered per credit or per token.
Where does it run?
In the EU: eu-central-1 (Frankfurt), on a dedicated instance per environment. That is the only region we run today: good for data residency if your data must stay in the EU, and worth raising early if it must sit somewhere else.

Bring us the Build Apps applications on your list.

Tell us how many are still in use, and we will tell you honestly whether we are the right place for them to land.
Talk through a migration
Syntica
Real environments for client work. Your code. Your repo. No lock-in.
Product
PricingRelease notes
Who it's for
Consultancies and agenciesInternal teamsMigration
Developers
DocsStatus
Company
AboutSecurity and governanceBlogContact
© 2026 Syntica. All rights reserved.
Privacy PolicyTerms of Service
We use cookies
We use essential cookies to run the site and optional ones to understand usage. See our Privacy Policy.