You can migrate your Android legacy-enrolled devices in Workspace ONE Express to take advantage of all the benefits of being enrolled in the Android Enterprise, including the use of work profiles and automatic separation of your work and personal applications.


You must have completed the following tasks before you can migrate Android devices.

  • Register Workspace ONE Express with Google as your Enterprise Mobility Manager. For details, see Android EMM Registration.
  • Approve public applications, Resave resources, and Resave Policies.

    Android Enterprise Apps must be approved before they can be installed on devices. Also, you must resave any Email or Wi-fi resources and policies you configured in existing Blueprints that you published before registering with Android EMM. Resaving resources and policies ensures that your devices receive all the corporate apps and settings upon migration to Android Enterprise Work Profile. You can perform all these tasks by following How Do You Migrate Blueprints for Android Enterprise.

After these prerequisites are complete, take the following steps.


  1. Navigate to Devices > Lifecycle > Legacy Android Migration.
  2. Select the New Migration button.
    A New Migration screen displays.
  3. Review the Pre Requisites. If you are sure that they have been completed, select Next to proceed.
  4. Complete the Details tab.
    1. Enter the Name and Description for this migration effort. Providing a name and description is useful for when you have more than one migration to perform. For example, you can migrate all the Android devices in one Blueprint, then later, migrate Android devices from another Blueprint.
    2. In Devices, select 'Devices in Blueprint <your Blueprint name>' to target only the legacy Android devices in a specific Blueprint or select 'All Devices' to target all legacy Android devices in your entire fleet. You can use the Search text box to locate a specific Blueprint.
    3. Customize the Message viewed by the device end user when they open the notification from their device.
    4. Select Validate and confirm that all legacy Android devices are eligible to be migrated.
    5. Select Continue to proceed.
  5. Review the migration Summary. You can see a listing of each Android device, the user name, eligibility status, and reason for ineligibility. You can also use the Search List option to locate a device in the listing.
  6. Select Create to send the notification.
    The New Migration screen closes and you are taken back to the Legacy Android Migration page in the Workspace ONE Express console.
    Table 1. Legacy Android Migration
    Setting Description
    New (button) Select to create an Android Migration.
    Edit (button) You can edit the settings of an existing migration.
    1. Locate the migration from the listing that you want to edit.
    2. Enable it by selecting the radio button located to the left of the migration name.
    3. Select the Edit button and change the migration configuration.
    Delete (button) You can delete an existing migration.
    1. Locate the migration from the listing that you want to delete.
    2. Enable it by selecting the radio button located to the left of the migration name.
    3. Select the Delete button and remove the migration from the listing permanently.
    Search Locate a specific migration from the listing by entering a search keyword.
    Refresh (button) Select to refresh the statuses of all active migrations.

    You can see the listing of all your Android migrations here, including columns for Name, Description, Devices, Devices Migrated, Total Devices, and Status.

  7. The end user receives a notification about the migration. When this notification is opened, it displays the Message you customized plus information about the migration including a way to opt out.
  8. Direct the user to select the Continue button to proceed with the migration.
    1. They can also postpone the migration, for example if their battery is low, by selecting the Not Now button.


  • The end user's Android legacy-enrolled device is upgraded to Android Enterprise Work Profile mode.
  • Their work and personal apps are separated.
  • New versions of work applications now feature a small, red toolbox badge in the corner of the app icon. This badge makes it easy to identify new versions of work apps and differentiate them from the old versions.
  • New versions of work apps can only access data from other new versions of work apps.

What to do next

Direct end users to uninstall old versions of work apps (the ones without the small, red toolbox) to limit work apps' access to personal data.