Can Android devices be migrated remotely from one Hexnode portal to another?Solved

Hexnode currently does not support remotely migrating managed devices directly from one portal to another. To move a device to a different Hexnode portal, the device must first be disenrolled from the existing portal and then enrolled again into the new portal. This applies even if both portals use the same configuration or policies. The general workflow is:

1. Disenroll the device from the current Hexnode portal.
2. Remove any remaining management profile or MDM association from the device, if required by the platform.
3. Enroll the device into the new Hexnode portal using the preferred enrollment method.
4.  Reassign policies, apps, and configurations from the new portal.

For Android devices, the exact reenrollment steps may vary depending on the enrollment method used, such as Android Enterprise, device owner enrollment, profile owner enrollment, or other supported Android enrollment modes. A direct portal-to-portal migration option without disenrollment is not available at this time.

That’s unfortunate. I was hoping this could be pushed remotely, especially for devices that are already deployed in the field. Is this something Hexnode has planned?

A remote portal migration feature would definitely be useful for larger deployments, especially where devices are not physically accessible. At present, there is no confirmed release timeline for this capability. The available approach remains disenrollment from the current portal followed by enrollment into the target portal. If this is needed for your deployment, the best option is to treat it as a feature request and include details such as:

• Device platform, for example Android
• Approximate number of devices
• Current enrollment method
• Whether devices are remote or physically accessible
• Whether the requirement is to avoid device reset, manual intervention, or both.

These details help clarify the migration use case and the expected behavior.