What gets migrated
- React + Vite or Next.js source code
- Supabase schema and data
- Supabase Edge Functions (if present)
- Environment variables
Prerequisites
- An Nometria account
- Your Lovable project connected to a GitHub repository (recommended)
- A Supabase account
- A custom domain (optional)
Step 1 — Connect Lovable to GitHub (if not done)
If your Lovable project isn’t already on GitHub:- In Lovable, go to Project Settings → GitHub
- Click Connect to GitHub and authorize Lovable
- Create a new repository or select an existing one
- Lovable pushes your project code to the
mainbranch
Step 2 — Connect to Nometria
New Migration → Connect via GitHub
Go to nometria.com/dashboard → New Migration → Connect via GitHub.
Select your Lovable repo
Authorize Nometria and select the repository that Lovable is syncing to. Choose the
main branch.Step 3 — Configure
Environment variables
Add your Supabase credentials and any other API keys:If your Lovable app uses Stripe, Resend, or other services, add those keys now.
Database
Select Use existing Supabase project and paste your Lovable Supabase project credentials.Or select Create new Supabase project to get a fully independent copy of your database.
Step 4 — Deploy
Click Deploy and monitor the build logs. First deployment takes 5–10 minutes.Step 5 — Two-way sync with Lovable
Because Lovable already pushes to GitHub, Nometria’s two-way sync connects naturally:- Lovable changes → GitHub
main(via Lovable’s GitHub sync) → Nometria detects → production redeploys - Developer PRs → merged to GitHub
main→ Nometria detects → production redeploys
.Nometria.yml for Lovable:
auto_merge from builder/latest may be redundant — Lovable pushes directly to main. Keep auto_deploy_on_merge: true to ensure production stays up to date after every Lovable commit.
Post-migration checklist
- Live URL loads correctly
- Supabase auth works (sign up / sign in)
- All Supabase Edge Functions deployed
- Database reads and writes function
- SSL active on your custom domain
- Lovable GitHub sync is still enabled (for ongoing builder changes)