Migration reference
The following table organizes APIM assets alphabetically and describes the equivalent API Composer asset after migration.
| APIM asset or property | Equivalent after migration to API Composer |
|---|---|
| API Version | Service version. |
| 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: Currently the migration of a mapping rule expression from APIM depends on
whether the Proxy was generated from a specification. If it wasn't, the expression can't be
migrated and you will have to reproduce it manually. |
| 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. |