Prerequisities for Android Migration

To provide an intuitive end user experience for the migration, this page will guide you through a successful migration. Not completing these steps could result in a failed migration or users not being able to access all apps they need.

Device Eligibility

Device needs to be eligible for migration. For example. Samsung devices with Knox Container enabled cannot be migrated.

Check eligibility for migration by navigating to Device Details > Custom Attributes and make sure migration.eligible attribute has a value of True.

Create Smart Group to Migrate from Android (Legacy)

Before you migrate, you will need to create Smart Groups for all devices that are being migrated. You can create separate groups for staging a small number of devices for testing purposes before you deploy to all your devices.

The Workspace ONE UEM console provides a seamless process that helps you create Smart Groups to migrate all devices from Android (Legacy) to Android Work Profile deployment.

  1. Select the applicable **Organization Group (OG)**to which your new smart group applies and from which it can be managed. Selecting an OG is optional.

  2. Navigate to Groups & Settings > Groups > Assignment Groups and then select Add Smart Group

  3. Enter a Name for the smart group.

  4. Configure the Smart Group type:

    • Criteria: This option works best for groups with large numbers of devices (more than 500) that receive general updates. This method works best because the inherent details of these groups can reach all endpoints of your mobile fleet.
    • Devices or Users: This option works best for groups with smaller numbers of devices (500 or fewer) that receive sporadic, although important, updates. This method works best because of the granular level at which you can select group members. Note: Switching between the two smart group types will erase any entries and selections you might have made.

    At least one device deployed as Android (legacy) needs to be selected as eligible for migration or you will get errors while setting up the migration.

  5. Select Save.

Recreate Profiles for Android

Android Enterprise profiles are separate from device administrator, or Android (Legacy) profiles. You must re-create profiles for Android enterprise. These profiles are available for configuration after completing the Android enterprise registration.

On UEM consoles lower than 9.4.0, Android enterprise profiles are available under Devices > Profiles & Resources > Profiles > Add > Add Profile > Android > Android for Work.

On UEM consoles 9.4.0 and higher, Android enterprise profiles are available under Devices > Profiles & Resources > Profiles > Add > Add Profile > Android.

Note: If the Wi-Fi profile was configured for your Android (Legacy) deployment, you must create and assign an Android Wi-Fi profile to the devices selected for migration before you can create a migration.

Android device profiles ensure proper use of devices, protection of sensitive data, and workplace functionality. Profiles serve many different purposes, from letting you enforce corporate rules and procedures to tailoring and preparing Android devices for how they are used.

Configure Application Management

Once an application is added to the Workspace ONE UEM console, it can be distributed to device administrator, also known as Android (Legacy), and Android enterprise enrollments. If a public application has been added to the UEM console prior to Android enterprise registration, the application management section of this guide will help you configure settings so there will be no disruption to existing app assignments.

Internal applications cannot be managed for Work Profile management mode under Android Enterprise. In order to make sure internal applications are available for devices that have migrated to Work Profile, you must upload the application to the Managed Google console as a private application prior to migration.

Use Workspace ONE UEM to manage the deployment and maintenance of publicly available mobile applications from Google Play Store. Make sure every public app is approved for your organization to ensure seamless migration.

Note: If you are migrating to Work Managed devices, review your Play Store restriction policy prior to migration. If the Play Store is blocked prior to migration, your devices will be treated as AOSP Work Managed devices, and will not support public app management. If you’d like to deploy apps from the Play Store after migrating to Work Managed, ensure the Play Store is not blocked on your legacy enrolled devices prior to migration to Work Managed.

Manage Public Apps for Android (Legacy) Migration

If a public app has been added to the UEM console prior to the Android (Legacy) migration and Android Enterprise registration, this task will help you make sure all apps are imported after the migration.

These steps simply ensure the UEM console is aware the app has been approved on managed Google Play. It is now possible to assign this app to Android enterprise enrollments after the migration has completed.

  1. Navigate to (log in with the same Gmail account used to configure Android enterprise), search for the app(s) and approve it for your organization.

  2. In the UEM console, navigate to Apps & Books > Native > Public > Add Application > Android > Import from Play .

  3. Select Import once the list of approved apps displays

    After migration, the app cache is cleared and users will have to re-enter there credentials.

Verify Network Settings

The Network Requirements for Android is a list of known endpoints for current and past versions of enterprise management APIs. Check your network settings to ensure a connection between Workspace ONE, the Google Play Store, and Android devices.

Once you’ve walked through the prerequisites, you are ready to proceed with the migration with your desired device mode.

check-circle-line exclamation-circle-line close-line
Scroll to top icon