Prerequisites: Migrating users, devices, groups, and other data from a source server Skip Navigation

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

Complete the following prerequisites before you begin a migration.
Prerequisite
Details
Log in
Log in to
BlackBerry UEM
as a Security Administrator. Only one administrator should perform migration activities at any one time.
Check the software version
To migrate data to
BlackBerry UEM
:
  • The
    BlackBerry UEM
    instance you are migrating data from must be version 12.13 or later.
  • The
    Good Control
    (standalone) instance that you are migrating data from must be at version 5.0 or later.
Configure the
BlackBerry UEM
company directory connection
Configure the destination
BlackBerry UEM
company directory connection in the same way that it is configured in the source. For example, if the source is configured for
Active Directory
integration and it is connected to the example.com domain, configure the destination
BlackBerry UEM
for
Active Directory
integration and connect it to the example.com domain.
Migration does not work if the company directory on the destination server does not match the company directory on the source server. 
Defragment the databases (
BlackBerry UEM
)
Defragment the source databases and the destination
BlackBerry UEM
database (if one exists) before you begin migration. If you are migrating a large number of users, you should defragment the destination
BlackBerry UEM
database after you migrate each set of users. For more information about defragmenting a
Microsoft SQL Server
database, visit www.technet.microsoft.com to read the article “Reorganize and Rebuild Indexes.”
BlackBerry UEM Client
For migrations of
BlackBerry Dynamics
-enrolled
BlackBerry UEM Client
s and
BlackBerry Dynamics
apps from an on-premises
BlackBerry UEM
source database, the latest
BlackBerry UEM Client
must be installed on the device.
Check the status of
BlackBerry Dynamics
apps
Check the
BlackBerry Dynamics
SDK version of all
BlackBerry Dynamics
apps you want to migrate. This includes first-party apps,
BlackBerry Dynamics
apps, third-party ISV apps, and internal custom apps.
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. You can find the SDK version in the release notes for the app.
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
BlackBerry Dynamics
apps that are not supported for migration are wiped from the device when the administrator starts the migration.
Check the status of
BlackBerry Dynamics
app entitlements
Make sure that:
  • The destination
    BlackBerry UEM
    has the same list of
    BlackBerry Dynamics
    app entitlements as the source server.
  • All migrated user accounts are assigned the same list of
    BlackBerry Dynamics
    app entitlements on the destination
    BlackBerry UEM
    as they have on the source server.
  • The authentication delegate is the same on the source server and the destination server. You can change the authentication delegate after migration.
  • The user's
    BlackBerry Dynamics
    profile allows the
    BlackBerry UEM Client
    to be activated by
    BlackBerry Dynamics
    , if the user's
    BlackBerry UEM Client
    on the source server is also activated by
    BlackBerry Dynamics
    .
Missing entitlements will result in
BlackBerry Dynamics
apps being disabled after migration.
Review organization IDs
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.
Check that the required ports are not blocked by a firewall or in use by other software
Ensure that port 1433 (TCP) and port 1434 (UDP) are unblocked on the
Microsoft SQL Server
.