Welcome to Opsole Docs

Your comprehensive guide to modern device migration and Microsoft Entra ID integration, including AD/Hybrid to Entra ID and Tenant-to-Tenant device migration.

What is Opsole Migrate?

Opsole Migrate is an enterprise device migration platform that automates the transition of Windows devices from Active Directory (AD) Joined or Hybrid Entra ID Joined into a clean Microsoft Entra ID Joined state — without reimaging. It preserves the user profile, data, and applications to minimize disruption and accelerate device modernization.

Key Capabilities

  • AD Joined → Entra ID Joined (in-place, no wipe)
  • Hybrid Entra ID Joined → Entra ID Joined (cloud-only conversion)
  • Microsoft Entra ID Tenant-to-Tenant Device Migration (M&A / consolidation)
  • User profile preservation (data, apps, settings)
  • Works with Intune readiness and enterprise rollout models

Enterprise Benefits

  • No device reimaging or wiping required
  • Controlled reboot workflow with phase-based execution
  • Designed for global rollout consistency and scale
  • Preserves user experience while modernizing device identity
  • Supports IT-scheduled or user-initiated execution models

Tenant-to-tenant device migration is commonly used for mergers and acquisitions, tenant consolidation, and organizational separation projects.

Onboarding Guide

Follow our step-by-step onboarding guide to get started with Opsole Migrate

Migration Journey

Follow our step-by-step guides to successfully migrate your devices

Tenant-to-Tenant Migration Limitation

When the migration method is configured as Tenant-to-Tenant device migration, OpsoleMigrate supports migration of the primary signed-in user profile only. Multi-profile migration on a single device is not supported in tenant-to-tenant scenarios.

Migration Process

Opsole Migrate executes a deterministic, phase-based migration workflow across reboots

Phase 1: Initiation

Initiates migration, performs pre-checks, prepares device identity changes, and begins the controlled transition workflow.

Phase 2: System Migration

Executes system-level actions across reboot boundaries to complete migration steps before the user session resumes.

Phase 3: Finalization

Finalizes post-login configuration, validation, cleanup, and device readiness for enterprise management.

Ready to start your migration?
Begin with onboarding and prerequisites to ensure your environment is ready
Start Onboarding →