How to Export Your App from Adalo (What You Can Take With You)

If you searched "export app from Adalo," you want a button. One that hands you the code so you can take the app elsewhere. That button does not exist. As of 2026, Adalo has no code export you could open in another tool or hand to a developer. The app you built lives inside Adalo's system. (Check your plan and Adalo's docs before you act, since platforms change. But this has been true for years.)

Do not panic. The code was never the valuable part. You own the things the code was built around. That means your data, your users, your store listings, your brand, and your knowledge of what the app should do. All of that comes with you. This guide shows what you can export and how. It covers what you cannot take. It covers the account issue that decides if your move is smooth or painful. And it compares the three real rebuild paths. One note on tone first. This is not an anti-Adalo post. If you are here, Adalo did its job. You proved an idea, got real users, and outgrew the tool. That is a win. (Still deciding whether to leave at all? Start with our Adalo pricing breakdown and our Adalo troubleshooting guide.)

What you can export from Adalo, step by step

Do all of this first. Do it before you cancel or downgrade your plan. Once your plan lapses, getting back in to pull data is a pain at best. At worst it is a support ticket.

1. Export every collection to CSV

Your database is the most valuable thing in the app. It comes with you in full. As of 2026, Adalo lets you export each collection as a CSV file. Users, Orders, Bookings, whatever you have. You do it from the database view, one collection at a time. So:

• Open the database and list every collection, even the ones you forgot you made. That list is your data inventory.
• Export each one to CSV. Check the row counts against the editor so nothing got cut off.
• Watch the Users collection. Emails and profile fields export fine. Passwords do not. They are hashed, as they should be on any platform. So users will set a new password on the new app. Plan for that in your launch note.
• Store the CSVs somewhere safe, with the date. This is your backup even if you wait months to move.

2. Download your images and assets

Image and file fields in your CSVs come through as URLs, not files. So you are not done until you download the files those URLs point to. A few images? Do it by hand. Hundreds? A short script can walk the URL columns. A developer can write one in minutes. Also gather the assets that never lived in the database. Grab the app icon, splash screen, logo files, and custom fonts. Get the original high-res versions, not the squeezed copies inside Adalo.

3. Document your flows with screen recordings

Almost everyone skips this step. It is worth more than the CSVs. The new app will not be built from Adalo's internals. It will be built from a spec. The best spec is the running app itself. So while the app still works:

• Screen-record every key flow on a real phone: sign up, log in, the core loop your users repeat, payments, notifications, settings, and edge cases.
• Screenshot every screen. Include the empty states and error states.
• Write one page of notes on what matters. Note which screens users live in and which features nobody touched. Note what you would cut if you rebuilt today. You have real usage behind you now. That knowledge is an asset the first build never had.

4. Collect your accounts and credentials

List everything tied to the app. Start with the Apple Developer and Google Play accounts (more on these below). Add your domain registrar and any outside services wired in, like Stripe, OneSignal, Xano, or email. Note who holds each login. More moves go sideways over a lost login than over anything technical.

What you cannot take with you

Be clear-eyed about this list. It is what makes the rest of the move go well.

• The app itself. The screens, parts, and styling you built live as settings inside Adalo's system. They are not a Flutter or React Native project you can open elsewhere. There is no build to download and no code hand-off. The published app is Adalo's engine running your settings.
• The logic. Every action, visibility rule, and automation is Adalo-only. You will rebuild it in whatever tool comes next. That is fine. Rebuilding logic from a screen recording is fast. You will fix old mistakes along the way.
• Database links. Your CSVs carry the records. But the links between collections flatten on export. A one-to-many between Users and Orders becomes an ID or text value in a column. Whoever rebuilds the app maps those IDs back into a clean schema on the new stack. Simple work, but it is work. Budget for it.
• Third-party wiring. Your Stripe account and its customer data are yours. They survive the move. The link between Stripe and the app gets rebuilt on the new side.

The developer account question (fix this first)

One question decides if your move is a smooth handover or a hostage talk: whose name is on the Apple Developer and Google Play accounts your app is published under?

If the accounts are yours, you are in a strong spot. The store listings, the app's name, its reviews, its ratings, and its installed base all belong to those accounts. A rebuilt app can ship as an update to the same listing. Your users get the new version like any other update. Every review and every install stays.

If someone else published the app (a freelancer, an agency, or a platform account), fix that before you move. Not after. Both stores let you transfer an app between accounts. Apple does it through the app-transfer flow in App Store Connect. Google Play has its own account transfer. The current account holder has to start it. And that is the catch. The transfer needs the help of whoever controls the account today. That talk goes better while things are friendly, not after you announce you are leaving. If a transfer truly cannot happen, the fallback is a brand-new listing plus moving users across (more below). Treat that as the last resort. Whatever path you rebuild on, make owning both accounts a must this time.

The three rebuild paths, compared

There is no export, so leaving Adalo means a rebuild. There are three real ways to do it. Each one is the right answer for somebody.

Path 1: Rebuild it yourself in FlutterFlow (or similar)

