Solution
Windows 365 migration stalls when every AVD, VDI, Azure VM, custom-image, user, schedule, and cleanup action is handled manually. EtherInsights gives teams guided readiness checks, scheduling, status tracking, and post-migration evidence in one place.
AVD + VDI
migration planning for Azure Virtual Desktop, older VDI, and eligible Azure VM paths
API-led
built around Microsoft's Windows 365 migration API and Graph-based status visibility
Tracked
schedule, import, migration history, statistics, and cleanup in the same motion
The problem
VDI exits stall when source cloud desktops, users, snapshots, scheduling, and post-migration cleanup are managed as separate manual tasks. Azure Virtual Desktop, AVD personal desktops, standalone Azure VMs, and custom image paths each need validation before they can land safely in Windows 365.
Some desktops are in Azure Virtual Desktop AVD. Some are standalone Azure VMs. Others come from older virtual desktop infrastructure VDI or custom image paths that need to be prepared before they can follow a supported Windows 365 import route.
User mapping, snapshot preparation, licence assignment, maintenance windows, and cleanup decisions are easy to mis-sequence when every cloud desktop wave is coordinated outside the migration tool.
Teams need to know what was imported, what succeeded, what failed, how long each stage took, and which actions remain before the next migration wave.
Original VMs, network interfaces, disks, and third-party VDI agents can remain behind because nobody wants to remove production dependencies without evidence.
How it works
Start from existing Azure Virtual Desktop personal desktops, eligible Azure VMs, or a prepared custom VM path. Older VDI candidates can be assessed and prepared into a supported Azure VM or VHD snapshot route before import.
Match source desktops to target users, check readiness, apply naming rules where needed, and prepare the snapshot-based Windows 365 import without rebuilding every step by hand.
Plan migrations around maintenance windows, licence assignment, high performance user groups, and user impact so the team can move in controlled waves rather than one-off manual jobs.
Follow import status, migrated Cloud PC history, duration statistics, and post-migration cleanup so the next wave has evidence rather than guesswork.
Migration operating view
EtherInsights turns the migration into a managed workflow: select eligible AVD or Azure VM sources, map users, prepare snapshot-based imports, track progress, review migrated Cloud PCs, and keep migration statistics ready for the next wave.
Product walkthrough
The current walkthrough shows the wider Cloud PC operating view. The migration page is designed to take screenshots from the dedicated migration workflow when those assets are ready.
How we deliver it
Use EtherInsights when the question is how to move users from Azure Virtual Desktop, older VDI, standalone Azure VMs, or prepared custom VM paths into Windows 365 with less manual risk. If stakeholders call it Windows365, W365, CloudPC, cloud desktop migration, or AVD migration, this is the planning route. EtherApps Forge supports application readiness where apps block the wave. EtherAssist supports day-two runbooks and troubleshooting once Cloud PCs are live.
EtherInsights started as the cost management platform for Microsoft 365 and Azure. It shows where spend is going, which owners need to act, and how to turn waste into savings. It now extends that operating view into full Windows 365 lifecycle support, plus tenant, user, security, device, and Intune reporting.
EtherApps Forge captures installed Windows applications from running systems, analyses the real application footprint, supports AI-guided packaging decisions, and produces deployment-ready outputs for modern environments.
EtherAssist gives IT and compliance teams the speed of AI without giving up data control, auditability, or practical governance. It supports troubleshooting, scripting, documentation, policy work, and repeatable internal support workflows.
Where this fits
FAQ
Short answers for teams moving from AVD, VDI, PCs, or Azure virtual machines to Windows 365 Cloud PCs.
A Windows 365 migration moves users from Azure Virtual Desktop, legacy VDI, physical PCs, or Azure virtual machines onto Windows 365 Cloud PCs. The work covers assessment and cohort planning, licensing, Intune and Microsoft Entra readiness, moving user profiles and applications, a controlled pilot, then wave-by-wave cutover and decommissioning of the old estate. EtherInsights supports each stage with estate evidence, guided steps, scheduling, and tracking.
Yes. Personal AVD desktops map naturally to Windows 365 Enterprise Cloud PCs, and Microsoft provides a migration capability for moving eligible single-session desktops. Pooled, shift-based, or low-density AVD estates are usually compared against Windows 365 Flex instead. EtherInsights turns the AVD footprint into migration cohorts and tracks each wave from pilot to decommission.
Applications are redeployed to Cloud PCs through Intune rather than lifted from the old desktop, so packaging readiness is part of the assessment. Profile and data continuity depend on the scenario: environments using cloud profiles and OneDrive typically carry user data across smoothly, while legacy profile tooling needs a planned approach. The pilot wave is where profile behaviour is proven before scale.
Each user needs a Windows 365 licence for the chosen Cloud PC size, plus supporting licensing for Windows, Intune, and Microsoft Entra ID that most Microsoft 365 enterprise and business plans already include. Tenant prerequisites centre on Intune enrolment, identity configuration, and network readiness. The assessment stage confirms the exact mix per estate before any commitment.
The usual risks are unplanned application dependencies, profile tooling that does not translate to Cloud PCs, undersized or oversized Cloud PC assignments, network egress surprises, and cutover waves that outrun support capacity. A cohort-based plan with a genuine pilot, sizing evidence, and per-wave rollback options keeps each risk visible and owned.
Start here
Start with a Windows 365 migration assessment, use the quick TCO calculator for the first commercial signal, then validate the source estate, schedule, and cleanup path inside EtherInsights.
