# user and role migration

GLOSSARY, read 10 Nov 2026

**Definition.** User and role migration recreates the accounts and permissions of the old platform in the new one. Kenna's API has role endpoints, roles carry asset group scope, and a role cannot be deleted while a user is connected to it. Map roles first, then users, and test with real accounts.

Roles in Kenna are tied to asset groups, so a role mapping depends on the tag and group mapping being done first. A role that points to a group that does not exist yet gives a user the wrong view or none.

Use the cutover to remove accounts that no one has used. Single sign-on groups, if the target supports them, make the later joiners and leavers cheaper.

## A sourced example

Kenna's Update Role and Delete Role reference pages state that updating a role's asset groups replaces the current list and that a role connected to a user cannot be deleted.

## Related terms

- [tag migration](/glossary/tag-migration/)
- [asset identity matching](/glossary/asset-identity-matching/)
- [saved reports](/glossary/saved-reports/)
- [migration runbook](/glossary/migration-runbook/)

## Sources

- Source for the example: user and role migration: https://apidocs.kennasecurity.com/reference/update-role.md (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/user-and-role-migration/
