From 09859a4b4cee885d32daf5a0cdb6678e24a488e1 Mon Sep 17 00:00:00 2001 From: akshat5302 Date: Thu, 22 Jan 2026 20:26:28 +0530 Subject: [PATCH 1/3] Add note on cloud database and S3 storage during migration from Community to Commercial --- ...upgrade-from-community-managed-services.md | 55 +++++++++++++++++++ self-hosting/upgrade-from-community.mdx | 4 ++ 2 files changed, 59 insertions(+) create mode 100644 self-hosting/upgrade-from-community-managed-services.md diff --git a/self-hosting/upgrade-from-community-managed-services.md b/self-hosting/upgrade-from-community-managed-services.md new file mode 100644 index 00000000..1609be13 --- /dev/null +++ b/self-hosting/upgrade-from-community-managed-services.md @@ -0,0 +1,55 @@ +--- +title: Upgrade from Community to Commercial Edition +sidebarTitle: Upgrade to Commercial Edition +--- + +This guide walks you through updating your configuration to migrate existing data from a **Community** setup to a **Commercial** environment. + +## Step 1: Navigate to the Plane directory + +```bash +cd /opt/plane +``` + +## Step 2: Open the environment configuration file + +```bash +vim plane.env +``` + +## Step 3: Update the database connection + +1. Search for the `DATABASE_URL` environment variable. + +2. Replace the existing value with your **remote (managed) database URL**. + +Example: + +```env +DATABASE_URL=postgres://user:password@remote-host:5432/dbname +``` + +## Step 4: Update datastore (object storage) settings + +1. Search for the `#DATASTORE SETTINGS` section in `plane.env`. + +2. Update the following environment variables as required for your managed storage setup: + +```env +USE_MINIO=0 +AWS_REGION= +AWS_ACCESS_KEY_ID= +AWS_SECRET_ACCESS_KEY= +AWS_S3_ENDPOINT_URL= +AWS_S3_BUCKET_NAME=uploads +``` + +> ⚠ Setting `USE_MINIO=0` disables the local MinIO service and enables external object storage (e.g., S3 or S3-compatible services). + +## Step 5: Restart Plane services + +Apply the changes by restarting the services: + +```bash +prime-cli restart +``` \ No newline at end of file diff --git a/self-hosting/upgrade-from-community.mdx b/self-hosting/upgrade-from-community.mdx index a95b5936..9b5fc9af 100644 --- a/self-hosting/upgrade-from-community.mdx +++ b/self-hosting/upgrade-from-community.mdx @@ -16,6 +16,10 @@ The instructions provided on this page are specific to installations using Docke - Install the [Commercial Edition](/self-hosting/methods/docker-compose#recommended-edition) on a fresh machine, not the one running the Plane Community Edition. - Be sure to log in as the root user or as a user with sudo access. The `/opt` folder requires sudo or root privileges. + +No backup is required if you are using a cloud database and S3 storage while migrating from Community to Commercial. Simply point your Commercial instance to the same cloud database and S3 storage. Refer to [this guide](https://app.plane.so/plane/wiki/5e4a0b13-fc55-4a3f-896f-9f0a829bfc8b/) for more details. + + ## Back up data on Community instance 1. Download the latest version of `setup.sh`. ```bash From a19c0e89d03179c9d317d3ac373973a7ad56cc8f Mon Sep 17 00:00:00 2001 From: danciaclara Date: Fri, 23 Jan 2026 13:43:45 +0530 Subject: [PATCH 2/3] review fixes --- self-hosting/methods/docker-compose.mdx | 2 +- ...upgrade-from-community-managed-services.md | 55 ------ self-hosting/upgrade-from-community.mdx | 156 ++++++++++++------ 3 files changed, 105 insertions(+), 108 deletions(-) delete mode 100644 self-hosting/upgrade-from-community-managed-services.md diff --git a/self-hosting/methods/docker-compose.mdx b/self-hosting/methods/docker-compose.mdx index 21136624..03e6f65e 100644 --- a/self-hosting/methods/docker-compose.mdx +++ b/self-hosting/methods/docker-compose.mdx @@ -32,7 +32,7 @@ Ensure you're using the **latest version of Docker Compose**. Check your Docker curl -fsSL https://prime.plane.so/install/ | sh - ``` 3. Follow the instructions on the terminal. Hit `Enter` or `Return` to continue. - 4. Enter the domain name where you will access the Plane app in the format `domain.tld` or `subdomain.domain.tld`. If you are using a paid plan, the domain linked to the license can’t be changed later. + 4. Enter the domain name where you will access the Plane app in the format `domain.tld` or `subdomain.domain.tld`. 5. Choose one of the options below: - **Express**: Plane installs with the default configurations. - **Advanced**: You can customize the database, Redis, storage and other settings. diff --git a/self-hosting/upgrade-from-community-managed-services.md b/self-hosting/upgrade-from-community-managed-services.md deleted file mode 100644 index 1609be13..00000000 --- a/self-hosting/upgrade-from-community-managed-services.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Upgrade from Community to Commercial Edition -sidebarTitle: Upgrade to Commercial Edition ---- - -This guide walks you through updating your configuration to migrate existing data from a **Community** setup to a **Commercial** environment. - -## Step 1: Navigate to the Plane directory - -```bash -cd /opt/plane -``` - -## Step 2: Open the environment configuration file - -```bash -vim plane.env -``` - -## Step 3: Update the database connection - -1. Search for the `DATABASE_URL` environment variable. - -2. Replace the existing value with your **remote (managed) database URL**. - -Example: - -```env -DATABASE_URL=postgres://user:password@remote-host:5432/dbname -``` - -## Step 4: Update datastore (object storage) settings - -1. Search for the `#DATASTORE SETTINGS` section in `plane.env`. - -2. Update the following environment variables as required for your managed storage setup: - -```env -USE_MINIO=0 -AWS_REGION= -AWS_ACCESS_KEY_ID= -AWS_SECRET_ACCESS_KEY= -AWS_S3_ENDPOINT_URL= -AWS_S3_BUCKET_NAME=uploads -``` - -> ⚠ Setting `USE_MINIO=0` disables the local MinIO service and enables external object storage (e.g., S3 or S3-compatible services). - -## Step 5: Restart Plane services - -Apply the changes by restarting the services: - -```bash -prime-cli restart -``` \ No newline at end of file diff --git a/self-hosting/upgrade-from-community.mdx b/self-hosting/upgrade-from-community.mdx index 9b5fc9af..f17e4b62 100644 --- a/self-hosting/upgrade-from-community.mdx +++ b/self-hosting/upgrade-from-community.mdx @@ -6,9 +6,6 @@ The Commercial edition comes with the free plan and the flexibility to upgrade t **IMPORTANT** - -Make sure you already have Commercial Edition installed on a fresh machine before starting this migration. If you haven’t installed it yet, follow our [Commercial Edition](/self-hosting/methods/docker-compose#recommended-edition) installation guide first. - The instructions provided on this page are specific to installations using Docker. If you are running Plane on Kubernetes, you'll need to manually create a database dump and back up your file storage by copying the relevant volumes or storage paths. @@ -16,52 +13,107 @@ The instructions provided on this page are specific to installations using Docke - Install the [Commercial Edition](/self-hosting/methods/docker-compose#recommended-edition) on a fresh machine, not the one running the Plane Community Edition. - Be sure to log in as the root user or as a user with sudo access. The `/opt` folder requires sudo or root privileges. - -No backup is required if you are using a cloud database and S3 storage while migrating from Community to Commercial. Simply point your Commercial instance to the same cloud database and S3 storage. Refer to [this guide](https://app.plane.so/plane/wiki/5e4a0b13-fc55-4a3f-896f-9f0a829bfc8b/) for more details. - - -## Back up data on Community instance -1. Download the latest version of `setup.sh`. - ```bash - curl -fsSL https://github.com/makeplane/plane/releases/latest/download/setup.sh -o setup.sh - ``` - -2. Run the setup.sh backup script to take the backup of the Community Edition instance. - ```bash - ./setup.sh backup - ``` -3. When done, your data will be backed up to the folder shown on the screen. - e.g., `/plane-selfhost/plane-app/backup/20240522-1027` - This folder will contain 3 `tar.gz` files. - - `pgdata.tar.gz` - - `redisdata.tar.gz` - - `uploads.tar.gz` - -4. Copy all the three files from the server running the Community Edition to any folder on the server running the Commercial Edition. - - e.g., `~/ce-backup` - -## Restore data on Commercial instance -1. Start any command-line interface like Terminal and go into the folder with the back-up files. - ``` - cd ~/ce-backup - ``` -2. Copy and paste the script below on Terminal and hit Enter. - ``` - TARGET_DIR=/opt/plane/data - sudo mkdir -p $TARGET_DIR - for FILE in *.tar.gz; do - if [ -e "$FILE" ]; then - tar -xzvf "$FILE" -C "$TARGET_DIR" - else - echo "No .tar.gz files found in the current directory." - exit 1 - fi - done - - mv $TARGET_DIR/pgdata/ $TARGET_DIR/db - mv $TARGET_DIR/redisdata/ $TARGET_DIR/redis - mkdir -p $TARGET_DIR/minio - mv $TARGET_DIR/uploads/ $TARGET_DIR/minio/uploads/ - ``` -3. This script will extract your Community Edition data and restore it to `/opt/plane/data`. + + + + This upgrade path is for installations using Plane's default PostgreSQL database and MinIO object storage. + + + ## Back up data on Community instance + 1. Download the latest version of `setup.sh`. + ```bash + curl -fsSL https://github.com/makeplane/plane/releases/latest/download/setup.sh -o setup.sh + ``` + + 2. Run the setup.sh backup script to take the backup of the Community Edition instance. + ```bash + ./setup.sh backup + ``` + 3. When done, your data will be backed up to the folder shown on the screen. + e.g., `/plane-selfhost/plane-app/backup/20240522-1027` + This folder will contain 3 `tar.gz` files. + - `pgdata.tar.gz` + - `redisdata.tar.gz` + - `uploads.tar.gz` + + 4. Copy all the three files from the server running the Community Edition to any folder on the server running the Commercial Edition. + + e.g., `~/ce-backup` + + ## Restore data on Commercial instance + 1. Start any command-line interface like Terminal and go into the folder with the back-up files. + ``` + cd ~/ce-backup + ``` + 2. Copy and paste the script below on Terminal and hit Enter. + ``` + TARGET_DIR=/opt/plane/data + sudo mkdir -p $TARGET_DIR + for FILE in *.tar.gz; do + if [ -e "$FILE" ]; then + tar -xzvf "$FILE" -C "$TARGET_DIR" + else + echo "No .tar.gz files found in the current directory." + exit 1 + fi + done + + mv $TARGET_DIR/pgdata/ $TARGET_DIR/db + mv $TARGET_DIR/redisdata/ $TARGET_DIR/redis + mkdir -p $TARGET_DIR/minio + mv $TARGET_DIR/uploads/ $TARGET_DIR/minio/uploads/ + ``` + 3. This script will extract your Community Edition data and restore it to `/opt/plane/data`. + + + + + This upgrade path is for installations using external or managed database and object storage services (like AWS RDS and S3). Since your data already lives in external services, you only need to update your configuration — no backup and restore required. + + ## Update configuration for Commercial Edition + + 1. Open the `plane.env` file located at `/opt/plane/plane.env`. + + 2. Configure database connection. + + 1. Find the `DATABASE_URL` environment variable. + 2. Verify it points to your external database: + ```env + DATABASE_URL=postgresql://user:password@your-db-host:5432/plane + ``` + + If you need to change it, update the value with your managed database connection string. + + 3. Configure object storage + + 1. Find the `#DATASTORE SETTINGS` section in `plane.env` + 2. Update these environment variables for your external storage: + ```env + USE_MINIO=0 + AWS_REGION=us-east-1 + AWS_ACCESS_KEY_ID= + AWS_SECRET_ACCESS_KEY= + AWS_S3_ENDPOINT_URL=https://s3.amazonaws.com + AWS_S3_BUCKET_NAME=plane-uploads + ``` + + :::info + Setting `USE_MINIO=0` disables the local MinIO service and enables external object storage (S3 or S3-compatible services). + ::: + + 4. Restart Plane services to apply the configuration: + ```bash + prime-cli restart + ``` + + Your Commercial Edition instance is now connected to your existing external database and storage. + + + + + +## What's next + +Now that you've upgraded to Commercial Edition: + +- [Activate a paid plan license](/self-hosting/manage/manage-licenses) if you have one. \ No newline at end of file From 7913d437d2fc0f3f20fa5847ff3ba3a5db4493b5 Mon Sep 17 00:00:00 2001 From: danciaclara Date: Fri, 23 Jan 2026 13:45:42 +0530 Subject: [PATCH 3/3] minor fixes --- self-hosting/upgrade-from-community.mdx | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/self-hosting/upgrade-from-community.mdx b/self-hosting/upgrade-from-community.mdx index f17e4b62..ccaa45f4 100644 --- a/self-hosting/upgrade-from-community.mdx +++ b/self-hosting/upgrade-from-community.mdx @@ -111,9 +111,6 @@ The instructions provided on this page are specific to installations using Docke - ## What's next -Now that you've upgraded to Commercial Edition: - -- [Activate a paid plan license](/self-hosting/manage/manage-licenses) if you have one. \ No newline at end of file +- [Activate a paid plan license](/self-hosting/manage/manage-licenses). \ No newline at end of file