Preparing to migrate from API Connect V5

Deploy Cloud Pak for Integration with the API management capability and plan your migration.

Deploy Cloud Pak for Integration and the API management capability

See the Installation section for details on installing the Cloud Pak for Integration framework and the API management capability, which provides the API Connect features.

Update your API Connect V5 deployment to version 5.0.8.7 or later

Before migrating data from API Connect V5, ensure that your deployment is at least at Version 5.0.8.7. Earlier versions of API Connect are not supported by the migration utility. For information on upgrading your V5 deployment, see Upgrading your API Connect cloud in the API Connect V5 documentation.

Plan your migration

Review the following migration resources:
- API Connect Upgrade Central: v5 to v10 provides a high-level view of the migration process.
- Migrating a Version 5 deployment provides detailed planning and migration information, including the steps you will follow to migrate V5 data to Cloud Pak for integration.
- Converting APIs to native DataPower API gateway documentation provides additional information about porting your v5 API assemblies to the native V10 API gateway service that is used in Cloud Pak for Integration.
Review the Migration considerations to understand what data can be migrated, what customizations must be recreated after migration, and differences between V5 and V10 data.
Plan for downtime.
The migration process allows for your V5 gateways to remain functional, allowing API traffic to continue until you alter the load balancer/DNS to direct API traffic to new v10 gateways in your Cloud Pak for Integration deployment. The details of how the change-over is performed will depend on your specific networking infrastructure.

The API Connect Migration Utility provides the flexibility to incrementally migrate by provider organization or by catalog, which reduces risks and supports multiple project team schedules.