Migration reference
The following table organizes Classic APIM assets alphabetically and describes the equivalent APIM 3.0 asset after migration.
| Classic APIM asset or property | Migration results |
|---|---|
| API Version | Creates a Service Version. |
| API Version policies | Converts policies to rules. Adds API-level rules to a single API-level policy and adds version-level rules to a separate policy associated with each version. |
| Application | Migrates the Application. |
| Endpoint account (Snap account) | Copies the account to the new Service project. |
| File | Copies the file to the new Service project. |
| Mapping rule expression | Creates an advanced routing rule from a Header, Path,
Query Parameter, or HTTP Method condition. Important: For unpublished APIs or Proxies, migration creates all HTTP methods
with empty definitions. For published APIs and Proxies, migration creates only the
defined HTTP methods. |
| Proxy | Creates a Service Version that includes all Proxy endpoints. After migrating a Proxy that includes Task URLs, you can change them to local endpoints to avoid an extra network call. Refer to Runtime architecture for more information about endpoint execution. |
| Proxy endpoint policies | Converts policies to rules. Creates a policy for each endpoint from that endpoint's rules. |
| Proxy-level policies | Converts policies to rules and adds them to one policy associated with the Service Version. |
| Snaplex | Selects the same Snaplex for the new Service Version. |
| Subscriptions (pending and approved) | Migrates pending and approved subscriptions, configured for API key authentication with a time-to-live of 365 days. Sends the owner of the Classic APIM asset an email notification of successful migration. |