Which AI app builder are you migrating off?
Each builder lets go of an app differently, so there is one page per builder: what the export actually contains, what needs a plan of its own, and what it costs each month to run the result yourself.
The shared part of the story is the same whichever builder you used. The code is usually the easy part. The state, meaning user accounts, uploaded files, secrets and whatever the builder wired up for you, is where the work tends to live. And the question of what you would still have if the vendor changed direction is worth asking before anything else, because one of the builders below has already done so.
Each page carries that shared argument and adds what is specific to its builder, checked against the builder's own documentation on the date shown at the foot of the page. If your builder is missing from the list, the Lovable page is the closest general guide, and we are glad to look at one we have not written up yet.
BOLTBolt can push your project to GitHub or download it as a zip; secrets and the database are separate jobs.
> CODE LEAVES BY GIT SYNC OR DOWNLOAD
EMERGENTEmergent's paid plans let you download the code or connect GitHub; the app is React, FastAPI and MongoDB, so the database side differs from a Postgres move.
> CODE LEAVES BY GIT SYNC OR DOWNLOAD
LOVABLELovable syncs your code to a Git repository on every plan; the Supabase database, user accounts and uploaded files need their own export.
> CODE LEAVES BY GIT SYNC OR DOWNLOAD
REPLITReplit projects download as a zip or sync to a GitHub repository; the Postgres database exports with pg_dump, and secrets and integrations stay behind.
> CODE LEAVES AS A DOWNLOAD
RIFFThe Databutton-era builder your app was made with is no longer offered; Riff's docs describe a zip code export and nothing about database export, so this page starts from the deprecation.
> CODE LEAVES AS A DOWNLOAD
ZITEZite's help centre describes export as a move between Zite accounts and its FAQ said the code will not run outside Zite, so leaving means taking the data out as CSV and rebuilding the app, with the running app as the specification.
> NO RUNNABLE CODE EXPORT
Unsure which kind of migration yours is, or whether to migrate at all? A short technical discovery call is usually enough to say, and we are glad to say if staying put is the better answer.