Migration guide
Move a Lovable project into a repository-led Xroga workflow
Lovable documents GitHub synchronisation for project code. A safe migration still requires an inventory of the services and configuration that live outside the repository.
Reviewed against official sources · 2026-09-11
01
Preserve the original before changing platforms
Export or connect the complete repository, record the working commit, capture environment-variable names without secret values, and document current domains, data stores, authentication, scheduled work, and deployment ownership.
02
Audit what the source platform supplied
Separate portable source code from hosted services, platform-specific packages, generated configuration, and implicit runtime behavior. Confirm licences and asset rights. Do not assume a Git export contains databases, secrets, deployment history, or provider state.
03
Move one boundary at a time
Make the application build locally first, then restore data and identity integrations, then deployment configuration. Keep each transition reviewable and preserve a rollback point until the replacement path is verified.
04
Verify the result rather than the transfer
Run the destination repository’s checks and production build. Test authentication, critical data paths, narrow layouts, provider callbacks, domain routing, monitoring, and rollback. Only retire the original service after the new production URL is directly verified.
Primary sources
Product capabilities change. These official pages were used for the factual statements above; verify them again before making a purchasing decision.