What steps are needed to upgrade from n8n Community Edition to the Enterprise version?

Below is an overview of what switching from a self-hosted Community Edition to a self-hosted Enterprise setup typically involves:

1. Obtaining an Enterprise License:
   You’ll need to purchase an enterprise license from n8n. Once you have the license key, you’ll use it to activate the additional enterprise features.

2. Upgrading to the Enterprise Edition Image:
   The Enterprise edition comes with additional features (for example, SSO, multi-main mode, external secrets, advanced workflow sharing, etc.) that aren’t available in the Community Edition. When self-hosting, this usually means switching to the Enterprise Docker image (or updating your deployment package if you use npm or other installation methods). Check the n8n pricing page for details on available deployment options for the Enterprise edition.

3. Configuration Changes:
   Once you have the enterprise image and a valid license, you will update your deployment to include the license key. Typically, this is done either via the user interface (for example, under Usage and Plan settings) or by providing the key as an environment variable during startup. This activation unlocks the extra features.

4. Ensuring Compatibility:
   Since you’re already using PostgreSQL and running in main mode on Docker, no major changes to your current configuration are required beyond switching the installation image and adding the enterprise license key. However, if you want to take advantage of advanced Enterprise features (like multi-main mode for high availability), you might need to review and update your deployment strategy (for example, configuring a load balancer, adding worker nodes, etc.) as outlined in the Enterprise documentation.

5. Further Considerations:

   • Review any additional documentation and the pricing page to make sure your planned enterprise setup meets your needs.
   • If you want to unlock specific enterprise-only features, check whether extra configuration steps (e.g., setting up external storage or SSO) are needed.
   • Always back up your existing instance and data before performing the upgrade.

In short, moving to the Enterprise edition when self-hosting involves acquiring a license, switching to the Enterprise deployment image, and updating your configuration to activate the enterprise features.

For specific setup instructions, please refer to the official enterprise deployment documentation or reach out to the n8n support team.

Below is an overview of what switching to a self‑hosted Enterprise setup generally implies compared to running the Community Edition:

---

1. Unlocking Additional Features

The Enterprise release unlocks a number of additional features that aren’t available in the Community Edition. These may include:

• Advanced authentication options such as SSO (SAML, LDAP)
• Custom variables, environments, and external secrets
• More granular sharing and collaboration controls (for workflows and credentials)
• Built‑in support for external storage of binary data
• Enhanced logging options such as log streaming
• Additional workflow and user management features (e.g. projects and version control via Git)

Before switching, review exactly which enterprise features you need and confirm that they address your current and future requirements.

---

2. Licensing and Updates

• Enterprise License:
  Unlike the Community Edition where you can register to unlock a few extra capabilities, the Enterprise version requires an active Enterprise license. This license is tied to your self‑hosted setup and is used to enable the premium features of the product.

• Docker Image:
  If you run n8n with Docker, you’ll typically need to update the image you’re using to the one provided for the Enterprise edition. This may involve pulling a different image or configuring environment variables specific to the Enterprise build. Check with n8n Enterprise documentation or your account representative for the exact Docker image details.

---

3. Configuration and Deployment Changes

Some configuration adjustments may be required when switching:

• Environment Variables & Settings:
  With the additional features, you may need to set extra environment variables or update your configuration files. For example, if you plan to use SSO or external secrets, there will be new environment variables or configuration steps compared to the Community Edition.

• User Management:
  The Enterprise version puts more emphasis on enhanced user and permission management. You might have to update your settings or deploy new components (for example, an SSO service) to integrate the new capabilities.

• Data Persistence & Upgrades:
  Since you’re already running with a persisted PostgreSQL backend and a main execution mode, the bulk of your current Docker and data persistence setup might remain the same. However, always back up your data before making any major changes and test the Enterprise configuration in a staging environment if possible.

---

4. Documentation and Support

• Review Enterprise Documentation:
  Before switching, consult the specific Enterprise documentation, as it will detail any differences in installation, configuration, and best practices that might impact your environment.

• Support Access:
  An Enterprise license typically comes with dedicated support options. If you’re planning the migration, having a support contact can help with any issues that might arise during the update.

---

Summary

Switching from the self‑hosted Community Edition to the Enterprise version mainly involves obtaining an Enterprise license, updating to the Enterprise‑specific Docker image (or installation package), and reconfiguring your environment to make use of premium features like advanced user management, SSO, and other enterprise‑only capabilities.

If you require further details while preparing your migration, it’s a good idea to consult the Enterprise documentation and reach out to n8n support or your account representative.

Hope this helps with your planning!