FlutterFlow is the most common next stop for Adalo grads, and for a reason. It generates real Flutter code you can download. So the "no export" problem does not repeat. You get more control, more speed headroom, and a real escape hatch. The trade: the learning curve is real (state, queries, null handling). And you stay the person who maintains the app, ships every update, and answers every store review, forever. It is the cheapest path in dollars and the priciest in your time. If your app is simple and you enjoy building, it is a fine pick. Our FlutterFlow vs Adalo vs Bubble comparison goes deeper.

Path 2: Hire an agency for a custom rebuild

An agency rebuilds the app as a custom Flutter or React Native project. You get exactly the app you spec, in real code, with no platform ceiling. The trade: expect about $35,000 to $120,000 upfront, based on how complex the app is. Plan for several months of build time. And ask the question most quotes skip: who maintains it? OS updates, certificate renewals, and bug fixes do not stop when the contract ends. So budget for a retainer or an in-house developer on top. Agencies make sense when the app is truly complex and you have the budget to own a codebase.

Path 3: A done-for-you operator that rebuilds and runs it

Most Adalo refugees have never heard of the third path. An operator rebuilds the app as custom native iOS and Android software, then runs it for you, for good. That is what Rehost does for Adalo users. We rebuild your app from your CSVs, assets, and screen recordings. We ship it in about 14 days as an update to your current listings. Then we host, watch, and run it. There is no editor to learn and no dashboard to babysit. When you want a change, you send a message and we ship it. Rehost Business starts at $950/month, billed by monthly active users, with no setup fee. And the ownership answer is documented before launch. Customer data remains yours; developer accounts, domains, code licenses, exports, and handoff follow the signed agreement.

The migration checklist

In order, whichever rebuild path you choose:

1. Export every collection to CSV and check the row counts.
2. Download all images and files, including everything the exports point to by URL.
3. Screen-record every flow and screenshot every screen while the app still runs.
4. Write the one-page spec: what stays, what goes, what real usage taught you.
5. Confirm the Apple Developer and Google Play accounts are in your name. Start the store transfer now if they are not.
6. List third-party services (payments, push, integrations) and who holds each login.
7. Choose your rebuild path. Get the new app built and tested against your CSVs.
8. Ship the rebuilt app as an update to your current listings.
9. Keep your Adalo plan alive until the new app is stable. Then export one last data snapshot and cancel.

How to avoid losing users during the switch

A move only counts as a win if your users come with you. Three things protect them:

• Keep the same listing. This is the big one. It is why the account section above matters. If the new app ships as an update to your current listing, users just update the app they already have. Reviews, ratings, and installs all carry over.
• Roll out in phases. Both stores support staged rollouts. Release to a small share of users first. Watch crash reports and support messages. Ramp up as it holds steady. You catch problems at 10 percent instead of 100.
• Use the old app to announce the move. If push still works in your Adalo app, send a note that an upgraded version is coming. If passwords will reset, say what to expect. An in-app banner does the same job. If you were forced onto a new listing, this channel is how you point everyone at it. So do not cancel the old app until most of your active users have moved.

FAQ

Can you export code from Adalo?

No. As of 2026, Adalo has no source-code export. There is no way to download your app as a Flutter, React Native, or other codebase you could keep working on elsewhere. You can export your data (each collection as a CSV), your uploaded files and images, and your brand assets. Check your plan and Adalo's docs for the latest. But plan any move as a rebuild, not a port.

How do I transfer my Adalo app to another platform?

You move the pieces, not the app. Export every collection to CSV. Download all assets. Record every screen and flow. Then rebuild on the new stack (FlutterFlow, a custom agency build, or a done-for-you operator like Rehost) and import your data. If your App Store and Google Play listings sit under your own developer accounts, the new app ships as an update to the same listings. Your users carry over on their own.

Will I lose my App Store reviews if I rebuild my Adalo app?

Not if the new app ships as an update to your current listing. Reviews, ratings, and installs belong to the listing, not to the tool that built the app. You only lose them if you must start a brand-new listing. That mostly happens when the app was published under someone else's developer account and cannot be transferred. So securing the accounts is step one.

Can I export my users from Adalo?

Yes. The Users collection exports to CSV like any other. It includes emails and profile fields. Passwords do not export. They are stored hashed, as on any careful platform. So users will set a new password or use a reset flow the first time they sign in to the new app. Tell them ahead of time and the friction is small.

How much does it cost to migrate from Adalo?

The export itself costs nothing but time. The rebuild is where the money goes. If you rebuild in FlutterFlow, it costs your own hours plus the tool fee. An agency build runs about $35,000 to $120,000 upfront, plus upkeep after. A done-for-you operator like Rehost is $950/month with no setup fee. Rehost rebuilds the app and then runs it for you.

The bottom line

There is no export button. It turns out you do not need one. Your data, your assets, your store listings, and your brand all come with you. So does everything you learned by running a real app with real users. That is worth far more than the settings you leave behind. Outgrowing Adalo means the tool did its job. The only choice left is who builds and runs the next version: you, an agency, or an operator. Want it rebuilt as a custom native app in about 14 days, shipped to your current listings, and then run for you for good, with customer-data, account, license, export, and handoff terms in writing? That is what we do. Book a call and bring your CSVs. We will give you a straight answer on the move, even if the right answer is not us.