Move a web app built in one AI coding tool's hosted "sites" feature to a normal host?
Context: A solo owner (not a developer) built a personal job-search dashboard over ~3 months using an AI coding assistant. The dashboard UI was built and deployed inside that assistant's own built-in site hosting. It uses that platform's built-in sign-in and its built-in SQLite-style database. The rest of the system (job scraping workers, scoring, a Postgres database) already runs on a separate general-purpose cloud host and works. A simpler earlier project of theirs was successfully moved off the AI tool onto their own GitHub repo and that general cloud host.
Problem: the dashboard's decisions (approve/reject a job, application status) save to the built-in database, not the main Postgres database, so the workflow never connects. The owner wants a working beta in about 3 days and has said they are tired of tech troubleshooting.
How I read it: Yes, they can move it. Step 1 is pushing the dashboard code to their GitHub (low risk, minutes). Step 2 is hosting it on the same cloud host as the workers, which means replacing the built-in sign-in (with the Postgres provider's login) and the built-in database (writes go to Postgres instead). Step 2 is extra work (maybe half a day) but the database switch was required anyway.
What I'm unsure about: For a non-technical owner on a 3-day deadline, would you (a) move hosting now, since the database rewrite is happening anyway, or (b) only push the code to GitHub now, keep the current hosting for the beta, and move after? I lean (a). Is there a people/process risk I'm missing, like the owner losing the ability to keep working with the original AI tool, or the move becoming another time sink?