Skip to content
Kong Logo | Kong Docs Logo
search
  • We're Hiring!
  • Docs
    • Kong Gateway
    • Kong Konnect
    • Kong Mesh
    • Plugin Hub
    • decK
    • Kubernetes Ingress Controller
    • Insomnia
    • Kuma

    • Docs contribution guidelines
  • Plugin Hub
  • Support
  • Community
  • Kong Academy
Get a Demo Start Free Trial
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Plugin Hub
  • decK
  • Kubernetes Ingress Controller
  • Insomnia
  • Kuma

  • Docs contribution guidelines
  • 3.3.x (latest)
  • 3.2.x
  • 3.1.x
  • 3.0.x
  • 2.8.x
  • 2.7.x
  • 2.6.x
  • Older Enterprise versions (2.1-2.5)
  • Older OSS versions (2.1-2.5)
  • Archive (pre-2.1)

github-edit-pageEdit this page

report-issueReport an issue

enterprise-switcher-iconSwitch to OSS

On this pageOn this page
  • Prerequisites
  • Migration steps
Kong Gateway
2.8.x
  • Home
  • Kong Gateway
  • Install And Run
  • Migrating from Kong Gateway (OSS) to Kong Gateway
You are browsing documentation for an outdated version. See the latest documentation here.

Migrating from Kong Gateway (OSS) to Kong Gateway

As of Kong Enterprise version 2.1.x and later, it is no longer necessary to explicitly run the migrate-community-to-enterprise command parameter to to migrate all Kong Gateway (OSS) entities to Kong Enterprise. Running the kong migrations commands performs that migration command on your behalf.

Important: You can only migrate to a Kong Enterprise version that supports the same Kong Gateway (OSS) version.

Prerequisites

Warning: This action is irreversible, therefore it is strongly recommended to back up your production data before migrating from Kong Gateway (OSS) to Kong Enterprise.

  • If running a version of Kong Gateway (OSS) earlier than 2.8.x, upgrade to Kong 2.8.x before migrating Kong Gateway (OSS) to Kong Enterprise 2.8.x.

Migration steps

The following steps guide you through the migration process.

  1. Download Kong Enterprise 2.8.x and configure it to point to the same datastore as your Kong Gateway (OSS) 2.8.x node. The migration command expects the datastore to be up-to-date on any pending migration:

    kong migrations up [-c configuration_file]
    kong migrations finish [-c configuration_file]
    
  2. Confirm that all of the entities are now available on your Kong Enterprise node.

Thank you for your feedback.
Was this page useful?
  • Kong
    THE CLOUD CONNECTIVITY COMPANY

    Kong powers reliable digital connections across APIs, hybrid and multi-cloud environments.

    • Company
    • Customers
    • Events
    • Investors
    • Careers Hiring!
    • Partners
    • Press
    • Contact
  • Products
    • Kong Konnect
    • Kong Gateway
    • Kong Mesh
    • Get Started
    • Pricing
  • Resources
    • eBooks
    • Webinars
    • Briefs
    • Blog
    • API Gateway
    • Microservices
  • Open Source
    • Install Kong Gateway
    • Kong Community
    • Kubernetes Ingress
    • Kuma
    • Insomnia
  • Solutions
    • Decentralize
    • Secure & Govern
    • Create a Dev Platform
    • API Gateway
    • Kubernetes
    • Service Mesh
Star
  • Terms•Privacy
© Kong Inc. 2023