Assess
Establish the environment, dependencies and scope of the issue before changing anything.

For replacing legacy Windows Server domain controllers, moving FSMO roles, validating DNS / SYSVOL and retiring old DCs. The goal is not simply to complete the migration, but to keep authentication, name resolution and policy behavior verifiable afterwards.
Confirm directory health, role dependencies, DNS / SYSVOL state and the maintenance window before sequencing the new and legacy domain controllers.
The same delivery discipline applies to migrations, remediation, operational handovers and other critical infrastructure changes.
Review functional level, FSMO, replication, DNS, SYSVOL, GC, time hierarchy, GPO and dependencies.
Define the target roles, address/DNS plan, old-server retention and business validation method.
Deploy the new DC and validate replication, DNS and SYSVOL before client dependency changes.
Move critical roles and validate logon, GPO, DNS, shares and application dependencies.
Retire the old DC only after residual dependencies are cleared; provide records and a new baseline.
Before implementation we define ownership, maintenance windows, verification and rollback. After the change we retain key records and handover documentation.
Establish the environment, dependencies and scope of the issue before changing anything.
Define scope, impact, maintenance window, verification and rollback.
Execute within the approved scope and keep evidence at key checkpoints.
Validate system behavior, access, business paths and recovery capability.
Provide configuration baseline, implementation record, residual risks and next actions.
For project decision-makers
Verify replication, DNS, SYSVOL/NETLOGON, time sync and dependent services first. If replication is already unhealthy, identify the trusted baseline before any migration action.
Scope and impact depend on the live environment; no unverified zero-downtime promise.
Versions, roles, dependencies and known issues.
Affected services, acceptable downtime and validation criteria.
Maintenance window, backup state and rollback conditions.