Why did Storage Migration Service apply the wrong local group SID to a share permission?

I'm testing out Storage Migration Service to transfer files from a Windows Server 2016 install to a Windows Server 2022 install. The source system has some permissions set at the Share level as well as NTFS. Inventory and Transfer completed fine; I did not do the Cutover in this test environment. I used the destination server as the Orchestrator. When checking the share permissions on the destination system (using the File & Storage Services component in Server Manager) I noticed that while the share permission that was assigned to a domain account looks fine, the permission entry that corresponds to a local group shows only the SID. I can see that the local group was created on the destination server (both from Computer Manager and checking the SMS log) and the SID is in fact different than the SID displayed on the Share. Most of the multipart SID is correct for the destination server, but the last section (after final dash) has the value for that group from the source server rather than the value from the newly created group on the destination server; so there is no actual group matching the SID on the destination server. Is this expected behavior? Any solutions? thanks Martin