Description:
Sometimes an object might need to be moved from one client to the other.
There are some things that should be considered, such that LCM is not actually moving any object, instead, it is deleting the old object and creating a new one with the exact same settings and identifiers (except TT1 and TT2 ids). Thus, object history WILL NOT and CANNOT be transferred.
Notes:
If a large amount of objects need to be moved, a GUI consultation can be opened to ask the SW team to perform it more efficiently.
When transferring objects between different SP (LCM accounts), make sure the original SP and destination SP have the same payment plans available, otherwise there might be issues.
Required information:
IMEI or other object id | |
Destination client | |
Archival/deletion of original object |
OPTION 1: CLONING OF ORIGINAL OBJECT TO ARCHIVE COMPANY AND ORIGINAL KEPT WITH FAKE IMEI
1- Login to superadmin LCM.
2- Go to Objects, search the object and click on Edit.
4- Click on Change company and type in or select New company
5- Select “set original object hidden (only TT1) with fake IMEI at old company” and click on “Save”.
Result:
Original object will be preserved in original company with same name but a different random IMEI (no new data will be accepted for this object, only historical data will be kept, and client will be charged for archived object).
New object will be created in destination company with exactly the same LCM settings (including IMEI) as the original object (but different TT1 and TT2 id) and without TT2 tracking history.
If original object's history in original company does not need to be preserved, see option 2.
OPTION 2: CLONING OF ORIGINAL OBJECT TO ARCHIVE COMPANY AND ORIGINAL DELETED
If archival version of the object does not need to be kept in original company, select “delete original object from old company” and click on “Save”.
Result:
Original object will acquire Pending delete state.
New object will be created in destination company with exactly the same LCM settings (including IMEI) as the original object (but different TT1 and TT2 id) and without TT2 tracking history.