Migrating from v3 to v4
Migration from Entitlement v3 to Entitlement v4 is supported by two pillars: A unidirectional synchronization of data from Entitlement v3 to Entitlement v4. An Entitlement v3 proxy allows entitlements stored in Entitlement v4 to be accessed through Entitlement v3 APIs during our transition to Entitlement v4.
See EMS v3 to Entitlement v4 - Program initiation deck for more details about the migration program.
This migration path is specific to named user licenses. Pooled license information in v3 will not be migrated as Entitlement v4 does not support pooled licenses and other concurrent licensing models at this time.
Entities that will be migrated to Entitlement v4 are:
- Entitlements
- Licenses
- Features
- Products
For migrating users, the Entitlement v4 team will do most of the migration outside of information in the Data Migration Workflow.
Changes to API calls
This spreadsheet provides information regarding the differences between API calls in EMS v3 and Entitlement v4.
Entity mapping from v3 to v4
| Status | Legacy Name | Entitlement v4 Name |
|---|---|---|
| New | N/A | Service |
| New | N/A | Bundles |
| Mapped | Product | Product |
| Mapped | Feature | Feature |
| Mapped | Entitlement | Entitlement |
| Migrated | Activations | Licenses |