After Migration, whats the difference between 'Administrators' and 'Administrators (migrated)' role

Question

We just migrated to the cloud.  When I'm assigning roles to people, I made an assumption (I know, assumption) that the 'Administrators' and 'Administrators (migrated)' roles were the same.  But I'm finding they are not.  How can I compare the two roles and clean them up so they are the same?

I'm seeing weird functionality differences, and if I'm in the Administrators role, stuff doesn't work, but using Administrators (migrated) it does.

I would have 'assumed' again that any administrator privileges on our server version would have migrated to the Administrator role, but that doesn't seem to be the case.

Thanks,

Dan Breyen · Answer

I'm assuming I can't just rename the role, as the Administrators role already exists. The 'Users' and 'Developer' Roles weren't cloned as (migrated).  Seeing the Cloud 'Adminstrators' role and the 'Administrators (migrated)' role makes me think there are items in 'Administrators' that need to be setup for Cloud functionality.  BUT this means there are settings in 'Administrators' that need to be put into 'Administrators (migrated)' in order to get the migrated role to work, and vis versa.  I would like to get 'Administrators' to work and remove the migrated version, but I need to make sure all the changes from the migrated version get moved into the new cloud version.

Blue Ridge Consultants · Answer

Normally the xyz (migrated) roles are created when a duplicate role already exists in the cloud (or has already been created through a test migration).  So in your case, the Administrators (migrated) role would be the good one with permissions already granted while the Administrators role is the pre-defined one already in the cloud.

I would recommend trying to rename Administrators (migrated) to Administrators.