Shipholm
Sign inStart free

Skills

Migrate from Lovable (and Supabase)

Move a Lovable app – with or without Supabase or Lovable Cloud behind it – to Shipholm, step by step.

0. Is there a backend at all?

A Lovable project is a Vite + React app in a GitHub repository (connect it in Lovable's GitHub settings if it is not). Look for @supabase/supabase-js in package.json and a supabase/ folder:

Lovable keeps pushing to the repository's default branch while the project is open there. Work on a branch of your own until the cut-over, and decide with your human whether Lovable stays the editor afterwards (every push still deploys) or is retired.

Check which branch is the real one before you build anything. create_app builds main unless you pass a branch, but the newest work may be on another branch (the repository's default branch, a branch another agent works on). git log --oneline main..<other> and the other way round show what each has. Several writers are common – Lovable, another agent, a human – so read git log main for commits that are not yours before you merge into it.

Frontend-only apps: after the first deploy, check that the files in public/ are served as what they are: curl -sI https://<app>.shipholm.dev/favicon.png must say image/png. An SPA fallback answers a missing file with index.html and status 200. The page looks fine, but card images and icons are broken. That usually means the build is not the one you think: the wrong branch, or no Dockerfile, so Railpack built it.

1. Inventory – what does the app really use?

Read the repository before deciding anything:

Write the result down as a table: what is used, how much data, what can go. Often features that were generated "just in case" (comments, profiles, notifications) have no data at all – dropping them is the biggest simplification.

2. Choose where the data lives

Keep the existing ids (uuids) so links like /app/<id> keep working.

3. Export the data

4. Replace the backend

5. Files and sign-in

6. Cut over

  1. Set up the app before the pull request is built. A preview copies the parent app's settings when it is built: storage=true (or database=true), previews=true and the secrets (set_env(..., app=..., secret=true) for the admin key). Keep the old health path until the new server runs in production.
  2. Work on a branch with previews=true: the pull request gets <app>-pr<N>.shipholm.dev. If the repository is synced with Lovable, do not push to the branch Lovable deploys until the cut-over.
  3. Import into the preview and check every page. The import's answer lists every file it could not download. A download that returned HTML means the source app has the problem above, not the import. Fix it there and run the import again; it fetches only the files it is missing.
  4. Add both domains (add_domain for <domain> and www.<domain>) and create their TXT records now. Verification needs only the TXT record, so the old site keeps running.
  5. Merge, then set health_path="/healthz". Wait until https://<app>.shipholm.dev/healthz answers JSON from the new server (the old SPA answers HTML). Import into production and compare the row counts with the source. Then verify_domain both domains.
  6. Switch DNS last. Lovable serves a custom domain from an A record (185.158.133.1 when we moved one; proxied in Cloudflare). Delete it and add one A record per address that add_domain returned for the apex, plus a CNAME www → <app>.shipholm.dev. Make both DNS only, not proxied: the certificate is issued once traffic arrives, usually within two minutes.
  7. Check both hosts over HTTPS (/, /healthz, a few pages, the API), and that the apex redirects to www.
  8. Remove the domain from the Lovable project. Keep the Supabase project read-only for a while before you delete it.

Use when: Migrate an app from Lovable to Shipholm – frontend-only apps in one step, apps on Supabase or Lovable Cloud via SQLite or Postgres (inventory, export, replace the backend, files and sign-in, cut over). Use when an app was built in Lovable or uses @supabase/supabase-js.

For agents: get_skill("shipholm-migrate-from-lovable") over MCP, or the SKILL.md at https://api.shipholm.com/skills/shipholm-migrate-from-lovable/SKILL.md.