
On-premise MDMs have specific advantages to them, but are they better than cloud –based MDM solution? Read on to find out.
How to move devices from one MDM to another: planning, Apple devices on iOS and macOS 26, Android and Windows steps, and which devices need a reset.


Content writer, trio.so
MDM migration is the process of moving your organization's devices, policies and apps from one mobile device management (MDM) service to another, or from an older setup of the same product to a newer one, such as on-premises to cloud. In practice it means rebuilding your settings in the new MDM, then unenrolling each device from the old one and enrolling it in the new one. The catch is the device: some can move without being erased, others need a factory reset. Since iOS 26, iPadOS 26 and macOS 26, Apple Business and Apple School Manager can move company Apple devices to a new MDM and keep their data.
If you are planning to switch MDM vendors and want the steps and the devices that will cause trouble, this guide covers the types of migration, the phases, platform-by-platform steps and the tools that help.
MDM migration refers to the process of transferring an organization's device management from one platform or version to another. It covers the device enrollments themselves, the configuration profiles and policies, the apps and their licences, and the reports and integrations around them. Common reasons are:
Settings rarely transfer automatically between vendors. Expect to rebuild them, and use the move to drop the ones nobody can explain.
Every MDM migration runs in three phases:
Inventory every device with its platform, owner, ownership type (company or personal) and how it was enrolled. Rebuild your policies, apps and integrations in the new MDM, and test them on a few devices before anyone else moves.
Move devices in groups, starting with the easiest. For each group, unenroll from the old MDM and enroll in the new one, then check that every policy and app arrived.
Confirm that every device reports to the new console, retire the old service, cancel its licences and revoke its tokens and certificates.
Moving from a server you run to a cloud service removes the server upkeep and reaches devices outside the office without a VPN. The devices still need to be re-enrolled in the cloud service, so plan it like any other vendor change. See cloud MDM for how the two models compare.
Upgrading to a new version of the same MDM usually keeps enrollments in place, but check the vendor's notes: some major versions change how profiles or agents work and need a planned rollout.
Changing vendor is the most common and the most work. Every device moves, every policy is rebuilt, and app licences move to the new service.
Company devices that need a reset lose local data, so make sure work files sit in cloud storage or a backup first. Keep devices encrypted throughout, and do not leave devices unmanaged between the old and new MDM longer than necessary.
Check that the new MDM supports every platform, OS version and enrollment method you use today: Apple Automated Device Enrollment, Windows Autopilot, Android Enterprise zero-touch and QR enrollment, and personal-device enrollment.
A device being reset or re-enrolled is out of use for a while. Schedule moves outside working hours, keep a spare device for critical roles, and move kiosks and shared devices when the site is closed.
A newer MDM can bring features the old one lacked, such as OS update enforcement with deadlines, vulnerability findings or better reporting for audits.
One console for every platform replaces the second tool many teams run for Windows or Android, and automatic enrollment removes hands-on setup.
Moving off an on-premises server ends hardware, hosting and maintenance costs, and consolidating tools can cut licence spend. Price the whole fleet for three years before you decide.
Settings do not map one to one between vendors, and some devices cannot move without a reset. Android devices set up as fully managed or dedicated are the usual example.
Staff dislike surprise resets and new prompts. Tell people what will happen, when, and what they need to do.
Migrations take IT time for rebuilding, testing and support calls. Small teams should run the old and new MDM side by side for a few weeks rather than moving everything in one weekend.
Lost or forgotten devices that never re-enroll are a risk. Track every device through the move, and wipe or lock any that do not arrive in the new console.
List devices by platform and enrollment method, decide which can move without a reset, and set a date for each group.
Pilot the new MDM on a few devices per platform, including IT's own, and check every policy, app and integration before wider waves.
Plan for the things that go wrong:
Keep a backup of work data, a contingency plan for critical devices, and the old MDM available until the last group has moved.
Agree the timing with team leads, send users a short note before their device moves, and give them one contact for problems.
The process follows the same three phases, with platform-specific steps in the middle.
Each platform moves differently:
| Platform | Company devices | Personal devices |
|---|---|---|
| iPhone, iPad, Mac | On iOS, iPadOS or macOS 26 or later, enrolled through Automated Device Enrollment: reassign them to the new MDM in Apple Business or Apple School Manager with a deadline, and they move and keep their data. Older devices: erase and re-enroll. | The user removes the old enrollment and enrolls again with a work account. |
| Android | Fully managed and dedicated devices usually need a factory reset, then enroll by zero-touch, QR code or enrollment token. | The user removes the old work profile and creates a new one. |
| Windows | Unenroll from the old MDM and enroll in the new one; for Autopilot devices, move the device registration and profile to the new service. | The user removes the old work account and adds it again. |
Apple's device migration has limits: devices set up as Shared iPad or with Return to Service app preservation are not migrated, and devices added with Apple Configurator must be past their 30-day provisional period. Apps and their data can be kept if the new MDM delivers them before setup finishes. See Apple's deployment guide and our guides to Apple DEP and Android Enterprise enrollment.
There is no universal tool that moves everything from one vendor to another. These are the tools that do exist:
Apple Business and Apple School Manager can move company Apple devices on version 26 or later to a new MDM service, with a deadline you set and their data kept. For other platforms, some vendors offer scripts or services to help move their own customers; check what the new vendor offers before you assume anything moves automatically.
Your old MDM's inventory and policy exports are the main assessment tool. Use them to list devices by enrollment method and settings by purpose.
Some vendors and partners offer guided migration as a paid service, which can help larger fleets.
For devices that need a reset, the data question is about user files, not the MDM. Move work files to cloud storage before the reset so nothing is lost.
Comparing vendors before a move? See Hexnode alternatives and Jamf alternatives.
trio.so enrolls Apple devices through Apple Business, including company devices moved from another MDM on iOS, iPadOS and macOS 26, Windows PCs through Windows Autopilot and Android devices through Android zero-touch, QR code or enrollment token. It has no migration or import tool; trio.so's team can scope a move with you; see how to switch MDM to trio.so. Plans start at $5 per device.

