Management service migration using web applications

1. A system, comprising:

at least one computing device; and

at least one memory comprising executable instructions, wherein the instructions, when executed by at least one processor, cause the at least one computing device to at least:

generate, by a migration service, a web application to migrate a client device from a first management service to a second management service, wherein a respective management service enforces compliance rules for client devices that are used by an enterprise;

identify, based on a user interface of the web application, a request to migrate the client device from the first management service to the second management service;

transmit, to the first management service, an un-enrollment request to un-enroll the client device from the first management service;

transfer, by the migration service, management data for the client device from the first management service to the second management service, the management data comprising: a user group for the client device, and at least one compliance rule for the client device, wherein the migration service temporarily stores the management data in a temporary device record of the migration service;

receive, from the second management service, an enrollment link for the client device to enroll with the second management service; and

redirect, by the web application, the client device to complete an enrollment of the client device with the second management service based on the enrollment link.

2. The system of claim 1 , wherein the enrollment link comprises a time-limited enrollment token that uniquely authenticates the client device with the second management service, wherein the time-limited enrollment token is valid for a predetermined time period.

3. The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:

transmit, to the second management service, a request for enrollment data for the client device, wherein the request for enrollment data comprises at least one of: a device identifier of the client device, user credentials, and an identity of an enterprise managing the client device; and

wherein the enrollment link is received based on the request for enrollment data.

4. The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:

receive, from the first management service, a registration status of the client device from the first management service, wherein the registration status indicates that un-enrollment of the client device from the first management service is complete.

5. The system of claim 4 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:

transmit, to the first management service, an API call comprising a device identifier of the client device, wherein the registration status is received based on the API call.

6. The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:

generate a link to the web application; and

transmit the link using at least one of: an email, a text, an instant message, an application notification, or a messaging service.

7. The system of claim 6 , wherein the link is a unique link for the client device, the unique link comprising a parameter associated with the client device.

8. A method implemented by instructions executed by at least one computing device, the method comprising:

generating, by a migration service, a web application to migrate a client device from a first management service to a second management service, wherein a respective management service enforces compliance rules for client devices that are used by an enterprise;

identifying, based on a user interface of the web application, a request to migrate the client device from the first management service to the second management service;

transmitting, to the first management service, an un-enrollment request to un-enroll the client device from the first management service;

transferring, by the migration service, management data for the client device from the first management service to the second management service, the management data comprising: a user group for the client device, and at least one compliance rule for the client device, wherein the migration service temporarily stores the management data in a temporary device record of the migration service;

receiving, from the second management service, an enrollment link for the client device to enroll with the second management service; and

redirecting, by the web application, the client device to complete an enrollment of the client device with the second management service based on the enrollment link.

9. The method of claim 8 , wherein the enrollment link comprises a time-limited enrollment token that uniquely authenticates the client device with the second management service, wherein the time-limited enrollment token is valid for a predetermined time period.

10. The method of claim 8 , further comprising:

transmitting, to the second management service, a request for enrollment data for the client device, wherein the request for enrollment data comprises at least one of: a device identifier of the client device, user credentials, and an identity of an enterprise managing the client device; and

wherein the enrollment link is received based on the request for enrollment data.

11. The method of claim 8 , further comprising:

receiving, from the first management service, a registration status of the client device from the first management service, wherein the registration status indicates that un-enrollment of the client device from the first management service is complete.

12. The method of claim 11 , further comprising:

transmitting, to the first management service, an API call comprising a device identifier of the client device, wherein the registration status is received based on the API call.

13. The method of claim 8 , further comprising:

generating a link to the web application; and

transmitting the link using at least one of: an email, a text, an instant message, an application notification, or a messaging service.

14. The method of claim 13 , wherein the link is a unique link for the client device, the unique link comprising a parameter associated with the client device.

15. A non-transitory computer-readable medium comprising executable instructions, wherein the instructions, when executed by at least one processor, cause at least one computing device to at least:

generate, by a migration service, a web application to migrate a client device from a first management service to a second management service, wherein a respective management service enforces compliance rules for client devices that are used by an enterprise;

identify, based on a user interface of the web application, a request to migrate the client device from the first management service to the second management service;

transmit, to the first management service, an un-enrollment request to un-enroll the client device from the first management service;

transfer, by the migration service, management data for the client device from the first management service to the second management service, the management data comprising: a user group for the client device, and at least one compliance rule for the client device, wherein the migration service temporarily stores the management data in a temporary device record of the migration service;

receive, from the second management service, an enrollment link for the client device to enroll with the second management service; and

redirect, by the web application, the client device to complete an enrollment of the client device with the second management service based on the enrollment link.

16. The non-transitory computer-readable medium of claim 15 , wherein the enrollment link comprises a time-limited enrollment token that uniquely authenticates the client device with the second management service, wherein the time-limited enrollment token is valid for a predetermined time period.

17. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:

transmit, to the second management service, a request for enrollment data for the client device, wherein the request for enrollment data comprises at least one of: a device identifier of the client device, user credentials, and an identity of an enterprise managing the client device; and

wherein the enrollment link is received based on the request for enrollment data.

18. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:

receive, from the first management service, a registration status of the client device from the first management service, wherein the registration status indicates that un-enrollment of the client device from the first management service is complete.

19. The non-transitory computer-readable medium of claim 18 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:

transmit, to the first management service, an API call comprising a device identifier of the client device, wherein the registration status is received based on the API call.

20. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:

generate a link to the web application; and

transmit the link using at least one of: an email, a text, an instant message, an application notification, or a messaging service.