Migrating from API Connect v5 Public Cloud

Prepare to move to API Connect v10 by migrating your existing data from API Connect v5 Public Cloud.

The migration process provides tools to extract v5 data, arrange it for v10 formats, and load it onto a v10 deployment.

What can I migrate to v10?

The resources and assets associated with your v5 Public Cloud instance are included in the migration; for example, TLS profiles, APIs, Catalogs, Products, Consumers, subscriptions, user registries, and developer organizations. In addition, your billing data (Stripe integrations, paid Plans, and consumer payment methods) is migrated from v5 to v10.

Analytics data (including searches, visualizations, and dashboards) cannot be migrated due to changes in the Analytics feature. If you want to preserve your event data, you should export it from v5 Public Cloud using either CSV files or REST API calls as explained in the v5 Public Cloud documentation.

Important: The migration utility allows migration from v5 to a v10 v5-compatible gateway or v10 API Gateway. References to conversion of v5-compatible artifacts to v10 API Gateway refer to the v5-compatible artifacts that were initially from a v5 environment and were unpacked by the migration utility.

How do I migrate to v10?

You should be familiar with v5 Public Cloud architecture and requirements, and with the deployment configuration that you want to migrate to v10. The migration process requires you to have administrator-level access to both v5 Public Cloud and to your v10 on-premises deployment. During the migration process you can keep your existing v5 system active while you set up your v10 API Connect deployment.

The migration process involves the following high-level tasks, which are described in the topics that follow:

  1. Deploy API Connect v10.
  2. In your v5 Public Cloud instance, enable migration and download your data.
  3. Install the AMU (API Connect Migration Utility) tool on the computer where you downloaded your data.
  4. Unpack the downloaded data, which creates a directory structure containing YAML files where you can modify data for use in v10.
  5. Use the AMU tool to upload the modified data to your v10 API Connect deployment.
  6. Recreate billing integrations and other customizations as needed.