22.02 HF2 to HF8 inclusive
22.12 Base to HF2 inclusive
After enabling Classic to New Experience Realm Migration by following the below article you may not see all expected Realms to be Migrated
There are several Realm PostAuth types which are not supported to be Migrated from Classic to New Experience at this point in time, please see the below direct link for this list of Realm types
If the Realm(s) which you are missing in your environment is not of a PostAuth type listed in the document above it could be because the Migration Tool is unable to read the Realm correctly.
If you check the log file in the D:\SecureAuth\AdminApiLogs folder and see an error similar to the below it could be something as simple as the Realm foldername
Error|SecureAuth.Admin.API.Controllers.API.V3.MigrationController|Error trying to get migration info for realm 'secureauth5'|System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.Convert.ToInt32(String value)
at SecureAuth.Admin.API.Controllers.API.V3.MigrationController.<>c__DisplayClass7_0`1.<GetAndIterateClassicRealms>b__1(String migratableRealm)
To fix this particular problem simply rename the Realm folder to ensure it starts with a capital S
As an example, change secureauth5 to SecureAuth5
Once you have changed the name of the folder come out of the Classic Migration page and go back to it again, the Realm should now be present for Migration to New Experience
This has been fixed in 22.12 HF3 (EE-3175)
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.