From d6f9a0483391ba74c36725a6a19e15dec6f6c806 Mon Sep 17 00:00:00 2001 From: Daniel Date: Wed, 18 Dec 2024 15:51:06 -0400 Subject: [PATCH 1/6] docs: project transfer azure --- .../introduction/billing-azure-marketplace.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/content/docs/introduction/billing-azure-marketplace.md b/content/docs/introduction/billing-azure-marketplace.md index 04f88a5a6d..9a601cd710 100644 --- a/content/docs/introduction/billing-azure-marketplace.md +++ b/content/docs/introduction/billing-azure-marketplace.md @@ -83,12 +83,26 @@ updatedOn: '2024-12-17T19:44:50.022Z' Neon pricing plans include allowances for compute, storage, and projects. For details on each plan's allowances, see [Neon Plans](/docs/introduction/plans). If you exceed these allowances on a paid plan, overage charges will apply to your monthly bill. You can track your usage on the **Billing** page in the Neon Console. For guidance, see [Monitoring Billing](/docs/introduction/monitor-usage). +## Transfer existing Neon projects to an Azure-created Neon organization + +You can transfer existing Neon projects to an Azure-created organization, but the following restrictions apply: + +- The Neon project must belong to a personal Neon account, not an organization. Organization to organization project transfers are not yet supported. +- The Neon project you want to transfer must reside in an [Azure region](/docs/introduction/regions#azure-regions). Azure-created Neon organizations do not support Neon projects created in [AWS regions](/docs/introduction/regions#aws-regions). +- Neon Free Plan to Free Plan transfers are not supported. Your Azure organization must be on a paid Neon plan, such as the Scale or Business plan. + +For transfer instructions, see [Transfer projects to an organization](/docs/manage/orgs-project-transfer). + +If the restrictions listed above prevent you from transferring your project, you have a couple of options: +- Open a [support ticket](https://console.neon.tech/app/projects?modal=support) to request assistance transferring your Neon project (only supported for projects residing in an [Azure region](/docs/introduction/regions#azure-region)). +- Migrate your data from the existing Neon project to a Neon project in your Azure-created region using `pg_dump` and `pg_restore`. See [Migrate data from Postgres with pg_dump and pg_restore](/docs/import/migrate-from-postgres#run-a-test-migration) for instructions. + ## Changing your pricing plan Changing the Neon pricing plan for an Azure subscription involves the following steps: 1. [Creating a new Neon resource](#create-a-neon-resource) with the desired pricing plan. -2. Opening a [support ticket](https://console.neon.tech/app/projects?modal=support) to request transferring your existing Neon projects to the new Neon resource. The Neon support team will transfer your projects from the "old" Neon organization to the new one. If you're on the Neon Free Plan and can't open a support ticket, you can email Neon support at `support@neon.tech`. +2. Opening a [support ticket](https://console.neon.tech/app/projects?modal=support) to request assistance transferring your existing Neon projects to the new Neon resource. The Neon support team will transfer your projects from the "old" Neon organization to the new one. If you're on the Neon Free Plan and can't open a support ticket, you can email Neon support at `support@neon.tech`. 3. Once the project transfer is complete, you can [delete your old Neon resource](#deleting-a-neon-resource-in-azure). If the old resource was on a paid plan, deleting it will stop billing. From 7b91d49980143b35e0c3d8cba60677c19fd57a6a Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Wed, 18 Dec 2024 19:52:36 +0000 Subject: [PATCH 2/6] chore: format content markdown files with Prettier --- content/docs/introduction/billing-azure-marketplace.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/docs/introduction/billing-azure-marketplace.md b/content/docs/introduction/billing-azure-marketplace.md index 9a601cd710..530b5b1726 100644 --- a/content/docs/introduction/billing-azure-marketplace.md +++ b/content/docs/introduction/billing-azure-marketplace.md @@ -94,6 +94,7 @@ You can transfer existing Neon projects to an Azure-created organization, but th For transfer instructions, see [Transfer projects to an organization](/docs/manage/orgs-project-transfer). If the restrictions listed above prevent you from transferring your project, you have a couple of options: + - Open a [support ticket](https://console.neon.tech/app/projects?modal=support) to request assistance transferring your Neon project (only supported for projects residing in an [Azure region](/docs/introduction/regions#azure-region)). - Migrate your data from the existing Neon project to a Neon project in your Azure-created region using `pg_dump` and `pg_restore`. See [Migrate data from Postgres with pg_dump and pg_restore](/docs/import/migrate-from-postgres#run-a-test-migration) for instructions. From cf85836d8b10f0c064c6ac1101a4260f78145be4 Mon Sep 17 00:00:00 2001 From: Daniel Date: Thu, 19 Dec 2024 18:54:17 -0400 Subject: [PATCH 3/6] docs: edit --- .../introduction/billing-azure-marketplace.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/docs/introduction/billing-azure-marketplace.md b/content/docs/introduction/billing-azure-marketplace.md index 530b5b1726..425ca05911 100644 --- a/content/docs/introduction/billing-azure-marketplace.md +++ b/content/docs/introduction/billing-azure-marketplace.md @@ -85,18 +85,18 @@ Neon pricing plans include allowances for compute, storage, and projects. For de ## Transfer existing Neon projects to an Azure-created Neon organization -You can transfer existing Neon projects to an Azure-created organization, but the following restrictions apply: +You can transfer existing Neon projects to an Azure-created organization, but note these restrictions: -- The Neon project must belong to a personal Neon account, not an organization. Organization to organization project transfers are not yet supported. -- The Neon project you want to transfer must reside in an [Azure region](/docs/introduction/regions#azure-regions). Azure-created Neon organizations do not support Neon projects created in [AWS regions](/docs/introduction/regions#aws-regions). -- Neon Free Plan to Free Plan transfers are not supported. Your Azure organization must be on a paid Neon plan, such as the Scale or Business plan. +- The Neon project must belong to a personal Neon account, not an organization. Transfers between organizations are not supported. +- The Neon project must be in an [Azure region](/docs/introduction/regions#azure-regions). Azure-created Neon organizations do not support projects created in [AWS regions](/docs/introduction/regions#aws-regions). +- The billing plan of the Azure-managed organization must match or exceed the billing plan of the personal Neon account. For example, transferring from a Free account to a Scale account is allowed, but not from Scale to Free. -For transfer instructions, see [Transfer projects to an organization](/docs/manage/orgs-project-transfer). +For detailed transfer steps, see [Transfer projects to an organization](/docs/manage/orgs-project-transfer). -If the restrictions listed above prevent you from transferring your project, you have a couple of options: +If the restrictions above prevent you from transferring your project, consider these options: -- Open a [support ticket](https://console.neon.tech/app/projects?modal=support) to request assistance transferring your Neon project (only supported for projects residing in an [Azure region](/docs/introduction/regions#azure-region)). -- Migrate your data from the existing Neon project to a Neon project in your Azure-created region using `pg_dump` and `pg_restore`. See [Migrate data from Postgres with pg_dump and pg_restore](/docs/import/migrate-from-postgres#run-a-test-migration) for instructions. +- Open a [support ticket](https://console.neon.tech/app/projects?modal=support) for assistance with transferring your Neon project (supported only for projects in [Azure regions](/docs/introduction/regions#azure-regions)). +- Migrate your data from an existing Neon project to a Neon project in your Azure-created region using `pg_dump` and `pg_restore`. Refer to [Migrate data from Postgres with pg_dump and pg_restore](/docs/import/migrate-from-postgres#run-a-test-migration) for instructions. ## Changing your pricing plan From b7fa38edfce8974e7e5032ba9f6adf20b8ae6253 Mon Sep 17 00:00:00 2001 From: Daniel Date: Thu, 19 Dec 2024 18:59:48 -0400 Subject: [PATCH 4/6] docs: update project transfer docs --- content/docs/manage/orgs-project-transfer.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/docs/manage/orgs-project-transfer.md b/content/docs/manage/orgs-project-transfer.md index 8d175a8077..5fe96308e9 100644 --- a/content/docs/manage/orgs-project-transfer.md +++ b/content/docs/manage/orgs-project-transfer.md @@ -15,6 +15,7 @@ A few important points to keep in mind: - You must be at least a Member of the selected Organization to transfer projects to it. - The number of projects you can transfer is limited by the target Organization plan's allowance. - Projects can't be transferred between incompatible plans due to differences in usage allowances. For example, attempting to transfer projects from a Scale plan personal account to a Launch plan Organization will result in an error. +- The billing plan of the organization must match or exceed the billing plan of the personal Neon account you are transferring projects from. - If any organization members were already collaborators on the projects being transferred, we'll remove their collaborator access since they'll get full access as org members anyway. ## Transfer from the Neon Console From b6a3e1f01b8fd920113ef55cdbec6b7c11c4afdd Mon Sep 17 00:00:00 2001 From: Daniel Date: Thu, 19 Dec 2024 19:07:31 -0400 Subject: [PATCH 5/6] docs: revision --- content/docs/introduction/billing-azure-marketplace.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/introduction/billing-azure-marketplace.md b/content/docs/introduction/billing-azure-marketplace.md index 425ca05911..01fcb0165b 100644 --- a/content/docs/introduction/billing-azure-marketplace.md +++ b/content/docs/introduction/billing-azure-marketplace.md @@ -87,16 +87,16 @@ Neon pricing plans include allowances for compute, storage, and projects. For de You can transfer existing Neon projects to an Azure-created organization, but note these restrictions: -- The Neon project must belong to a personal Neon account, not an organization. Transfers between organizations are not supported. +- The Neon project must belong to a personal Neon account, not an organization. Transfers between organizations are not yet supported. - The Neon project must be in an [Azure region](/docs/introduction/regions#azure-regions). Azure-created Neon organizations do not support projects created in [AWS regions](/docs/introduction/regions#aws-regions). -- The billing plan of the Azure-managed organization must match or exceed the billing plan of the personal Neon account. For example, transferring from a Free account to a Scale account is allowed, but not from Scale to Free. +- The billing plan of the Azure-managed organization must match or exceed the billing plan of the personal Neon account. For example, transferring from a Free account to a Scale account is allowed, but not Scale to Free. For detailed transfer steps, see [Transfer projects to an organization](/docs/manage/orgs-project-transfer). If the restrictions above prevent you from transferring your project, consider these options: -- Open a [support ticket](https://console.neon.tech/app/projects?modal=support) for assistance with transferring your Neon project (supported only for projects in [Azure regions](/docs/introduction/regions#azure-regions)). -- Migrate your data from an existing Neon project to a Neon project in your Azure-created region using `pg_dump` and `pg_restore`. Refer to [Migrate data from Postgres with pg_dump and pg_restore](/docs/import/migrate-from-postgres#run-a-test-migration) for instructions. +- Open a [support ticket](https://console.neon.tech/app/projects?modal=support) for assistance with transferring your Neon project (supported only for projects that reside in [Azure regions](/docs/introduction/regions#azure-regions)). +- Migrate your data to the Azure organization project using `pg_dump` and `pg_restore`. Refer to [Migrate data from Postgres with pg_dump and pg_restore](/docs/import/migrate-from-postgres#run-a-test-migration) for instructions. ## Changing your pricing plan From 7e33840d26a8d03b6a1e1c5b3d869b696e8c9148 Mon Sep 17 00:00:00 2001 From: Daniel Date: Fri, 20 Dec 2024 05:13:39 -0400 Subject: [PATCH 6/6] docs: edit --- content/docs/introduction/billing-azure-marketplace.md | 1 + content/docs/manage/orgs-project-transfer.md | 3 +-- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/introduction/billing-azure-marketplace.md b/content/docs/introduction/billing-azure-marketplace.md index 01fcb0165b..8509fe3829 100644 --- a/content/docs/introduction/billing-azure-marketplace.md +++ b/content/docs/introduction/billing-azure-marketplace.md @@ -90,6 +90,7 @@ You can transfer existing Neon projects to an Azure-created organization, but no - The Neon project must belong to a personal Neon account, not an organization. Transfers between organizations are not yet supported. - The Neon project must be in an [Azure region](/docs/introduction/regions#azure-regions). Azure-created Neon organizations do not support projects created in [AWS regions](/docs/introduction/regions#aws-regions). - The billing plan of the Azure-managed organization must match or exceed the billing plan of the personal Neon account. For example, transferring from a Free account to a Scale account is allowed, but not Scale to Free. +- The billing plan of the Azure-managed organization must match or exceed the billing plan of the personal Neon account you are transferring projects from. For example, attempting to transfer projects from a Scale plan personal account to a Free plan organization will result in an error. For detailed transfer steps, see [Transfer projects to an organization](/docs/manage/orgs-project-transfer). diff --git a/content/docs/manage/orgs-project-transfer.md b/content/docs/manage/orgs-project-transfer.md index 5fe96308e9..6815e341e6 100644 --- a/content/docs/manage/orgs-project-transfer.md +++ b/content/docs/manage/orgs-project-transfer.md @@ -14,8 +14,7 @@ A few important points to keep in mind: - You must be at least a Member of the selected Organization to transfer projects to it. - The number of projects you can transfer is limited by the target Organization plan's allowance. -- Projects can't be transferred between incompatible plans due to differences in usage allowances. For example, attempting to transfer projects from a Scale plan personal account to a Launch plan Organization will result in an error. -- The billing plan of the organization must match or exceed the billing plan of the personal Neon account you are transferring projects from. +- The billing plan of the organization must match or exceed the billing plan of the personal Neon account you are transferring projects from. For example, attempting to transfer projects from a Scale plan personal account to a Launch plan organization will result in an error. - If any organization members were already collaborators on the projects being transferred, we'll remove their collaborator access since they'll get full access as org members anyway. ## Transfer from the Neon Console