Initiating the Android Enterprise migration on a device
When the migration request reaches the device, the users can initiate the migration on the device.
About this task
MaaS360® does the following checks before it initiates
the migration.
- The battery charge must be 30% or more.
- The device must be connected to the internet.
- Android devices with OS versions earlier than 7 must be encrypted.
- The time on the device and the server must be synchronized.
- The Play Store Services app must be up to date.
- The shared device must not be in a signed-out state. If a user signs out of a device, they must sign back in to the MaaS360 app before they can start the migration.
- The device must not be out-of-compliance (OOC).
Note: An error message is displayed and the migration process is stopped if the device does not meet
any of the preceding conditions.
Follow these steps to initiate the migration on the device.
Procedure
Results
The device is successfully migrated to the Work Profile. Work apps are moved to a workspace and
marked with a briefcase icon.
Note: Migration might fail in cases such as a failed Google
attestation, lost or no internet connection, failed Samsung Knox License activation, or failed
Google account creation. In these cases, you can either retry or stop the migration. If the
migration is stopped, the device is restored to Device Admin mode.
What to do next
Open the older MaaS360 app without the briefcase icon on the device and then click Continue to uninstall the app.