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
You do not need to reproduce an existing Replit project from memory.
Use the codebase as the starting point
1. Confirm the latest working code is in a Git repository.
2. Create a branch or copy for the migration.
3. Import the repository into Empromptu AI.
4. Identify environment variables, external services, databases, and scheduled jobs.
5. Run the main workflow with test data.
6. Correct missing or environment-specific pieces.
7. Establish the new deployment path before changing production.
The first goal is parity: the important workflow behaves as it does today.
The second goal is improvement: add the data, evals, monitoring, controls, or AI behavior that brought you to Empromptu AI.
Keep those goals separate so a migration does not become an uncontrolled rewrite.
Common mistakes
Migrating code without environment variables and external service details.
Combining parity work with a major redesign.
Changing production before the new deployment path is proven.
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.