One of the errors we are seeing a fair bit is 'customer login ### is duplicated' and when reviewing the accounts one of the login entries is marked as Inactive.
Does this mean that the migration is not recognising when logins are inactive? In the migration training this error was mentioned as one that has to be fixed but I'm not sure how, we try not to delete information if possible.
Hi Suzanne,
Tess provides SQL code and advice around this issue in the v10_to_v11_Migration_Toolkit documentation.
One of the suggestions is creating a new login type and applying this new type to the dupes. This is the road we went down as we too didn't want to delete the dupes (yet).
Hope that helps!