You have no notifications.
Hi,
Migrating K13 users to Xbk members is pretty straightforward, but I haven't read anything about where K13 user roles are assigned in Xbk.
Has anyone had experience with this?
Environment
All the details are in the documentation for the Xperience by Kentico Kentico Migration Tool.
- Roles
- Only roles that have at least one user whose Privilege level is set to Editor and above are migrated.
- Because Xperience by Kentico uses a different permission model, no existing role permissions or UI personalization settings are migrated. After the migration, the permissions for each role must be configured again.
To prevent this role data from being lost, I went with the following approach:
For the relevant role, I created a custom field (boolean) (https://docs.kentico.com/13/managing-users/adding-custom-fields-to-users#adding-custom-fields-to-users). This extra field acts as a kind of dummy field for the migration tool because the migration tool does create this field in the Xbk database.
In the migration tool, I adjusted the MemberInfoMapper so that when this field is mapped, true or false is set here if the K13 user has this role.
This results in XbK in a new boolean field for the member (https://docs.kentico.com/documentation/developers-and-admins/development/registration-and-authentication/add-fields-to-member-objects). We can now adjust the Xbk code so that we can make use of the extra field on the ExtendedApplicationUser.
Hope this helps
Adding some additional details - the Kentico Migration Tool does not support migrating live site member roles because Xperience by Kentico does not have any built-in support for managing this kind of data.
In Kentico Xperience 13, marketer administration users and website visitor users were all the same thing, differentiated by their permission to access the Xperience administration.
In Xperience by Kentico, users refer to people logging into the administration UI and members refer to website visitors who have accounts. The data is separate, as are the APIs to manage them.
We are planning to add native website membership management in a future product update.
In the meantime is there is:
To response this discussion, you have to login first.
