Switch MDM provider
Migrate to Headwind MDM from Your Current Android MDM
Move your Android fleet in planned batches. Test on 2 devices first and keep the old platform running until the last device is switched.
Read the detailed migration guide →YOUR MIGRATION AT A GLANCE
First test2 devices
Migration steps5
Old MDMLive until cutover
Why Teams Migrate to Headwind MDM
Companies switch when they need to run the MDM server themselves, read the source code, or own the license outright.
Open source code
The Community Edition is released under the Apache License. Enterprise customers receive the mobile app source code. Open source details
On-premise and air-gapped
Install the server on your own hardware or private cloud. Device data stays inside your network. Closed networks
No Firebase dependency
Push messages run through the Headwind MDM server itself. Devices stay manageable with no Google services in the path.
Predictable licensing
Commercial editions come with perpetual licenses. Budget once and plan the rollout around it. See pricing
How Much Do You Pay for MDM?
Per-device subscriptions are billed again at every renewal. Headwind MDM Premium is a one-time license for up to 300 devices.
One-time payment, perpetual license Up to 300 managed devices 1 year of support included, renewal optionalYou pay every year$3,600
Headwind MDM Premium, one time$2,990
Pays for itself in10 months
Two Ways to Move Android Devices to Headwind MDM
Android allows one device owner per device, and the MDM agent holds that role. Your migration path depends on whether ownership can be handed over.
DEVICE OWNERSHIP TRANSFER
No wipe
Headwind MDM 6.39 and later can take over device ownership from another MDM. Devices keep their data and stay in the field. Your current provider must support the transfer as well.
RE-PROVISIONING
Any MDM
Factory-reset each device to remove the old management setup, then enroll it in Headwind MDM with a QR code. This path works with every Android MDM.
Not sure whether your platform supports ownership transfer? Tell us which MDM you run and we will check it against your setup.
How to Migrate to Headwind MDM in 5 Steps
The same staged plan works for 50 devices or 5,000. Each step ends with a check before you move on.
1
Deploy the Headwind MDM server
Pick where the server runs. Headwind Cloud is the fastest way to start, and you can move to an on-premise installation later. For self-hosting, check the hardware requirements and follow the installation guide.
- Document the current setup first: apps, policies, restrictions, launcher or kiosk screen. Screenshots help.
- Confirm you can open the admin panel before you touch any device.
2
Enroll test devices and rebuild your configuration
Take two devices from the current fleet. Enroll one in Headwind MDM with a QR code and leave the other on the old MDM. Place them side by side and compare.
- Recreate device groups, kiosk profiles and application policies in Headwind MDM.
- Users should find the same apps and finish their usual tasks. The home screen does not need to match pixel for pixel.
- Kiosk mode requires a commercial edition. Add licensing to the plan if your fleet runs kiosk screens. Compare editions
3
Beta test with IT and pilot users
Use the test device the way an employee would. Then hand devices to a few volunteers for their normal workday. They will spot problems an IT check misses, such as a restriction that only gets in the way after a few hours.
- Restart the device and reconnect it to the network.
- Open the main apps and confirm updates and restrictions apply.
- Fix every configuration issue before the next batch.
4
Migrate the rest of the fleet in batches
Size each batch by how many devices your team can reset and enroll in a day. Start with one site or one team, then expand. The rest of the fleet keeps working on the old MDM in the meantime.
- A factory reset erases local data. Back up anything users store on the device.
- Plan for field devices that are hard to collect. Ownership transfer helps most here.
- Make sure enrollment has network access to the Headwind MDM server at every site.
5
Decommission the old MDM
Keep the old platform until the last batch runs without issues. Time the cutover against the renewal date of your current contract so you do not pay for an extra term.
- Export the reports and inventory you want to keep before access ends.
- Remove migrated devices from the old console.
What You Recreate in Headwind MDM During Migration
MDM platforms do not exchange configuration files. You rebuild each setting in Headwind MDM, with your documented setup as the reference.
Device groups
Organize devices by site, team or device type.
Application policies
Which apps are installed, allowed or hidden on each configuration.
App deployment
Upload your APK files once and push them to devices silently.
Restrictions
Device settings, permissions and lockdown rules your users rely on.
Home screen layout
App icons and their order on the device desktop, so users find what they had before.
Files and content
Documents, media and config files your apps expect to find on the device.
Wi-Fi and network settings
Network credentials devices need to reach the server at every site.
MDM Migration FAQ
How long does a migration to Headwind MDM take?
It depends on fleet size and how many devices your team can re-enroll per day. Server setup and the two-device test usually come first, followed by a pilot. The batch phase takes the most time.
Will users lose working time during the migration?
Each device is out of use while it is reset and enrolled. The rest of the fleet keeps working on the old MDM, so batches limit the impact to a small group at a time.
Do I have to factory-reset every device?
Usually yes, because Android allows only one device owner. Headwind MDM 6.39 and later support device ownership transfer, which avoids the reset when your current MDM supports it too.
Does the Headwind MDM team help during migration?
Yes. Contact us with your current platform and fleet size, and we will help you plan the path. Most setup questions are already answered on the Headwind MDM Q&A forum.
How does my IT team learn Headwind MDM?
Admins learn the console during the two-device test and the pilot. The quick start guide covers enrollment in about 15 minutes.
What should I do with my current MDM license?
Keep it active until the last batch is migrated and verified. Plan the cutover before the renewal date to avoid paying for another term.
Can I test Headwind MDM before buying server hardware?
Yes. Start in Headwind Cloud and move to an on-premise installation later.
Can I migrate devices that run in an air-gapped network?
Yes. Headwind MDM does not rely on Firebase, so the server and devices can run inside a closed network. Provisioning on a closed network
Plan Your Move to Headwind MDM
Start a cloud trial today, or talk to us about a self-hosted migration.
Your current MDM Fleet size and device models Cloud or self-hostedFree and Premium license plans are available. Compare features