Example: Simple migration

This example demonstrates how to migrate API Versions or Proxies from Classic APIM to API Management 3.0:

  1. From the left navigation pane in API Management 3.0, open the Migration Tool.
  2. Select one or more API Versions or Proxies to migrate.
    Select one or more API Versions or Proxies to migrate

  3. Click Next.
  4. Select the target location for each new Service.
    Select target location

  5. Optionally, you can exclude specific assets by clicking the Assets to migrate field, expanding the tree and deselecting them.
    Important: Any deselected tasks don't have corresponding Service endpoints created.

    Deselecting assets

  6. We'll leave the Migrate policies toggle enabled for the selected items. The Migration Tool converts the policies to rules and groups the migrated policies by origin, such as per version or per endpoint. If you disable the toggle, you can instead create a new APIM 3.0 Policy to associate with the new Service.
    Migrate policies toggle enabled, with migrated policies grouped by origin

  7. Click Next and review your selections:
    Review migration selections

  8. Click Back to make changes, or click Migrate. Migration can take from a few seconds to several minutes, depending on the number of assets migrated.
  9. In the Services Catalog, we find the new Services in the selected project:
    Migrated Services

  10. Expand a migrated Service and click a version to view the endpoints, Policies, and other related assets.