You can move devices to a different account individually or in bulk as follows:


  1. Click  on the left sidebar menu.
     
    The Devices screen will appear and list all the devices in the account you are logged in to. (See Switching Accounts for details on how to change the account you are viewing.)
      
  2. Locate the rows of the devices you want to move to a different account.
     
    If necessary, you can use the Search feature to find them, as shown in Searching for Devices.
     
  3. Select the check boxes of the devices.
    Note: You can select multiple devices as follows:
     
    1. Click the check box at the top left of the grid.
       
      The Select options will appear.
        
    2. You can select the first 20 devices by clicking Select 20 Items on This Page.
       
      You can select all the devices in the grid by clicking Select All X Items.
  4. In the options bar above the grid, click  to the left of Bulk Actions.
     
    The Bulk Device Actions dialog box will appear.
      
  5. Leave Move selected in the list of options on the left.
     
  6. Click the Destination Account drop-down arrow and choose the account to which you want to move the devices from the list.
    Note: You can type in the field to narrow your results to certain accounts. After you have typed four characters, only matching account names will remain in the drop-down list.
  7. If you previously have had the move fail due to missing asset associations, groups, or PEG behaviors, you can select Force Move Devices to force the account change. ( means selected, and  deselected.)
    Caution: You should use the force-movement feature only if you are absolutely certain that this will not break any needed associations! Any associations that are restricting the move will be removed. You will be warned of the reasons the move was originally blocked, so you will be aware of what you are disassociating. See the section "Entities Affected by a Force Move" below for an explanation of how the association/disassociation will work.
    The changes you are making will be delineated in the Activity Name field.
      
  8. Click Process.
     
    A success message will appear at the bottom of the screen.
      
  9. Click Dismiss to exit it. (Or you can wait a few seconds, and it will automatically close.)


Entities Affected by a Force Move


Here are how various entities/fields will be affected when you force a move for the devices to the new account:


  • Device configuration: If the configuration is noninheritable or inaccessible in the account the devices are being moved to, the default device config will be set on the device.
     
  • PEG behavior: If any behavior is associated directly on the device and noninheritable or inaccessible in the target account, the default device config will be set on the device.
    Note: If the force move will remove the PEG behavior or PEG configuration, a warning message will be displayed informing you that moving a device without an associated PEG behavior/PEG configuration will result in telematics data not being properly decoded in the event data JSON.

    Therefore, if any of the devices being moved are sending telematics data,     make sure that you assign the needed PEG behavior/PEG configuration immediately after the move.
  • Schedule: If an associated schedule is noninheritable or inaccessible in the target account, it will be removed (set to null on the device).
     
  • IO profile: If an associated IO profile is noninheritable or inaccessible in the account the devices are being moved to, it will be removed (set to null on the device).
     
  • Service profile: If an associated service is noninheritable or inaccessible in the destination account, it will be removed (set to null on the device).
     
  • Group: If an assigned group is noninheritable or inaccessible in the new account, its association will be removed (set to null on the device).
     
  • Asset: Any assets the devices are assigned to will be moved to the target account as long as all the assets' associations are accessible in that account. When an asset is moved, its associations will be affected as follows:
     
    • Schedule: If an associated schedule is noninheritable or inaccessible in the target account, it will be removed (set to null on the asset).
       
    • IO profile: If an associated IO profile is noninheritable or inaccessible in the account the devices and assets are being moved to, it will be removed (set to null on the asset).
       
    • Route: If an associated route is noninheritable or inaccessible in the target account, it will be removed (set to null on the asset).
       
    • Sensor layout: If an associated layout is noninheritable or inaccessible in the new account, it will be removed (set to null on the asset).
       
    • Assets: Any accessible assets that are assigned to the asset will retain their association.
       
    • Drivers: Any accessible drivers that are assigned to the asset will retain their association.
       
    • Group: If an assigned group is noninheritable or inaccessible in the new account, its association will be removed (set to null on the asset).
       
    • Device: The devices assigned to the asset will have already been moved to the target account if the associated entities are accessible in that account.