Considerations: Migrating devices from a source server

The users must exist in the destination 

BlackBerry UEM

 domain.

You must migrate all of a user's devices at the same time.

iOS

 devices must have the latest version of the 

BlackBerry UEM Client

 installed.

All 

iOS

 devices must be trusted (untrusted 

iOS

 devices cannot be migrated).

iOS

 devices that are assigned the App lock profile cannot be migrated because the 

BlackBerry UEM Client

 cannot be opened for the migration

Android Enterprise

 devices must have the latest version of the 

BlackBerry UEM Client

 installed.

You cannot migrate 

Android

 devices that have a work profile using a 

Google

 account or 

Google

 domain.

All 

BlackBerry Dynamics

 apps compatible with migration are migrated. 

BlackBerry Dynamics

 apps that are incompatible with migration are wiped from the device 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 cannot 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 are the same 

Good Control

 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 "remote locked" when the device is migrated may not be able to be unlocked.

If a device has a 

BlackBerry UEM Client

 activated and one or more apps are locked, and the administrator tried to migrate it, the device is no longer associated with the user or the 

BlackBerry UEM

server.

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 keep their caches up to date. 

Microsoft ActiveSync

 may not function after migration on devices with BlackBerry Work that are not cached.

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.

BlackBerry Dynamics

-only devices (no BlackBerry UEM Client) are visible in the source database until all apps are migrated.

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.

Devices with an unknown operating system are not migrated.

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.

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

.

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 

Good Control

 source. After the migration is complete the key must be obtained from the destination 

BlackBerry UEM

.

After migration, access keys can no longer be generated on the source server.

For UEM-to-UEM migration, the device is removed from the source server at the start of migration and access keys can no longer be generated.

To trigger the migration, 

Android

 users must restart their device to force the 

BlackBerry Dynamics

 apps to cold start. Sometimes a second restart is required.

iOS

 device users must swipe up to close apps. 

To trigger the migration, it is a best practice to first open the app that is configured as the authentication delegate.

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.