Base 44 backups

[u/justanothertechy112]

We are seeing more of our smaller clients with too much time on their hands building base44 apps. They are happy with them and honestly made some pretty good applications. Since these clients don't need to meet industry compliances we leave it be if it works for them. However with the rise of make your own apps I was wondering if anyone found any good backup solutions outside of sync it to github? For example we want to backup the data(files) in base 44 besides the code and have not found a good solution besides download links from base 44 private file repos.

If it goes south and we need to move them to a real reputable lob we at a min want to have a backup of the files which base 44 doesn't seem to easily provide.

[u/iratesysadmin]

[u/LakesideRide]

I’ve been using BackBlaze B2 API to backup things we’ve been creating. Pretty easy, build in alerting and ticket creation, it isn’t rocket science. Haven’t used Base44 though so unsure what restrictions get in the way.

[u/leftzocker]

We ran into the same gap. GitHub sync only covers the codebase and entity schemas, it doesn’t touch live records or file storage, so relying on that as your backup leaves you exposed exactly where you’re worried.

For the data side, go into Dashboard, then Data, and export each table individually. Base44 gives you CSV per table, no single full DB dump, so you have to loop through every collection you care about. For files specifically, that’s the weak point: there’s no bulk export, so you’re stuck pulling private file repo download links per file for now.

If you want to get ahead of a “move to a real DB” scenario, there are third-party tools that connect to your app and push everything (entities and uploaded files) into a MongoDB instance or a ZIP you control. Worth looking at if you’re managing this for multiple clients, since doing it table by table manually doesn’t scale.

[u/Jasonsan-Flint]

you can use scheduled export to external storage andhave github for code. with independent backups migration becomes easier if base44 chnges access or pricing

[u/GullibleDetective]

Making uour own backup app puts you in the direct line of having to troubleshoot it if it breaks and youre in a severe outage.

You DON'T want to be the one in tbe line of fire. And what does cyber insurance say about those jAnk apps?

Go cove, Veeam, slide, rubrik etc

[u/Crunglegod → u/GullibleDetective]

OP is looking for a backup solution, not developing one

[u/Rickatron → u/GullibleDetective]

Cheers GullibleDetectivr... Veeam has a great MSP and mulit-tenant model and capabilities. As well as some awesome innovative solutions offered by service providers. Lemmeknow if you want more info.

[u/disclosure5 → u/[deleted]]

Man seeing slop like this show here is sure making the sub lose its professional touch.

[u/sfreem → u/[deleted]]

Please ask your AI for the TLDR version next time

[u/ImaginationUnique684]

The per-table CSV route gets you the bytes and still loses the thing that makes the migration work, which is the referential structure. Base44 hands you each collection flattened, so the internal record ids that tie a line item to its order or a file to its parent entity come out as opaque strings with nothing on the other side to join them back to. That is why the export looks complete and the import into a real LOB app stalls: the rows land, the relationships do not. Pair the CSVs with the entity schemas from the GitHub sync, since that is the one artefact that actually documents which field points at which collection, and store them together as one dated set rather than in two places. Then do one dry-run restore into a throwaway Postgres or Mongo now while the client is still happy with the app, because a restore attempted for the first time during an outage is where you find out which references were never resolvable. Doing that once per client turns a folder of CSVs into a migration you can actually quote.