Skip to main content
Question

Sign, when migration is complete - Jamf Pro

  • February 9, 2026
  • 3 replies
  • 58 views

Forum|alt.badge.img+7

Hi everyone,
I'm currently preparing to move about 500 devices from Jamf to another MDM. I've made sure all devices are updated to macOS and iOS/iPadOS 26 and have tested moving a few devices to confirm that it works without deleting them first.

The question is, is there any way to see if they have been moved in Jamf? And if so, trigger a cleanup somehow?

3 replies

h1431532403240
Forum|alt.badge.img+6

Yes — create a Smart Computer Group with these criteria:

  • Managed is No
  • Last Check-in more than x days ago (e.g., 7 days)

Devices that have enrolled in another MDM will have their Jamf MDM profile removed and stop checking in, so they'll appear in this group.

For cleanup, you can select those devices from an Advanced Search and use Action > Delete to remove them in bulk. Or script it via the API (DELETE /v3/computers-inventory/{id}).

Important: If these devices are in Apple Business Manager under your Jamf MDM server, reassign them to the new MDM server in ABM — otherwise they'll re-enroll to Jamf on next reset.

Reference: Mass Actions for Computers


Forum|alt.badge.img+7
  • Author
  • Contributor
  • February 10, 2026

Thanks for your information. The thing is that I’m doing the lastest thing with ABM if they’re updated to macoOS or iOS/iPadOS 26 directly within ABM.

https://intuneirl.com/mac-admins-your-migration-glow-up-just-dropped/

WRONG BELLOW - Was so for a while but now it’s gone
What I notised is that even tough they’re swished of for in this case Inlune the Jamf Self Service and Jamf commands still works. And at first the smart group above worked but today they’re still back to managed. Strange because now the scope in ABM is set to our Intune instance.


h1431532403240
Forum|alt.badge.img+6

There are two separate things happening here depending on your device platform:

iOS/iPadOS: There's no locally installed Jamf framework — management is entirely via the MDM profile. Once the ABM migration completes and the device restarts, Jamf loses all control. If these devices still show as managed, the migration hasn't actually completed on-device yet. Users must accept the enrollment prompt and restart — tapping "Not Now" delays it until the deadline.

macOS: The jamf binary and Self Service are installed as local packages, independent of the MDM profile. After ABM migration swaps the MDM profile to Intune, the jamf binary keeps running and checking in to Jamf Pro — which re-establishes "managed" status. You need to run sudo /usr/local/bin/jamf removeFramework via Intune post-migration.

Don't rely solely on Smart Groups for tracking migration status. Smart Groups depend on check-in data and can be misleading (as you've seen). Use the Jamf Pro API with RSQL filters for more accurate detection:

# Find devices that are unmanaged AND no longer MDM-capable
curl -X GET "https://yourserver.jamfcloud.com/api/v3/computers-inventory?section=GENERAL&filter=general.remoteManagement.managed==false%20AND%20general.mdmCapable.capable==false" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Accept: application/json"

Once confirmed, clean up with:

# Delete migrated device records
curl -X DELETE "https://yourserver.jamfcloud.com/api/v3/computers-inventory/{id}" \
-H "Authorization: Bearer YOUR_TOKEN"

Reference: