Readiness Checklist

Use this checklist immediately before running Opsole Migrate on target devices.

This checklist is not a replacement for the full Validation Checklist. The Validation Checklist confirms enterprise prerequisites. This page confirms that the device, user, and migration window are ready for execution.

---

Go / No-Go Rule

Do not start migration on a device unless every required item below is confirmed.

If the device is not ready, pause migration for that device and remediate the issue before continuing.

---

1. Portal and Configuration Readiness

• Portal onboarding is complete.
• Portal configuration is complete and saved.
• Correct migration scenario is configured.
• Required tenant credentials were verified successfully in the portal.
• Validated provisioning package is uploaded.
• Provisioning package has not expired.
• AD disjoin account is configured if required by the scenario.
• Multi-user profile migration setting is correct for the migration wave.
• Recovery settings, group assignment, and device attributes match the approved plan.

---

2. Device Readiness

• Device is in scope for the current migration wave.
• Device is in a supported starting state for the configured scenario.
• Device is powered on and connected to AC power where possible.
• Device has stable network connectivity.
• Device is not on a captive portal, guest network, or restricted network segment.
• Device can reach required Microsoft and Opsole endpoints.
• Device has enough free disk space for migration operations and logs.
• Device does not have a known temporary, corrupted, roaming, mandatory, or container-based profile in scope.

---

3. User Readiness

• User has been notified of the migration window.
• User has saved work and closed business applications.
• User understands that automated reboots will occur.
• User understands they must not sign in while the migration-in-progress banner is displayed.
• User has their Microsoft Entra ID credentials available for post-migration sign-in.
• Service desk contact or escalation path has been provided to the user.

---

4. Recovery Readiness

• Local administrator or LAPS recovery path is available.
• BitLocker recovery access is available where BitLocker is enabled.
• Support team understands the approved recovery process.
• Support team knows when to use Patch.exe recovery flows.
• Device-specific recovery ownership is clear for the migration window.

---

5. Security Tooling Readiness

• EDR, antivirus, WDAC, AppLocker, and application-control policies are applied to the device.
• Opsole Migrate executables are allowed.
• Opsole Migrate runtime and log paths are allowed.
• Scheduled task creation and SYSTEM-context execution are not blocked.
• No Opsole Migrate files are quarantined or removed after installation.
• EDR isolation actions are controlled for the migration window.

---

6. Deployment Readiness

• Opsole Migrate MSI is deployed or available on the target device.
• MSI installation completed successfully.
• The latest migration package can be downloaded by the application at runtime.
• If using silent or scheduled execution, the correct device assignment or deployment group is configured.
• If using user-initiated execution, the user knows how to launch Opsole Migrate.

---

7. Final Pre-run Confirmation

• Device is ready to start migration.
• User is ready to begin migration.
• Service desk is ready to support the migration window.
• Migration owner has approved start for this device or wave.

---

Next Steps

• Continue to Migration Process