An MDM migration is mostly re-enrollment: rebuild your settings, move devices in planned waves, and check each one arrives. With Apple's device migration on version 26, a pilot, clear communication and the old MDM kept until the last device moves, a mid-size fleet can switch in a few weeks without losing data.
Moving devices, policies and apps from one MDM service to another, or from an older setup to a newer one. Each device is unenrolled from the old MDM and enrolled in the new one.
Inventory your devices, rebuild your policies and apps in the new MDM, connect Apple, Google and Microsoft accounts, pilot with a few devices, then move devices in waves and retire the old service.
Company Apple devices on iOS, iPadOS or macOS 26 or later enrolled through Automated Device Enrollment can move through Apple Business or Apple School Manager and keep their data. Fully managed Android devices and older Apple devices usually need a reset.
A small fleet can move in a few weeks. Larger fleets plan for two to three months, with a pilot first and waves after that.
Apple Business and Apple School Manager can move Apple devices on version 26 or later. Otherwise, use your old MDM's exports, the new vendor's onboarding help and a clear plan per platform.
Related reading: cloud MDM, Apple DEP, Apple Business and Android Enterprise enrollment.
trio.so enrolls Apple, Windows and Android devices through their zero-touch programmes. Plans start at $5 per device.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.





Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.
Related
The related industry news, interviews, technologies, and resources.

On-premise MDMs have specific advantages to them, but are they better than cloud –based MDM solution? Read on to find out.

What cloud MDM is, how cloud-based device management works, cloud vs on-premises MDM compared, and what to check before you move your devices.

What mobile device management (MDM) is, how it works on Apple, Android and Windows, what it can see on company and personal phones, and how to choose MDM.

Seven IBM MaaS360 alternatives compared on platforms and published pricing, with MaaS360's own plans and what to check before you switch.

Seven Miradore alternatives compared on platforms and published pricing, with Miradore's own plans and its 50-device free limit.

Seven 42Gears SureMDM alternatives compared on platforms and published pricing, with SureMDM's own plans and when it still fits.

The best Microsoft Intune alternatives for IT teams: an honest comparison of features, platforms and published pricing, and when to stay on Intune.

Learn how to calculate ROI of MDM with proven cost savings formulas. Organizations achieve 200-400% return through reduced IT costs and enhanced productivity.
14-day free trial. No credit card required.
trio.so for MSPs: one console, separate clients