mirror of
https://github.com/supabase/supabase.git
synced 2026-10-09 11:25:06 +03:00
Ivan VasilovandJordi Enric
56de26fe22
This PR migrates the whole monorepo to use Tailwind v4: - Removed `@tailwindcss/container-queries` plugin since it's included by default in v4, - Bump all instances of Tailwind to v4. Made minimal changes to the shared config to remove non-supported features (`alpha` mentions), - Migrate all apps to be compatible with v4 configs, - Fix the `typography.css` import in 3 apps, - Add missing rules which were included by default in v3, - Run `pnpm dlx @tailwindcss/upgrade` on all apps, which renames a lot of classes - Rename all misnamed classes according to https://tailwindcss.com/docs/upgrade-guide#renamed-utilities in all apps. --------- Co-authored-by: Jordi Enric <jordi.err@gmail.com>
60 lines
3.0 KiB
Plaintext
60 lines
3.0 KiB
Plaintext
---
|
||
id: 'project-transfer'
|
||
title: 'Project Transfers'
|
||
description: 'Transfer a project to another organization.'
|
||
---
|
||
|
||
You can freely transfer projects between different organizations. Head to your [projects' general settings](/dashboard/project/_/settings/general) to initiate a project transfer.
|
||
|
||
<Image
|
||
alt="Project Transfer: General Settings"
|
||
src={{
|
||
light: '/docs/img/guides/platform/project-transfer-overview--light.png',
|
||
dark: '/docs/img/guides/platform/project-transfer-overview.png',
|
||
}}
|
||
className="max-w-[600px] mx-auto! border rounded-md"
|
||
|
||
width={677}
|
||
height={224}
|
||
/>
|
||
|
||
<Image
|
||
alt="Project Transfer: Confirmation Modal"
|
||
src={{
|
||
light: '/docs/img/guides/platform/project-transfer-modal--light.png',
|
||
dark: '/docs/img/guides/platform/project-transfer-modal.png',
|
||
}}
|
||
className="max-w-[600px] mx-auto!"
|
||
|
||
width={773}
|
||
height={581}
|
||
/>
|
||
|
||
Source organization - the organization the project currently belongs to
|
||
Target organization - the organization you want to move the project to
|
||
|
||
## Pre-Requirements
|
||
|
||
- You need to be the owner of the source organization.
|
||
- You need to be at least a member of the target organization you want to move the project to.
|
||
- No active GitHub integration connection
|
||
- No project-scoped roles pointing to the project (Team/Enterprise plan)
|
||
- No log drains configured
|
||
|
||
## Usage-billing and project add-ons
|
||
|
||
For usage metrics such as disk size, egress or image transformations and project add-ons such as [Compute Add-On](/docs/guides/platform/compute-add-ons), [Point-In-Time-Recovery](/docs/guides/platform/backups#point-in-time-recovery), [IPv4](/docs/guides/platform/ipv4-address), [Log Drains](/docs/guides/platform/log-drains), [Advanced MFA](/docs/guides/auth/auth-mfa/phone) or a [Custom Domain](/docs/guides/platform/custom-domains), the source organization will still be charged for the usage up until the transfer. The charges will be added to the invoice when the billing cycle resets.
|
||
|
||
The target organization will be charged at the end of the billing cycle for usage after the project transfer.
|
||
|
||
## Things to watch out for
|
||
|
||
- Transferring a project might come with a short 1-2 minute downtime if you're moving a project from a paid to a Free Plan.
|
||
- You could lose access to certain project features depending on the plan of the target organization, i.e. moving a project from a Pro Plan to a Free Plan.
|
||
- When moving your project to a Free Plan, we also ensure you’re not exceeding your two free project limit. In these cases, it is best to upgrade your target organization to Pro Plan first.
|
||
- You could have less rights on the project depending on your role in the target organization, i.e. you were an Owner in the previous organization and only have a Read-Only role in the target organization.
|
||
|
||
## Transfer to a different region
|
||
|
||
Note that project transfers are only transferring your projects across an organization and cannot be used to transfer between different regions. To move your project to a different region, see [migrating your project](/docs/guides/platform/migrating-within-supabase).
|