Device backup and wipe

1. A non-transitory computer-readable medium embodying program instructions executable in at least one computing device that, when executed by at least one hardware processor, direct the at least one computing device to at least:

in response to an enrollment request being received to enroll a first client device with a management service, transmit, from the management service to a second client device, a wipe request generated by the management service, the first client device and the second client device being associated with a common enterprise account, the wipe request comprising commands for the second client device to at least:

backup, to the management service, enterprise data associated with a particular application;

verify receipt of a confirmation that the management service has received the enterprise data; and

transmit, to the first client device, the enterprise data associated with the particular application;

determine, by the management service, that an entirety of the enterprise data is received from the second client device; and

transmit, from the management service, to the second client device, the confirmation that the management service has received the enterprise data, wherein

the confirmation causes the second client device to remove the enterprise data from the second client device, and

personal data associated with the second client device is retained on the second client device after the enterprise data is removed.

2. The non-transitory computer-readable medium of claim 1 , wherein the wipe request is generated based on a number of enrolled devices exceeding a predefined threshold once the first client device enrolls with the management service.

3. The non-transitory computer-readable medium of claim 2 , wherein the at least one computing device is further directed to at least:

generate translated settings based on settings of the particular application specified in the enterprise data, wherein a platform of the second client device is different from a platform of the first client device, and the translated settings are generated to be compatible with a version of the particular application for the platform of the first client device; and

transmit the translated settings to the first client device.

4. The non-transitory computer-readable medium of claim 1 , wherein the at least one computing device is further directed to at least:

determine priorities for a plurality of files of the enterprise data, the priorities being based on files characteristics comprising at least one of: estimated usage, actual usage, age, file size, date created, and date modified; and

wherein the wipe request comprises commands for the second client device to at least backup the plurality of files based on the priorities.

5. The non-transitory computer-readable medium of claim 1 , wherein the at least one computing device is further directed to at least:

receive, from the second client device, an indication that the enterprise data is removed from the second client device; and

remove the second client device from an enrolled device list to discontinue management of the second client device.

6. The non-transitory computer-readable medium of claim 1 , wherein the at least one computing device is further directed to at least: generate a user interface comprising:

a list of applications installed on the second client device, and an estimated data requirement to backup data associated with the particular application.

7. The non-transitory computer-readable medium of claim 1 , wherein the at least one computing device is further directed to at least transmit the enterprise data to the first client device in response to the first client device being successfully enrolled with the management service.

8. A system, comprising:

at least one computing device comprising at least one hardware processor; and

program instructions stored in memory that, when executed by the at least one hardware processor, direct the at least one computing device to at least:

in response to an enrollment request being received to enroll a first client device with a management service, transmit, from the management service to a second client device, a wipe request generated by the management service, the first client device and the second client device being associated with a common enterprise account, the wipe request comprising commands for the second client device to at least:

backup, to the management service, enterprise data associated with a particular application;

verify receipt of a confirmation that the management service has received the enterprise data; and

transmit, to the first client device, the enterprise data associated with the particular application;

determine, by the management service, that an entirety of the enterprise data is received from the second client device; and

transmit, from the management service to the second client device, the confirmation that the management service has received the enterprise data, wherein

the confirmation causes the second client device to remove the enterprise data from the second client device, and

personal data associated with the second client device is retained on the second client device after the enter rise data is removed.

9. The system of claim 8 , wherein the wipe request is generated based on a number of enrolled devices exceeding a predefined threshold once the first client device enrolls with the management service.

10. The system of claim 9 , wherein the at least one computing device is further directed to at least:

generate translated settings based on settings of the particular application specified in the enterprise data, wherein a platform of the second client device is different from a platform of the first client device, and the translated settings are generated to be compatible with a version of the particular application for the platform of the first client device; and

transmit the translated settings to the first client device.

11. The system of claim 8 , wherein the at least one computing device is further directed to at least:

determine priorities for a plurality of files of the enterprise data, the priorities being based on files characteristics comprising at least one of: estimated usage, actual usage, age, file size, date created, and date modified; and

wherein the wipe request comprises commands for the second client device to at least backup the plurality of files based on the priorities.

12. The system of claim 8 , wherein the at least one computing device is further directed to at least:

receive, from the second client device, an indication that the enterprise data is removed from the second client device; and

remove the second client device from an enrolled device list to discontinue management of the second client device.

13. The system of claim 8 , wherein the at least one computing device is further directed to at least:

generate a user interface comprising a list of applications installed on the second client device, and an estimated data requirement to backup data associated with the particular application.

14. The system of claim 8 , wherein the at least one computing device is further directed to at least transmit the enterprise data to the first client device that is successfully enrolled with the management service.

15. A computer-implement method, comprising:

in response to an enrollment request being received to enroll a first client device with a management service, transmitting, from the management service to a second client device, a wipe request generated by the management service the first client device and the second client device being associated with a common enterprise account, the wipe request comprising commands for the second client device to at least:

backup, to the management service, enterprise data associated with a particular application;

verify receipt of a confirmation that the management service has received the enterprise data; and

transmit the enterprise data associated with the particular application to the first client device;

determining that an entirety of the enterprise data is received from the second client device; and

transmitting, from the management service to the second client device, the confirmation that the management service has received the enterprise data, wherein

the confirmation causes the second client device to remove the enterprise data from the second client device, and

personal data associated with the second client device is retained on the second client device after the enterprise data is removed.

16. The computer-implement method of claim 15 , wherein the wipe request is generated based on a number of enrolled devices exceeding a predefined threshold once the first client device enrolls with the management service.

17. The computer-implement method of claim 16 , further comprising:

generating translated settings based on settings of the particular application specified in the enterprise data, wherein a platform of the second client device is different from a platform of the first client device, and the translated settings are generated to be compatible with a version of the particular application for the platform of the first client device; and

transmitting the translated settings to the first client device.

18. The computer-implement method of claim 15 , further comprising:

determining priorities for a plurality of files of the enterprise data, the priorities being based on files characteristics comprising at least one of: estimated usage, actual usage, age, file size, date created, and date modified; and

wherein the wipe request comprises commands for the second client device to at least backup the plurality of files based on the priorities.

19. The computer-implement method of claim 15 , further comprising:

receiving, from the second client device, an indication that the enterprise data is removed from the second client device; and

removing the second client device from an enrolled device list to discontinue management of the second client device.

20. The computer-implement method of claim 15 , further comprising:

generating a user interface comprising: a list of applications installed on the second client device, and an estimated data requirement to backup data associated with the particular application.