Considerations: Migrating devices from a source server

Keep the following things in mind when migrating devices to a destination

BlackBerry UEM

Item	Considerations
Best practice	It is a best practice to migrate one device for each unique configuration, for example, different groups, policies, app configurations, etc.) to make sure the destination server is set up correctly before migrating the rest of your devices.
Maximum number to migrate	You can migrate a maximum of 2000 devices at a time from a source server.
Destination BlackBerry UEM	Before you migrate devices verify that BlackBerry UEM supports the device type and OS.
Users	The users must exist in the destination BlackBerry UEM domain. You must migrate all of a user's devices at the same time.
Managed iOS devices on a BlackBerry UEM source	iOS devices must have the latest version of the BlackBerry UEM Client installed. iOS devices that are assigned an App lock profile can't be migrated because the BlackBerry UEM Client can't be opened for the migration In the app settings for all applicable apps, clear the Remove the app from the device when the device is removed from BlackBerry UEM check box. If you attempt to migrate without performing this step, the app is removed and the device may be unenrolled from BlackBerry UEM . However, even if you clear this check box, the app may still be removed during migration if the setting has not been delivered to the device. For more information on tracking commands being delivered to a device, visit support.blackberry.com/community to read article 102688.
Managed Android devices on a BlackBerry UEM source	Android Enterprise devices must have the latest version of the BlackBerry UEM Client installed. You can't migrate Android devices that have a work profile using a Google account or Google domain.
Chrome OS devices on a BlackBerry UEM source	You can migrate Chrome OS devices.
Windows devices	You can't migrate Windows devices.
macOS devices	You can't migrate macOS devices.
MDM controls ( BlackBerry UEM )	Devices activated with " MDM controls " temporarily lose access to email when the migration begins. Email services are restored when the migration is complete.
Groups	You can't migrate a device that belongs to a shared device group. These devices do not appear in the migration list.
BlackBerry Dynamics -enabled devices	BlackBerry Dynamics apps All BlackBerry Dynamics apps compatible with migration are migrated. BlackBerry Dynamics apps that are incompatible with migration are wiped when the administrator triggers the migration. These apps must be reactivated on the destination BlackBerry UEM . For migrations from an on-premises BlackBerry UEM source database, all BlackBerry Dynamics apps must be at BlackBerry Dynamics SDK version 7.1 or later. For migrations from a Good Control (standalone) instance, all apps must be at BlackBerry Dynamics SDK version 4.0.0 or later. To determine the version of SDK used for the apps to be migrated, run the container activity report on Good Control . In the Migrate devices screen, the Incompatible containers column displays the number of BlackBerry Dynamics apps for each device that can't be migrated and the total number of BlackBerry Dynamics apps for each device. Click on the number to see the BlackBerry Dynamics apps that are incompatible with migration. Make sure that the user has entitlements for the app on the destination BlackBerry UEM . If the app doesn't have the entitlement, after migration, the user will receive a message that the app is blocked. BlackBerry Dynamics apps are not migrated if the destination BlackBerry UEM already has apps registered for that user. BlackBerry Access for Windows , BlackBerry Access for macOS , and BlackBerry Enterprise BRIDGE are not supported for migration. After the migration is complete, users must re-enroll these apps in UEM . Custom apps migrate only if the source and destination servers have the same organization ID. It is possible to merge two organizations. For more information, visit support.blackberry.com/community to read article 47626. Devices with BlackBerry Dynamics apps activated by multiple users should not be migrated. BlackBerry Dynamics apps that are locked due to compliance or remotely by the administrator before the migration process may no longer function after migration and may need to be reactivated. If the BlackBerry UEM Client is locked, the user may not be migrated. The migration process does not track or guarantee migration of the BlackBerry UEM Client and apps activated on a device after that device's data is cached. Administrators should refresh the user cache before each migration. Device authentication The authentication delegate must be the same on the source server and the destination BlackBerry UEM . You can change the authentication delegate after migration. For migrations from a Good Control (standalone) instance, devices with a device authentication delegate of Good for Enterprise are not migrated. After removing Good for Enterprise as the authentication delegate, refresh the cache before continuing with the migration. It is a best practice to ensure that the user is assigned the same authentication delegate on BlackBerry UEM as they had on the source server.
	Device management BlackBerry Dynamics -only devices (no BlackBerry UEM Client) are visible in the source database until all apps are migrated. BlackBerry Dynamics-enabled devices are always enrolled for BlackBerry Dynamics on the destination server. For migrations from a Good Control (standalone) instance, Good Dynamics MDM enrollments are not migrated. The user must unenroll from MDM. If the destination BlackBerry UEM requires MDM, the user must manually delete the old MDM profile and install and activate the BlackBerry UEM Client and re-enroll the device for MDM. Operating system Devices with an unknown operating system are not migrated. Chat sessions The source BEMS server may keep stale Connect chat sessions open for up to 24 hours so the user may temporarily appear to be logged into chat from two devices. Unread Connect chat messages are deleted during migration. Users should log out of Connect before migration. Users If a user has more than one device with BlackBerry Dynamics apps, all the devices are automatically selected for migration. You can't migrate devices for the same user from multiple Good Control source servers. You can migrate devices from multiple Good Control sources, but the users cannot already have a BlackBerry Dynamics device on the destination BlackBerry UEM . Unlock keys If a user forgets the password for a BlackBerry Dynamics app after migration has been initiated, but before the container has completed migration, the unlock access key must be obtained from the BlackBerry UEM source. After the migration is complete the key must be obtained from the destination BlackBerry UEM . Access keys After migration, access keys can no longer be generated on the source server. The device is removed from the source server at the start of migration and access keys can no longer be generated. After the migration is started iOS device users must swipe up to close apps. To trigger the migration on the device, it is a best practice to first open the app that is configured as the authentication delegate on the device. Not all apps will appear on the launcher until the migration is complete. After migration, app icon arrangements in the launcher are reset to the default. Devices upload the VIP rules, bookmarks, and user certificates to the new server.

.json configurations
(

Good Control

only)

For migrations from a

Good Control

(standalone) instance, .json configurations are not migrated. Because .json configurations are global, migrating them could overwrite .json configurations in the destination database. Ensure that any required .json configurations are reapplied in the destination server.

Section:

Migrating users, devices, groups, and other data from a source server

Device migration quick reference