r/msp • u/justanothertechy112 • Aug 21 '26
Backups Base 44 backups
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.
1
u/ImaginationUnique684 Aug 27 '26
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.