Supabase Project Transfer Limitation

[Bhavish49]

Currently, Supabase only allows transferring ownership at the organization level, not at the individual project level. This means if a project is created under one Gmail account, it cannot be directly transferred to another Gmail account without moving the entire organization.
Suggested improvement: Enable project-level transfer so that users can move a single project to another account without affecting the rest of the organization.

[DYNOSuprovo]

Project-level transfer is actually already supported in Supabase without needing to transfer your entire organization.

Here is how you can move an individual project directly from one account/organization to another:

How to Transfer a Single Project

1. Invite the destination account as an Owner/Admin:
   • In your destination organization (the account you want to transfer the project into), make sure your primary account is invited as an Owner or Administrator (or invite the destination Gmail account into the source organization).
2. Transfer via Project Settings:
   • Go to your Supabase Dashboard and select the specific project you want to move.
   • Navigate to Project Settings → General.
   • Scroll down to the Transfer Project card.
   • Select the target destination organization from the dropdown and click Transfer Project.

Key Details During Transfer:

• No Downtime: The database connection strings, API URLs (https://<project-ref>.supabase.co), API keys, and existing storage data remain completely unchanged during and after the transfer.
• Billing: The compute and add-on costs for that individual project will transition to the destination organization's billing plan on the next invoice.
• Other Projects Untouched: Only that selected project is moved; all other projects in your original organization stay untouched.