Transfer Your Lovable Project to Another Account: Keep It Yours
Complete guide to moving projects between accounts. Plus why independent hosting prevents billing surprises after handoff.
The 4-Step Transfer Process
Here is exactly how to move a Lovable project to another account. The whole process takes 5 minutes.
Invite the target email to your workspace
In your Lovable workspace, go to Settings > People > Invite. Enter your client's email address and send the invite.
Client accepts the invitation
Your client checks their email, clicks the invitation link, and joins your workspace (or creates a Lovable account if they don't have one).
Open the project and find Transfer option
In the project you want to hand off, go to Settings. Look for the Transfer option (or Move to another workspace).
Select destination workspace and confirm
Choose your client's workspace as the destination. Accept the warning about GitHub and Supabase needing re-linking. Confirm the transfer.
After Transfer, Who Owns the Hosting Bill?
The transfer steps are straightforward. But the aftermath is where agencies get stuck.
Your client now owns the Lovable workspace. That's good. But Lovable's hosting bill moves with it.
Here is what happens next: Your client is responsible for monitoring AI credits. Building costs 0.5 to 1.7 credits per prompt. Hosting costs 20 credits per month on the free tier. Overage charges are automatic. No warning email before the bill spikes. No SLA. No support guarantee.
This is not a hosting decision. This is a relationship risk. Your client calls you three weeks in: "Why did we get charged EUR 47 for hosting we didn't touch?"
You want to hand off three things:
- The code (they own it)
- The infrastructure (they control it)
- The bill (they see it coming)
Lovable gives you the code and the bill. Ship gives you all three clearly separated.
Your client can see exactly what they're paying for: the server size and storage allocation. The bill is transparent. It does not spike based on AI usage. It doesn't require ongoing credit monitoring. They know the cost before the month starts.
After Transfer: Lovable Cloud vs. Ship
Transfer Lovable Projects with Transparent, Predictable Costs
Move your project cleanly to your client. Then move the hosting responsibility without ambiguity.
Predictable Costs
Your client sees exactly what they pay for: the server size and storage. No hidden AI credit burns. No mystery bills. No "why did we get charged EUR 47 this month?" support tickets. The cost is fixed month to month, tied to infrastructure, not usage spikes.
True Ownership
The app lives in your client's Opsily account. Not your agency's. Not Lovable's platform. Their infrastructure, their control, their terms. This is what delivering a project actually means. No ongoing platform dependency. No future surprises when Lovable changes pricing or features.
GDPR Automatic
German datacenter. EU data residency. No separate legal negotiation required. If your clients are in Europe, compliance is baked in. Lovable Cloud requires additional agreements and separate GDPR reviews. Ship delivers it by default.
Built for teams who need reliability
Simple, Transparent Pricing
Choose the server that fits your app. All plans include GDPR-compliant German hosting, automatic backups, and 99.9% uptime.
Loading pricing...
Enterprise-Grade Support for Client Projects
Ship is built for agencies handing off production apps. Your clients get the reliability they need.
99.9% Uptime SLA
Monitored 24/7 with automated failover and daily encrypted backups. Your client's app doesn't go down.
GDPR Compliant by Default
German datacenter, EU data residency, automatic compliance. No configuration, no separate legal work. Your app is GDPR-ready on day one.
German Infrastructure
Hetzner-backed datacenter in Germany. Your data stays in your jurisdiction. No US servers, no cross-border data transit.
Free SSL Certificates
HTTPS on every domain. Automatic renewal, no expiry surprises. Security is included, not an add-on.
Common Questions About Project Transfers
Lovable automatically created a GitHub repo during development. When you transfer the project, that GitHub repo doesn't move automatically. You need to check access permissions: if the repo was created under your agency email, your client won't have access yet. You have two options: (1) Transfer repo ownership to your client's GitHub account via GitHub's settings, or (2) Ask your client to connect their own GitHub account to the Lovable project in Settings. Ship simplifies this because GitHub is already part of the deployment workflow—no separate re-linking needed.
Move Your First Client Project to Ship
Free 7-day trial. No credit card. Full access to all features. See why agencies choose Ship for client handoffs.