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 | Equivalent after migration to APIM 3.0 |
|---|---|
| API Version | Service version |
| Application | Application |
| Endpoint account (Snap account) | Copied to the new Service project. |
| File | Copied to the new Service project. |
| Mapping rule expression | Advanced routing rule created 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 | 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 | Policies become rules, with the Policy containing them associated with the Service version endpoint. |
| Proxy-level policy | Policy rule, with the Policy containing it associated with the Service version. |
| Snaplex | The new Service version has the same Snaplex selected. |
| Subscriptions (pending and approved) | Pending and approved subscriptions configured for API key authentication with a time-to-live of 365 days. The owner of the Classic APIM asset receives an email notification of successful migration. |