01 — Overview
What this engagement is
This service uses an automated migration tool to move Windows devices and user profiles from existing domain-joined or workgroup environments to Entra ID, formerly Azure AD. The tool supports enterprise-scale deployment for large numbers of workstations, including physical and remote devices via VPNs. IT Partner configures and customizes the migration process based on the client environment, migrates selected devices and user profiles, joins devices to Entra ID, and provides support during the migration. User information such as documents, desktop preferences, browser favorites, recent file lists, settings, and configurations is preserved during the migration process.
02 — Outcomes
Success criteria
01Seamless migration of domain-joined or workgroup devices to Entra ID with minimal user disruption.
02Full retention of user profiles, data, and settings on migrated devices.
03Devices securely enrolled in Entra ID with all required policies applied.
04Significant reduction in downtime and migration errors due to automation and standardized processes.
05Ongoing support and troubleshooting to ensure a smooth migration experience for all users.
03 — Deliverables
What you receive
✓Initial discovery session covering the client’s existing environment and migration requirements.
✓Migration strategy tailored to the client’s infrastructure, including device selection, scheduling, and profile handling.
✓Configured migration tool based on the client’s infrastructure.
✓Customized migration scripts and settings as required for large-scale or remote device migrations.
✓Automated migration of selected user profiles and devices to Entra ID.
✓Transfer of user profiles, including documents, settings, desktop configurations, and other personalized data.
✓Devices joined to Entra ID with security and compliance policies maintained.
✓Support for issues, troubleshooting, and user questions related to migrated profiles and devices.
✓Review of licensing requirements and compliance prior to migration.
04 — Plan
How the work unfolds
Environment assessment and discovery
Conduct an environment assessment and discovery session.
Migration roadmap
Develop a migration roadmap that aligns with the client’s needs and schedules.
Migration tool setup
Set up the migration tool and customize the migration settings based on the device and profile requirements.
Test migration
Test migrating devices and user profiles.
Selected device migration
Begin migration of selected devices, including user profile data and domain settings.
Entra ID validation
Validate that devices are successfully joined to Entra ID.
User access validation
Ensure users retain access to their settings, data, and applications.
Technical support
Provide ongoing technical support for users and administrators.
Residual issue resolution
Address any residual issues with migrated devices or profiles.
05 — Before we start
Prerequisites
→No additional Microsoft licenses are required for the migration process itself.
→Entra ID (Azure Active Directory) licensing may be required depending on the client’s existing environment and Microsoft setup.
→The client must provide access to the current environment, including user profiles, domain information, and device inventory.
→The client must ensure readiness of the Entra ID environment for device migration, including required configurations and access.
→The client must collaborate with IT Partner to define the scope of the migration, including user devices, scheduling, and expectations.
06 — Working together
Who does what
IT Partner
- Conduct an initial discovery session to understand the client’s existing environment and migration requirements.
- Develop a migration strategy tailored to the client’s infrastructure, including device selection, scheduling, and profile handling.
- Configure the migration tool based on the client’s infrastructure.
- Customize migration scripts and settings as required for large-scale or remote device migrations.
- Perform the automated migration of user profiles and devices to Entra ID.
- Ensure the seamless transfer of user profiles, including documents, settings, desktop configurations, and other personalized data.
- Join devices to Entra ID, ensuring security and compliance policies are maintained.
- Provide support to address any issues or troubleshooting that may arise.
- Assist users with any questions or concerns related to their migrated profiles and devices.
Your team
- Provide access to the current environment, including user profiles, domain information, and device inventory.
- Ensure readiness of the Entra ID environment for device migration, including required configurations and access.
- Collaborate with IT Partner to define the scope of the migration, including user devices, scheduling, and expectations.
- Review the migration results and provide feedback for any required adjustments.
07 — Scope
What's not included
✕Procurement or cost of Microsoft licenses, hardware, replacement devices, accessories, or network equipment.
✕Full Microsoft Entra ID tenant design, identity architecture redesign, Conditional Access redesign, or security baseline implementation beyond the configuration needed to support the agreed device migration.
✕Microsoft Intune, Windows Autopilot, endpoint management, compliance policy, or application deployment implementation unless separately scoped.
✕Operating system upgrades, Windows reimaging, device rebuilds, firmware updates, driver remediation, hardware repair, or replacement of unsupported devices.
✕Application packaging, application compatibility remediation, application modernization, or troubleshooting of pre-existing application issues unrelated to the migration process.
✕Server migrations, Active Directory domain controller migration, Active Directory cleanup, Group Policy redesign or conversion, or decommissioning of legacy domain infrastructure.
✕Migration of non-Windows endpoints, mobile devices, macOS devices, Linux devices, printers, shared kiosks, or other device types not included in the agreed Windows workstation scope.
✕Backup, restoration, or recovery of data outside the agreed user profile migration scope, including remediation of previously corrupted, missing, or inaccessible user data.
✕Network, VPN, firewall, proxy, bandwidth, DNS, or connectivity remediation required to make devices reachable for migration.
✕End-user training, formal change management, communications campaigns, floor-walking, or after-hours/on-site support unless explicitly included in the agreed scope.
✕Ongoing managed services, long-term help desk support, or post-engagement endpoint operations after the migration support period is complete.
08 — Fine print
Limitations & technical notes
!Entra ID (Azure Active Directory) licensing may be required depending on the client’s existing environment and Microsoft setup.
09 — Questions
Frequently asked questions
What is Device migration automation for Windows?
Device migration automation for Windows is a service that migrates Windows workstations from traditional domain-joined or workgroup environments to Microsoft Entra ID, formerly Azure AD. It uses an automated migration tool to reduce manual effort, downtime, and migration errors while preserving user profiles, personal data, settings, and configurations.
Which types of Windows devices can be migrated with this service?
This service is intended for Windows workstations in domain-joined or workgroup environments that need to be moved to Entra ID. It supports enterprise-scale migrations across large numbers of physical workstations and remote devices connected through VPNs, provided the client environment and access requirements are ready.
Does the service preserve user profiles and personal data?
Yes, the service is designed to preserve user profiles during the migration. Profile data can include documents, desktop preferences, browser favorites, recent file lists, settings, configurations, and other personalized data included in the selected user profile migration scope.
Does this service join devices to Microsoft Entra ID?
Yes, IT Partner migrates selected devices and joins them to Entra ID as part of the engagement. The service also includes validation that devices are successfully joined and that required security and compliance policies are maintained where they are part of the client’s configured environment.
What is included in the Device migration automation for Windows service?
The service includes an initial discovery session, a tailored migration strategy, migration tool configuration, customized migration scripts and settings when required, test migration, automated migration of selected devices and user profiles, Entra ID join validation, user access validation, and migration support. It also includes review of licensing requirements and compliance before migration.
What is not included in this service?
Exclusions include Microsoft licensing and hardware costs, full Entra ID tenant or identity architecture design, Microsoft Intune and Windows Autopilot implementation, operating system upgrades and device rebuilds, application packaging or compatibility remediation, server and Active Directory domain-controller migration, non-Windows endpoints, network or VPN remediation, end-user training, and ongoing managed services after the migration support period — unless separately scoped.
How long does the service take?
The stated service duration is 2 weeks. The exact migration schedule within that period depends on the number of selected devices, remote connectivity conditions, profile complexity, testing results, and the migration roadmap agreed with the client.
How is the service priced?
The service is priced at $6 per seat plus a $4,500 tenant fee, quoted in writing before work begins — you pay after you approve delivery. The tenant fee covers discovery, migration strategy, tool configuration, and testing; the per-seat fee covers each migrated device. Confirm the final seat count and scope with IT Partner before kickoff.
Are additional Microsoft licenses required for the migration?
No additional Microsoft licenses are required for the migration process itself. However, Entra ID licensing may be required depending on the client’s current Microsoft environment, desired configuration, and existing licensing position.
What prerequisites must be completed before migration starts?
The client must provide access to the current environment, including user profiles, domain information, and device inventory. The client must also ensure the Entra ID environment is ready for device migration, including required configurations and access, and must collaborate with IT Partner to define the migration scope, schedule, and expectations.
Will users experience downtime during the migration?
The service is designed to minimize user disruption by using automation and standardized migration processes. Some user impact may still occur during device migration, profile transition, validation, or troubleshooting, so timing and communication should be planned with IT Partner during the migration roadmap phase.
Can remote users be migrated if they are not in the office?
Yes, the service supports remote Windows devices connected through VPNs. Successful remote migration depends on connectivity, device accessibility, VPN availability, and the client providing the required access and inventory information.