Migrate nickname cache for email systems and devices
A method for migrating a nickname cache via a migration manager is described. The method includes the migration manager locating where the nickname cache is stored and locating where the nickname cache is to be migrated. Once the source and target devices are located, the migration manager can generate any necessary transformations so that the data migrated from the source device to the target device is compatible. The nickname cache can then be extracted from the source device, transformed and stored into the nickname cache of the target device.
1. A method to migrate a nickname cache via a migration manager, the method comprising:
in the course of a data migration operation, locating a nickname cache to be migrated, wherein the nickname cache is stored in a source device;
determining that the nickname cache is not in use;
locating a target device where the nickname cache is to be migrated via a network;
generating a transformation, wherein the transformation maps a first data format associated with the source device with a second data format associated with the target device;
responsive to a determination that the nickname cache is not in use, extracting data associated with the nickname cache from the source device in the first data format;
transforming the extracted data from the source device in the first data format to the second data format that is compatible with the target device; and
migrating, via the network, the extracted data from the nickname cache of the source device to the nickname cache of the target device.
2. The method of claim 1 , wherein locating the nickname cache to be migrated is based on input from a user associated with the source device, wherein the user input provides an identity of the source device to the migration manager.
3. The method of claim 1 , wherein locating the target device where the nickname cache is to be migrated to is based on input from a user, wherein the user input provides an identity of the target device to the migration manager.
4. The method of claim 1 , further comprising identifying that the target device does not already has a nickname cache.
5. The method of claim 4 , further comprising instructing the target device to generate a nickname cache.
6. The method of claim 4 , further comprising evaluating the nickname cache associated with the target device, wherein the evaluation results in identifying a list of entries already stored in the nickname cache of the target device.
7. The method of claim 1 , wherein migrating the extracted data from the source device to the target device comprises comparing entries associated with the nickname cache of the source device with entries associated with a nickname cache of the target device to identify one or more duplicate entries.
8. The method of claim 7 , further comprising ignoring the duplicate entries found in both the nickname cache of the source device and the nickname cache of the target device.
9. The method of claim 7 , further comprising modifying the duplicate entries found in the nickname cache of the target device based on which of the duplicate entries found in both the nickname cache of the source device and the target device is more current.
10. A system to migrate a nickname cache via a migration manager, the system comprising:
a source device comprising a nickname cache to be migrated;
a target device where the nickname cache is to be migrated; and
a migration manager, the migration manager including a processor that is operable to execute instructions stored in memory to cause the system to perform operations comprising:
in the course of a data migration operation, locate the nickname cache to be migrated;
determine that the nickname cache is not in use;
locate the target device where the nickname cache is to be migrated via a network;
generate a transformation, wherein the transformation maps a first data format associated with the source device with a second data format associated with the target device;
responsive to a determination that the nickname cache is not in use, extract data associated with the nickname cache from the source device in the first data format;
transform the extracted data from the source device in the first data format to the second data format that is compatible with the target device; and
migrate, via the network, the extracted data from the nickname cache of the source device to the nickname cache of the target device.
11. The system of claim 10 , wherein the migration manager locates the nickname cache to be migrated based on input from a user associated with the source device, wherein the user input provides an identity of the source device to the migration manager.
12. The system of claim 10 , wherein the migration manager locates the target device where the nickname cache is to be migrated based on input from a user, wherein the user input provides an identity of the target device to the migration manager.
13. The system of claim 10 , wherein the migration manager further identifies whether the target device already has a nickname cache.
14. The system of claim 13 , wherein the migration manager further instructs the target device to generate a nickname cache when the target device does not already have a nickname cache.
15. The system of claim 13 , wherein the migration manager further evaluates the nickname cache associated with the target device, wherein the evaluation results in identifying a list of entries already stored in the nickname cache of the target device.
16. The system of claim 10 , wherein the migration manager migrates the extracted data from the source device to the target device by comparing entries associated with the nickname cache of the source device with entries associated with the nickname cache of the target device to identify one or more duplicate entries.
17. The system of claim 16 , wherein the migration manager ignores the duplicate entries found in both the nickname cache of the source device and the nickname cache of the target device.
18. The system of claim 16 , wherein the migration manager modifies the duplicate entries found in the nickname cache of the target device based on which of the duplicate entries found in both the nickname cache of the source device and the target device is more current.
19. A non-transitory computer-readable storage medium, having embodied thereon instructions executable by a processor to cause a system to perform operations comprising:
in the course of a data migration operation, locating a nickname cache to be migrated, wherein the nickname cache is stored in a source device;
determining that the nickname cache is not in use;
locating a target device where the nickname cache is to be migrated via a network;
generating a transformation, wherein the transformation maps a first data format associated with the source device with a second data format associated with the target device;
responsive to a determination that the nickname cache is not in use, extracting data associated with the nickname cache from the source device in the first data format;
transforming the extracted data from the source device in the first data format to the second data format that is compatible with the target device; and
migrating, via the network, the extracted data from the nickname cache of the source device to the nickname cache of the target device.
20. The non-transitory computer-readable storage medium of claim 19 , wherein migrating the extracted data from the source device to the target device comprises comparing entries associated with the nickname cache of the source device with entries associated with a nickname cache of the target device to identify one or more duplicate entries.