Can I migrate devices from a custom DPC to AMAPI?

Yes, but with important limitations.

Google supports migrating devices from a custom DPC (using the Play EMM API) to the Android Management API (AMAPI) without requiring a factory reset. This is done through the AMAPI SDK's DPC migration functionality.

Prerequisites:

• The device must be managed by a custom DPC integrated with the AMAPI SDK
• The device must be enrolled with the Google Play EMM API
• The device must belong to a Managed Google Play Accounts enterprise
• Android 9+ for fully managed devices; Android 11+ for work profiles on company-owned devices

Key limitations:

• Migration is only supported within the same EMM vendor. It cannot be used to move devices between different EMM providers
• The migration is irreversible. Once a device moves to AMAPI, it cannot be migrated back to the custom DPC
• The migration must be initiated by the custom DPC on the device, coordinated with the EMM backend

How it works:

1. The EMM sets up a policy in AMAPI for the migrating device
2. A migration token is created and sent to the custom DPC on the device
3. The custom DPC calls the migration method in the AMAPI SDK
4. Android Device Policy takes over management from the custom DPC

Notable example: Microsoft Intune completed its migration of Android personally-owned work profiles to AMAPI, with corporate-owned migrations following.

For more context on how DPC migration works and what to expect, see AMAPI publicly adds support for DPC migration.