How to Migrate Licenses from QPP NextGen 2.x to QPP NextGen 3.x
Available License Types
Author
Access
Admin
Author
Contributor
Consumer
Docurated
Generate New License Codes
To enable migration from QPP NextGen 2.x to 3.x, you must generate new license codes.
For example, if you require 10 Admin licenses and 12 Author licenses, you must generate two new license codes – NALP_LICENSE_ADMIN and NALP_LICENSE_AUTHOR and set the maximum number of active clients allowed for each license type to 10 and 12, respectively.
Note: You can increase or decrease the number of licenses required as per requirement.
To generate new license codes:
- Contact Quark and submit a request to generate new license codes and provide the following information:
- Type of licenses required (Admin, Author, Contributor, Consumer, Docurated)
- The number of active clients allowed for each license type
- Once Quark generates the new license codes, you will receive them for each license type.
- Open the configuration file contentplatform.yml or contentplatform_sso.yml (depending on which file you are using), and under the services qcplicensingservice and qcpdbmigrator set the following variables names:
- nalpeiron.licenseCode.admin: “your license code for admin”
- nalpeiron.licenseCode.author: “your license code for author”
- nalpeiron.licenseCode.contributor: “your license code for contributor”
- nalpeiron.licenseCode.consumer: “your license code for consumer”
- nalpeiron.licenseCode.docurated: “your license code for docurated”

Figure: A sample code snippet under the service qcpdbmigrator where you must add new license codes. Similarly, you must add the license codes under the service qcplicensingservice.
Note: To migrate to a minimal environment, only the license code nalpeiron.licenseCode.author is required.
License mapping in different migration scenarios
| Scenario | QPP NextGen 2.x | QPP NextGen 3.x | ||||
|---|---|---|---|---|---|---|
| System Admin (Or the default user with User ID = 1 | Author with Administrator role | Admin with Administrator role | ||||
| Custom Admin | Author with Administrator role | Admin with Administrator role | ||||
| Roles not associated to a user | A role was created but was not assigned to any user. | Roles that are not associated with any user or group in 2.x do not have a license associated with them. You can assign a license to such roles after migration through the dropdown field Select License Type in Roles tab under the Admin page. | ||||
| Roles associated to a user | Author
| Author
| ||||
| Roles associated to a group | A role was assigned to a group containing several users with different license types. | The license is assigned based on the user in the group whose license is the lowest in the license hierarchy*. For example, on 2.x the role X is associated with a group with two users – U1 and U2. U1 has the Author license and role Y. U2 has the Access (Docurated) license with role Z. On migration to 3.x, the role X is assigned the Docurated license. Note: To change the license assigned to a role (associated to a group), as an administrator, you first must remove the users from the group who have licenses that are lower in the hierarchy from the license you want to assign to the role. | ||||
| Demoting a user’s license | An administrator can demote a user’s license irrespective of the group they are part of. | An administrator can demote a user’s license if the user is not part of a group that has a role with a higher license in the license hierarchy. In such cases, the administrator can only demote the user’s license by first removing the user from the concerned group. | ||||
| License and role assignment | License and role assignments are independent of each other | QPP NextGen follows role-based licensing system; meaning, an administrator can keep or add a user without assigning a license by first assigning the role with no privileges to the user. However, if the user is already part of a group with an associated role, the administrator must first remove the user from the group. |
* Lowest in the license hierarchy means the license that has the least number of privileges.
License Hierarchy
- Admin (most/all privileges)
- Author
- Contributor
- Consumer (least privileges)
- Docurated