Configure your new device management service
Before you can link to your new device management service, you need to first configure it. After you complete the configuration, follow the steps below.
Link your new device management service to Apple School Manager or Apple Business Manager
First, download an Apple Push Notification service (APNs) certificate and use it to configure your new device management service. Next, to link your new service to Apple School Manager or Apple Business Manager, upload your device management service’s certificate and then download a new Device Management Service token for your new service.
For more information, see Link to a third-party device management service in Apple School Manager or Link to a third-party device management service in Apple Business Manager.
Re-create your enrollment and configuration profiles
You need to re-create your enrollment and configuration profiles and associated payloads in your new device management service. Make sure you designate specific payloads for users, devices, or their associated groups. For more information, consult your developer’s device management service documentation.
Reassign devices to your new device management service
In Apple School Manager or Apple Business Manager, you can assign some test devices from your existing device management service to your new service. After testing is successful, you can reassign the rest of your devices. You can then set the default to the new device management service.
If you’re migrating Mac computers to a new device management service
If you’re migrating Mac computers to a new device management service, consider the following:
Setup Assistant: Create a specific Setup Assistant payload that manages the specific Setup Assistant panes and whether the user should interact with each pane.
Bootstrap token: If you’re using a bootstrap token, make sure to set up your new device management service to enable this workflow. See Bootstrap token.
Activation Lock bypass codes: If your devices are activation locked, back up all the Activation Lock bypass codes before you migrate so you can reactivate devices after a reset or wipe.
FileVault recovery keys: In case you have escrowed FileVault recovery keys from your Mac computers, back them up securely to help users reset their password.
macOS user type: Migration of Mac computers to another device management service may require a local administrator user name and password. If the macOS users are standard users and not administrators, additional assistance may be needed to help them migrate.
Packages: If necessary, migrate macOS packages and make them available to use in the new device management service. After the packages are available, you need to assign them to their appropriate policies and workflows. This includes bootstrap packages that may be a part of any prestage enrollment profiles.
If the new device management service supports scoping
If the new device management service supports scoping, you need to mirror all scoping groups and assignments for apps, profiles, and so forth, in the new device management service.
How to handle in-house proprietary apps
You don’t need to unassign apps that your organization creates. You can just download them again after enrolling the device in the new device management service.
Maintain your network connection
If your Wi-Fi network requires authentication and that authentication is tied to a configuration profile, users may be unable to rejoin your network to complete the migration. Make sure you re-create the appropriate network access certificates and payloads so devices can reconnect and enroll in the new device management service.
If you’re going to use your network to migrate, consider the potential load on each access point. You may want to consider migration in groups to lessen the load on your network.
If you’re erasing devices that use an eSIM, make sure you turn on Preserve Data Plan in the device management Remote Wipe command.