Move from Lovable without losing the app you already built

Start with the GitHub repository

Lovable supports GitHub synchronization, and its documentation says projects can be cloned, modified and deployed outside Lovable. StackFerry uses the repository URL as the starting point. Public repositories can be inspected directly; private repositories require a read-only GitHub App connection.

Creating a StackFerry project does not copy database rows, users, uploaded files or secret values. The initial assessment is deliberately metadata-first.

Map every provider boundary

The frontend build is only one layer. Review environment variables, authentication providers, email templates, redirect URLs, database schema, row-level security, storage buckets, functions, scheduled jobs, analytics, payments and domain configuration.

Each dependency is classified as portable, adaptable, replaceable or blocked. That turns a vague migration into a route with explicit actions and risks.

Verify first, cut over last

Create the destination in an account owned by the customer. Reproduce the minimum configuration, deploy a preview, run automated checks and complete a smoke test. Production data, auth identities and storage objects remain outside the standard port unless a separate transfer plan is approved.

Only after the target is verified should you schedule DNS, email, OAuth callback or data changes. Keep a rollback path until the new environment has been observed under real traffic.

Frequently asked questions

Related guides

• Move a Lovable app to Netlify with the backend kept explicit
• Transfer a Supabase database without treating data like a build artifact
• Self-host a Lovable app with a plan for every managed dependency