Jamf: plan the MDM migration to Blueprints
Jamf has published a guide dedicated to migration towards declarative management. Its core recommendation is pragmatic: immediately migrate workflows made obsolete by Apple OS 27, but replace other profiles only when a Blueprint delivers an identifiable capability or benefit.
1. What the new guide establishes
Jamf divides migrations into two categories. Migrating legacy software-update mechanisms is mandatory: Apple removed the relevant deferral keys and MDM commands in macOS, iOS, iPadOS, and tvOS 27. Blueprints and their declarations replace these workflows, which no longer function.
Migrating restrictions and legacy profiles is discretionary. Jamf recommends adopting a Blueprint to achieve a specific goal, not merely because declarative management is Apple's long-term direction.
2. Turn the guide into a dependency inventory
An IT department should first map every setting to its delivery method, target devices, and business purpose. For updates, this means identifying commands, smart groups, scripts, and reports that still rely on a removed mechanism. For restrictions, teams should compare functional coverage, version requirements, and conflict behaviour before any replacement.
Moving to a Blueprint does not by itself prove compliance. Controls must confirm that the declaration arrived, was applied, and that exceptions can be explained device by device.
3. What does this change for a Belgian or French organisation?
For an SMB, the priority is to ask its MDM provider which OS 27 workflows still rely on removed commands and how outcomes are verified. A mid-market or large organisation operating across Belgium, France, and Europe should build a matrix by platform, version, population, and business owner, then migrate in rings.
Public-sector and regulated organisations have an additional requirement: retain evidence of the change, pilot, and final status. Support teams also need a clear procedure for distinguishing a declaration conflict, an offline device, and a version incompatibility.
4. Underside analysis: migrate by risk, not by slogan
Declarative management reduces dependence on a sequence of server commands, but shifts effort towards declaration quality, conditions, and observability. A sound path combines Apple Business Manager and Automated Device Enrollment to bring the device under management, Jamf to define the expected state, and compliance controls that can explain deviations.
This approach complements our analysis of OS 27 updates with Jamf and our guide to conditions in Blueprints. The goal is not a mass switch, but a traceable migration without competing profiles or an unmanaged interval.
5. Recommended migration plan
- Inventory software-update workflows, restrictions, and profiles with their current MDM delivery method.
- Give absolute priority to mechanisms removed by OS 27.
- Compare every remaining profile with its target Blueprint and document the intended benefit.
- Detect duplicates and conflicts before enabling the declaration for a pilot group.
- Measure delivery, application, and failure reason per device and OS version.
- Remove the legacy workflow only after validation, then archive evidence and the support procedure.
Objective: replace what no longer works first, then modernise everything else only when declarative management materially improves fleet control.
Plan your Jamf migration to DDMOfficial source: Jamf — Declarative Device Management Migration Guide, accessed October 15, 2026.