General migration rules

Generally, this section describes the state of a newly created repository database. In case of existing repository databases these migration rules are applied:

• Roles or groups will not be renamed by the migration, because role names might be used in conditional actions and formatting in Application Studio reports triggered by the _currentRoles system variable.
• Permissions will not be assigned to or removed from existing roles in migrated repositories.
• Roles will not be assigned to or removed from groups of existing repositories.
• New built-in roles are created in existing models of migrated repositories. These roles are not assigned to any users or groups.
• New repositories have only new built-in roles and groups.
• Newly created models in migrated repositories have only new built-in Application Roles.
• Both new and updated repositories behave the same way when new models are created. Existing models will not be modified, so the permissions assignments will be preserved as set up.