Skip to content

Project transfer requirements

A project transfer runs checks on your account, the project, and both organizations. This page lists each requirement and what to do when one blocks a transfer. For the steps, see Transfer a project.

The source organization is the organization the project belongs to before the transfer. The target organization is the organization you move the project to.

The Supabase Dashboard checks every requirement when you select a target organization. Transfer Project stays disabled until all of them pass.

Account requirements

Your account must meet the following requirements:

  • You're an Owner of the source organization. An Administrator can't transfer projects.
  • You're a member of the target organization with a role for the whole organization: Owner, Administrator, or Developer. On the Team Plan and Enterprise Plan, the Read-only role also qualifies. The No-access role and project-scoped roles don't qualify. For more information about roles, see Access control.
  • You use the same account in both organizations. An account that signs in with single sign-on (SSO) and a non-SSO account with the same email address are separate accounts, so a role held by one doesn't count for the other. If your SSO account isn't a member of both organizations, use a non-SSO account that is. For more information, see Enable SSO for your organization.

Recover access to the Owner account

In the Dashboard and with the Management API's transfer endpoint, only an Owner of the source organization can transfer a project. Supabase support can't transfer a project for you and doesn't decide ownership disputes.

If you can't sign in to the Owner account, contact support. Support must verify that you own the account before it restores access, and it usually relies on billing records to do so. An organization on the Free Plan has no billing records, so support might not be able to restore access.

Project and organization requirements

The project and the two organizations must meet the following requirements:

  • The project has no GitHub connection. Disconnect the GitHub integration, then reconnect it after the transfer.
  • No member and no pending invitation has a project-scoped role on the project. Remove those roles and cancel those invitations before the transfer. To assign the roles again afterwards, the target organization must be on the Team Plan or Enterprise Plan.
  • If both organizations are on the Free Plan, the source organization has no usage restriction. See the Usage restrictions on Free Plan organizations section.
  • If the source organization is on the Free Plan or Pro Plan, you have no overdue invoices. See the Overdue invoices section.
  • If the target organization is on the Free Plan, the transfer doesn't put an Owner or Administrator of the target organization over the free project limit. See the Free project limit section.
  • The project doesn't use a feature that the target organization lacks. See the Features that block a transfer section.

Usage restrictions on Free Plan organizations

A Free Plan organization that exceeded its quota can't transfer projects to another Free Plan organization. The Dashboard shows the following message:

This project can't be transferred to a Free organization while the source organization is in an active grace period or under service restrictions. Resolve the restriction or upgrade the source organization before transferring.

The block applies only when both organizations are on the Free Plan. It stays in place in all of the following cases:

  • Your usage drops back under the quota.
  • The grace period ends.
  • The restriction on the organization is lifted.

The block ends when the restriction notice clears from the source organization. The notice clears automatically if you continue to stay under plan limits for multiple billing cycles. For more information, see What is a grace period and does it reset after usage drops?.

To transfer without waiting, use either of these options:

  • Upgrade the source organization to the Pro Plan. The upgrade lifts the restriction, and the block applies only between two Free Plan organizations. The plan fee applies to the whole organization. For the cost, see Pricing.
  • Transfer the project to an organization on the Pro Plan and above.

Supabase support can't lift a restriction to allow a transfer.

If you upgrade the source organization only to transfer a project, transfer the project before you downgrade. An organization that returns to the Free Plan can be restricted again.

Overdue invoices

Overdue invoices block a transfer to any target organization when the source organization is on the Free Plan or the Pro Plan. The check covers the source organization and every other Free Plan or Pro Plan organization where you're an Owner or Administrator. The Dashboard names the organizations in the following message:

There are overdue invoices in the organization(s) <organization names>. Head to the organization's invoices page to settle the invoices before transferring the project.

Pay the overdue invoices on each organization's invoices page. The check also passes when an organization's credit balance covers its overdue amount.

Free project limit

The free project limit is counted for each member, not for each organization. Every Owner and Administrator of the target organization can have a limited number of active Free Plan projects, two by default, counted across all Free Plan organizations they own or administer. Paused projects don't count. When the source organization is also on the Free Plan, the check skips Owners and Administrators of the target organization who are also members of the source organization.

When the transfer would put a member over the limit, the Dashboard lists the affected members. To continue, use one of these options:

  • Ask each listed member to pause or delete one of their Free Plan projects, or to upgrade one of their Free Plan organizations.
  • Change the member's role to Developer in the target organization's team settings. The limit counts only Owners and Administrators.
  • Transfer the project to an organization on the Pro Plan and above.

Features that block a transfer

Some features block a transfer until you remove them or choose a different target organization. The following table lists each feature, when it blocks a transfer, and what to do.

FeatureBlocks the transfer whenWhat to do
Preview and persistent branchesThe target organization is on the Free PlanSave the data you need from the branches, then delete them
Log drainsThe target organization is on the Free PlanRemove the log drains
Advanced multi-factor authentication (MFA) with phone or WebAuthnThe target organization is on the Free PlanTurn off phone and WebAuthn MFA
PipelinesThe target organization is on the Free PlanDelete all pipelines
High availabilityThe target organization has no high availability access or capacityChoose a target organization with high availability access
AWS PrivateLinkThe project has a PrivateLink associationRemove the PrivateLink associations
Vector bucketsThe source organization has access to vector buckets and the target doesn'tContact support to turn on vector buckets for the target organization
Stripe ProjectsThe project was provisioned through StripeSee the Stripe Projects section
A restore in progressThe project is restoringWait until the restore finishes

Compliance settings don't block a transfer. If your project is a HIPAA project, transfer it only to an organization that also has the HIPAA add-on. See the shared responsibility model.

Partner-managed projects

For a project that you manage through a partner, start with the following:

Stripe Projects

A project provisioned through Stripe Projects can't be transferred while it's linked to Stripe. The Dashboard message asks you to deprovision the project through Stripe before you transfer it.

To move the data to another organization, create a project in that organization and copy the data to it. See Migrating within Supabase.

To read more about project transfers, see these pages: