Skip to content

Troubleshoot a project transfer

Find out why a project transfer is blocked, and what to do about it. For the steps of a transfer, 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.

When a check fails, the Supabase Dashboard shows a Project cannot be transferred box with one or more messages. The Management API's preview endpoint returns the same messages in its errors list. When a check fails, the transfer endpoint returns HTTP 400 with the messages after the text Transfer is not possible, due to the following reasons:. Two cases differ: a transfer to the project's current organization returns 400 with only its own message, and the endpoint returns 503 while transfers are paused.

The following tables list each message with its cause and fix. Some long messages are shortened to their first sentences, so match on the start of the message.

Role and membership messages

The following table lists the messages about your role in the two organizations:

MessageCauseFix
You must be an owner of the project to transfer a project.You aren't an Owner of the source organization.Ask an Owner to transfer the project or to make you an Owner.
You must be a member of the target organization to transfer a project.The account you're signed in with isn't a member of the target organization. An SSO account counts as a separate account.Ask for an invitation for this account.
You must have organization permissions within the target organization to transfer a project.You have the No-access role or only project-scoped roles in the target organization, or your access token doesn't include the target organization or lacks Organization Members with Read access.Ask an Owner for a role for the whole organization, or create a token with the access listed in Prerequisites.

Billing and limit messages

The following table lists the messages about restrictions, invoices, and project limits:

MessageCauseFix
This project can't be transferred to a Free organization while the source organization is in an active grace period or under service restrictions.Both organizations are on the Free Plan and the source exceeded its quota.See Usage restrictions on Free Plan organizations.
There are overdue invoices in the organization(s)An organization where you're an Owner or Administrator has overdue invoices.See Overdue invoices.
The target organization exceeds the free project limit when transferring this project.An Owner or Administrator of the target organization is at their limit.See Free project limit.

Project feature messages

The following table lists the messages about the project's features and status:

MessageCauseFix
Project is currently connected to GitHub. Please disconnect the GitHub integration before transferring the project to another organization.The project has a GitHub connection.Disconnect the GitHub integration, then reconnect it after the transfer.
Please remove linked project scoped role before transferring this project.A member or a pending invitation has a project-scoped role on the project.Remove every project-scoped role and cancel the invitations that carry one. To assign the roles again, the target organization must be on the Team Plan or Enterprise Plan.
The source project has preview branches that can't be transferred to an organization on a Free Plan.The target organization is on the Free Plan and the project has preview or persistent branches.Transfer the project to an organization on the Pro Plan and above. Or save the data you need from the project's preview and persistent branches, then delete them. Deleting a preview branch loses its data changes, and a branch that you create again is seeded from ./supabase/seed.sql.
Log Drains must be removed from the project before transferring it to an organization that does not have access to Log DrainsThe project has log drains and the target organization's plan doesn't include them.Remove the project's log drains.
Advanced MFA Phone must be removed from the project before transferring it to an organization that does not have access to Advanced MFA PhoneThe project uses phone MFA and the target organization's plan doesn't include it.Turn off phone MFA in the project's Auth settings. With the Management API, set mfa_phone_enroll_enabled and mfa_phone_verify_enabled to false with the update auth service config endpoint.
Advanced MFA WebAuthn must be removed from the project before transferring it to an organization that does not have access to Advanced MFA WebAuthnThe project uses WebAuthn MFA and the target organization's plan doesn't include it.Turn off WebAuthn MFA in the project's Auth settings. With the Management API, set mfa_web_authn_enroll_enabled and mfa_web_authn_verify_enabled to false with the update auth service config endpoint.
Pipelines must be removed from the project before transferring it to an organization that does not have access to PipelinesThe project uses Pipelines and the target organization doesn't have access to them.Remove Pipelines from the project.
ETL is not available on Free Plan organizations, please delete all of your pipelines before transferring the project.The target organization is on the Free Plan and the project has pipelines.Delete all pipelines.
The target organization does not have access to high availability projects.The project uses high availability and the target organization doesn't have access to it.Choose a target organization with high availability access.
The target organization has reached its maximum number of high availability projectsThe transfer would put the target organization over its limit of high availability projects.Choose a different target organization, or remove a high availability project from the target.
Project transfers with active AWS PrivateLink Associations are not supported. Please remove all AWS PrivateLink from project associations before transferring.The project has AWS PrivateLink associations.Remove the project's PrivateLink associations.
The source organization has access to Vector Buckets, which is not available in the target organization.The source organization has access to vector buckets and the target organization doesn't.Contact support to turn on vector buckets for the target organization.
Project is provisioned via Stripe. Please deprovision the project through Stripe before transferring it to another organization.The project is provisioned through Stripe Projects.See Stripe Projects before you remove anything in Stripe.
Your project is currently restoring, please wait until restoration is complete.A restore is in progress.Wait until the restore finishes.
Cannot transfer project to the organization it already belongs to.The target organization is the project's current organization. The project might have moved already.Check which organization owns the project.
One or more projects to be transferred are not part of source organization.The project's organization changed while the transfer was running.Reload the page and check which organization owns the project.
Project transfers are temporarily disabled, please try again later.Transfers are temporarily paused.Try again later.

The transfer button is missing or disabled

The following list covers each case where you can't start or confirm a transfer in the Dashboard:

  • The Transfer project section is missing. You're viewing a branch. Open the main project instead.
  • Transfer project is disabled. The tooltip gives the reason:
    • You need additional permissions to transfer this project: only an Owner of the source organization can transfer.
    • Project transfers are temporarily disabled, please try again later.: transfers are temporarily paused.
  • The dialog shows You do not have any organizations you can transfer your project to. Your account is a member of no other organization. Create an organization, or ask for an invitation to one.
  • Transfer Project in the dialog is disabled. No target organization is selected, the checks are still running, or a check is failing. Read the Project cannot be transferred box.

The transfer fails after you confirm

If you see a message that starts with Failed to transfer project: after you confirm, compare the rest of the message with the messages in the Role and membership messages, Billing and limit messages, and Project feature messages sections. If the text matches none of them, check which organization owns the project before you try again.

To read more about project transfers, see these pages: