Before you begin
Create a copy or migration branch and keep the live application unchanged.
Document environment variables, integrations, databases, scheduled jobs, and the critical user workflow.
Migrate without disrupting the live app
Moving a live app feels risky because it is not “just code.” It may be months of decisions, customer feedback, and your own work.
Use a parallel migration instead of changing the live version
1. In Lovable, use “Remix Project” to create a separate copy.
2. Connect the copy to GitHub.
3. Import that repository into Empromptu AI.
4. Test and improve the imported version while the original app stays live.
5. Switch production only after the new version works the way you expect.
This gives you a backup, version history, and a clean place to test without asking your users to participate in the migration.
If the first import is imperfect, do not panic. Review what carried over, what needs translation, and what should be rebuilt more robustly. You can correct the migrated version without touching the live app.
Common mistakes
Importing the live Lovable project without making a copy.
Switching production before testing the main workflow.
Interpreting an imperfect first import as a reason to start from zero.
Frequently asked questions
Does migration require downtime?
Not for the build and test phase. Keep the current application live and switch users only after the migrated version is verified.
What if the first import is incomplete?
Treat the import as a starting point. Identify what transferred, what depends on the old environment, and what should be translated or rebuilt more robustly.