Konnect Cloud

Import Kong Gateway Entities into Konnect Cloud

If you are an existing Kong Gateway user looking to use Konnect as your cloud-hosted control plane, you can use decK to import your Kong Gateway entity configuration into a runtime group in your Konnect organization.

You can also use this guide to migrate from konnect.konghq.com to cloud.konghq.com.

Afterward, you must manually move over:

Dev Portal files, developer accounts, and applications
Application registrations
Convert roles and permissions into Konnect teams
Certificates
Custom plugins

You cannot import unsupported plugins.

Prerequisites

Konnect Cloud account credentials.
decK v1.12 or later installed.

Import entity configuration

Use deck to import entity configurations into a runtime group.

When you provide any Konnect flags, decK targets the cloud.konghq.com environment by default. If you want to target the konnect.konghq.com environment instead, use the --konnect-addr flag.

Make sure that decK can connect to your Konnect account:
```
 deck ping \
   --konnect-runtime-group-name default \
   --konnect-email {YOUR_EMAIL} \
   --konnect-password {YOUR_PASSWORD}
```
If the connection is successful, the terminal displays the full name of the user associated with the account:
```
 Successfully Konnected as Some Name (Org Name)!
```
You can also use decK with Konnect more securely by storing your password in a file, then either calling it with --konnect-password-file /path/{FILENAME}.txt, or adding it to your decK configuration file under the konnect-password option along with your email:
```
 konnect-password: {YOUR_PASSWORD}
 konnect-email: {YOUR_EMAIL}
```
The default location for this file is $HOME/.deck.yaml. You can target a different configuration file with the --config /path/{FILENAME}.yaml flag, if needed.

The following steps all use a .deck.yaml file to store the Konnect credentials instead of flags.
Export configuration:
From Kong Gateway

From konnect.konghq.com
Run deck dump:
deck dump
Run deck dump and point decK at the konnect.konghq.com environment:
deck dump \ --konnect-addr https://konnect.konghq.com \ --konnect-email {YOUR_EMAIL} \ --konnect-password {YOUR_PASSWORD}
This command outputs Kong Gateway’s object configuration into kong.yaml by default. You can also set --output-file /path/{FILENAME}.yaml to set a custom filename or location.
Open the file. If you have any of the following in your configuration, remove it:
- Any _workspace entries: There are no workspaces in Konnect. For a similar concept, see runtime groups.
- Configuration for the Portal App Registration plugin: App registration is supported in Konnect, but not through a plugin, and decK does not manage it.
- Any other unsupported plugins:
  - OAuth2 Authentication
  - Apache OpenWhisk
  - Vault Auth
  - DeGraphQL
  - GraphQL Rate Limiting Advanced
  - Key Authentication Encrypted
Preview the import with the deck diff command, pointing to the runtime group that you want to target:
```
 deck diff --konnect-runtime-group-name default
```
If you’re not using the default kong.yaml file, specify the filename and path with --state /path/{FILENAME}.yaml.
If you’re satisfied with the preview, run deck sync:
```
 deck sync --konnect-runtime-group-name default
```
If you don’t specify the --konnect-runtime-group-name flag, decK targets the default runtime group. If you have more than one runtime group in your organization, we recommend always setting this flag to avoid accidentally pushing configuration to the wrong group.
Log in to your Konnect Cloud account.
From the left navigation menu, open Runtime Manager, then open the runtime group you just updated.
Look through the configuration details of any imported entities to make sure they were migrated successfully.

Migrate data planes

You can keep any data plane nodes that are:

Running Kong Gateway (Enterprise, include free mode)
Are at least version 2.5 or higher

Turn any self-managed nodes into cloud data plane nodes by registering them through the Runtime Manager and adjusting their configurations, or power down the old instances and create new data plane nodes through Konnect Cloud.

Follow the runtime setup guide for your preferred deployment type.
Once you have created or converted the data plane nodes, kong stop your old Gateway runtimes, then shut them down.
If any of the old nodes have connected PostgreSQL or Cassandra instances, you can shut them down now.

Post-migration tasks

See the following docs to set up any additional things you may need:

Dev Portal files: You can migrate API specs and markdown service descriptions into Service Hub using the Konnect Cloud GUI. Each Konnect service accepts one markdown description file, and each service version accepts one API spec. See Dev Portal Service Documentation.
Dev Portal applications and developers: If you have developers or applications registered through the Portal, those developers need to create new accounts in Konnect Cloud and register their applications in the new location.
- Create Dev Portal accounts
- Enable application registration: App registration in Konnect Cloud works through a different mechanism than in self-managed Kong Gateway. Enable app registration on each service that requires it.
- Publish services to the Dev Portal: The Dev Portal is automatically enabled on a Konnect Cloud org (Plus or Enterprise tier). Publish your services to the Dev Portal.
Prepare custom plugins for migration: Custom plugins are supported in Konnect Cloud, but with limitations. As long as your plugins fit the criteria, or if you can adjust them to do so, contact Kong Support to get the plugin manually added to your account.
Review and set up teams and roles: Konnect Cloud groups and roles don’t map directly to Kong Gateway teams and roles. Set up teams to mirror your Kong Gateway groups, then invite users to your org and assign them to a team on invite.