Handle Multiple Domain during SharePoint Migration

This blog describes the problem statement and resolution i.e. How to handle multi-domain issue during SharePoint Migration.

This is quite interesting & common scenario, which we face in almost all migration project i.e. On-Premises to On-Premises or On- Premises to Online.

SharePoint Migration project easily enters into escalation mode due to multi domain users after entire application migration.

Somehow application team tries to convince the business user to adapt or change the User Name with a NEW domain. This is something no business user ready to accept.

Scenario illustrated in below diagram:-

Problem Statement:-

Before Migration, Project was using Domain OLD.com and application URL like https://sharepoint.old.com where the user also have their login id like <<Domian>>\<<USerName>> old\user etc.

Business wants to migrate the application to different domain i.e. On Premises or Online.

New Domain like NEW.com and application URL like https://sharepoint.new.com

Users, who are part of the NEW domain can easily recognize by control and start using the application but some users are still part of the old domain.

As our new migrated application hosted into new domain so old domain user doesn’t recognize into new domain application.

 Below are the ways to resolve the issue:-

Option 1:-

If both domains have  TWO WAY TRUST. No configuration required. the user can be added as <<OLDDomain>>\<UserID>; instead of only user name.

 Option 2:-

If both domains have ONE WAY TRUST. Only people picker control configuration need to do using PowerShell. It will help control and application to recognize the user.

Option 3:-

 If both domains don't have TRUST process. User Profile Synchronization needs to perform. It will help control and application to recognize the user.

Ref :- https://collab365.community/sharepoint-2013-people-picker-problem-with-2-way-trusted-domains/