Migrating from EMSv3 to EMS v4, EMS v4 to EMS v4 (Mixed Provisioning to EMS v4 Provisioning), and Manual/Any Legacy to EMS v4
Migration from Entitlement v3 to Entitlement v4 is supported by a unidirectional synchronization of data from:
- Entitlement EMS v3 to Entitlement EMS v4
- Entitlement EMS v4 to Entitlement EMS v4 and
- Manual or any legacy system to Entitlement v4
For more information about the migration program, see EMS v3 to Entitlement v4 - Program initiation deck.
This migration path is specific to named user licenses. The pooled license information in EMSv3 will not be migrated as Entitlement v4 does not support pooled licenses and other concurrent licensing models at this time.
The entities that will be migrated to Entitlement v4 are:
- Entitlements
- Licenses
For migrating users, the Entitlement v4 team will do most of the migration outside of information in the Data Migration Workflow. To be more specific, the Data Migration team will effortlessly handle bulk migration using external scripts, manual verification, and out-of-band processes that fall outside the automated workflow.
Changes To API Calls
This spreadsheet provides information about the differences between API calls in EMS v3 and Entitlement v4.
Entity Mapping From v3 To v4
| Status | Legacy Name | Name of the Entitlement (v4) |
|---|---|---|
| New | N.A. | Service |
| New | N.A. | Bundles |
| Mapped | Product | Product |
| Mapped | Feature | Feature |
| Mapped | Entitlement | Entitlement |
| Mapped | Activations | Licenses |