Chrome browser policies for profile migration not working

Ever since ManagedAccountsSigninRestriction was deprecated, the new replacement settings ProfileSeparationSettings and ProfileSeparationDataMigrationSettings do not seem to have the intended effect I require.

I previously had it setup so that a user with data in chrome(logged in a unmanaged profile or not) would get the option of migrating data from their existing profile into the new managed profile when signing in. It appears that does not happen.

When a user goes to add a profile, they sign in using their managed profile and it simply signs them in with no offer of data migration. This was working with the now deprecated policy with the below setting

• Force separate profile and forbid secondary managed accounts—The managed account is the primary account. The profile has no secondary accounts. When the profile is created, importing existing browsing data is allowed.

The replacement policies do not appear to work. They are applied at the browser/machine level before a user is logged in so it does not rely on a user being logged in for the new policies to take effect.

Can anyone help? Has anyone managed to get past this?