Emergent says you own what you build, and the stack underneath is familiar: React or Next.js on the front, Python or Node APIs behind it, and MongoDB for data. Moving an Emergent app means handling code, data, secrets and sign-in as separate jobs, then proving the app starts outside Emergent.
This guide covers how the code and data each leave, what the code export leaves out, three things to check first, and a step-by-step checklist.
How your code and data leave
Saving to GitHub is on Standard plans and above. On any plan you can browse and copy files from the code view, though Emergent says there's no download button, so copying a large project by hand is slow and easy to get wrong.
- Source code, through GitHub or by copying files
- MongoDB data, through a separate export
- Per-collection CSV files from the Database Viewer
What the code export leaves out
- Environment variables and secrets
- Database contents, which need their own export
- Emergent Auth sign-in, if your app uses it
- The Universal LLM Key, if your app's AI features use it. You'll need your own AI provider account after the move.
Three things to check first
1. The route to your data
Emergent's documentation isn't consistent here. One help page says you can export with mongodump or Compass at any time, after allowlisting IPs if needed. Its FAQ says production export isn't currently self-serve and the managed cluster rejects external connections. Find out which applies to your app before you plan anything else.
2. Platform backups aren't your restore plan
Emergent keeps routine production backups for platform resilience, and says they aren't a self-serve restore service. Before any move, make sure you have your own copy of the data.
3. Live edits have no undo
Emergent notes that its Database Manager edits live data with no undo, and that deleting a project permanently removes the code and the database. Export first, and keep the original project until the new app has proved itself.
Emergent offers Pro users with a published app a move to a MongoDB Atlas cluster they own, on a dedicated M10 cluster or higher. That gets your data into your own account, but going back requires contacting support, so make the decision deliberately.
A step-by-step Emergent exit checklist
- Check your plan. Save to GitHub needs Standard or above.
- Get the code into your own repository.
- Confirm the data route. Work out how your MongoDB data can be exported today, and take your own copy.
- Rebuild the configuration. List every secret, sign-in method, AI key and storage location, and set each up in accounts you own.
- Restore a fresh data copy to the destination database and verify it, including any object and file storage.
- Start it outside Emergent. Deploy to your new host and check the core workflows.
- Plan the final data copy and domain change, and keep the Emergent project until you trust the new app.
If you'd rather hand it over, every Emergent web app is a flat $199 with AppExit, code and database included, whatever its size. The Emergent migration guide shows how we handle each step.
Frequently asked
Which Emergent plan do I need?
Save to GitHub needs the Standard plan or above. Lower plans can still copy files from the code view, which is slower and more error-prone for a large project.
Can I move an Emergent mobile app?
Mobile projects need their own review and are quoted separately. See mobile app migration.
Where should a MongoDB app go?
Somewhere that supports MongoDB and your API runtime. Our guide to where to host after leaving an AI builder compares the options.
Sources
Vendor documentation checked November 2026. Plans and export paths can change. AppExit is not affiliated with Emergent.