Migrating a Mac fleet from Jamf to Apple Business DMS means releasing every device from Jamf, reassigning it to Apple Business, and letting each Mac re-enrol on its next wipe or setup. Apple Business’s built-in DMS (Device Management Service, formerly MDM) has been available to every UK business since April 2026 at no cost, which is why this migration path now applies to any Jamf customer reassessing their device management stack, not just new starters.
How do you switch device management from Jamf to Apple’s native business service?
Switching means moving devices out of Jamf’s management and into Apple Business DMS as the controlling platform, while keeping devices enrolled in Apple Business itself throughout. Apple Business and Jamf both sit on the same enrolment infrastructure, so the underlying device record does not move. Only the MDM server assignment changes.
This is available to UK organisations today. There is no waitlist or regional restriction on Apple Business DMS for UK Apple Business accounts.
What’s actually different between Jamf and Apple Business DMS?
Jamf and Apple Business DMS sit at different depths of the same stack, and the trade offs between them are covered in full in Apple Business DMS vs Jamf vs Addigy: Which Is Right for Your UK Mac Fleet? and Do You Still Need a Third-Party DMS Now That Apple Business Is Free?
Step-by-step: migrating Macs from Jamf to Apple Business DMS
- Audit your existing Jamf configuration before touching a single device
- Release devices from Jamf’s management
- Reassign devices to Apple Business DMS in Apple Business
- Re-enrol devices on next setup or wipe
- Rebuild critical policies, profiles and scripts inside Apple Business DMS
- Validate compliance reporting before decommissioning Jamf
How do you release devices from your organisation before migrating?
Releasing a device removes it from Jamf’s active management without removing it from Apple Business itself. In most current Apple Business setups this is done from within Jamf, using the option to release management, or directly in Apple Business against the device record. The device remains enrolled in Apple Business throughout. This step should happen in planned batches, not as a single bulk release across the whole fleet, since every released device becomes unmanaged the moment Jamf lets go of it.
How do you re-enrol devices into Apple Business afterwards?
Once a device is reassigned to Apple Business DMS, re-enrolment typically happens automatically the next time the device is erased and set up, or restarted through Apple Business’s remote wipe and reassign flow. Devices do not need to be physically collected for this in most cases. This is the point at which a Blueprint (Apple Business DMS’s equivalent of a Jamf policy set) needs to already exist, or the device will land in an unconfigured state.
Disconnecting your domain and bulk uploading devices via CSV
For fleets with device records spread across multiple orders or resellers, bulk reassignment is typically handled by uploading a list of serial numbers, either as a CSV file or pasted directly into the device assignment screen. Exact mechanics vary by fleet size and how devices were originally registered to Apple Business, so this is the step worth confirming against your own Apple Business account before running it at scale, rather than assuming last year’s process still applies exactly as documented.
What happens to your existing Jamf configuration when you migrate?
This is where most of the actual migration effort sits, and it is rarely a clean like for like swap.
None of this transfers automatically. Every Smart Group, script and extension attribute needs to be reviewed and either manually rebuilt within Apple Business DMS’s Blueprint model or accepted as lost functionality.
What does migration cost, and who can help?
The Apple Business DMS layer itself is free, so the direct cost of migration sits in the time required to audit, rebuild and validate configuration rather than in licensing. For fleets under around 25 devices with straightforward configuration, this is realistically a few days of focused work. Larger or more heavily scripted Jamf deployments take longer, particularly where compliance reporting for Cyber Essentials or ISO 27001 depends on Jamf’s audit trail.
If your Jamf configuration includes scripting, compliance reporting or anything Cyber Essentials depends on, talk to us about a managed migration rather than doing this in house.
Related articles
- Apple Business DMS vs Jamf vs Addigy: Which Is Right for Your UK Mac Fleet?
- Do You Still Need a Third-Party DMS Now That Apple Business Is Free?
- Apple Business Now Includes Free MDM: What It Does, What It Doesn’t, and When Your Business Needs Jamf
FAQs
Does migrating from Jamf to Apple Business DMS remove devices from Apple Business?
No. Devices stay enrolled in Apple Business throughout the migration. Only the assigned MDM server changes, from Jamf to Apple Business DMS. The enrolment record, Managed Apple Accounts and app licensing remain intact, provided the device is reassigned rather than fully removed from Apple Business.
Will my Jamf Smart Groups and scripts carry over to Apple Business DMS?
No. Apple Business DMS has no equivalent for Jamf’s Smart Groups, extension attributes or scripting. Groups need rebuilding through Blueprint assignment, and any script-driven automation needs a manual process or third-party replacement, since Apple Business DMS does not support scripting.
How long does a Jamf to Apple Business DMS migration take?
For a fleet under 25 devices with straightforward configuration, migration typically takes a few days of focused work. Larger fleets, or those with heavy scripting and Cyber Essentials compliance reporting built on Jamf, take considerably longer to audit, rebuild and validate.
