Move accounts from node to node

Updated
  • Updated on Jan 7, 2026
  • Published on Nov 28, 2024
  • 1 minute(s) read
  • CC
 Prev Next

You can easily move accounts to different nodes within a hierarchy for territories, teams, and products. There are two ways you can move accounts; the Move option from the grid action menu or drag and drop accounts from one node to another from the grid.

Note

  • Drag and drop is only available in Proposed View.

  • No records can be moved to the parent. When initiated, the record will get moved to Unassigned.

  • You must have read-write permissions to drag and drop.

  • Only completed transactions can be moved.

  • Records cannot be moved to the same target node. The following error displays:

    Some of the selected records are already in the target node. Please select another node or select a different set of records.

  1. Go to Territories > Manage Accounts.

  2. Find and select the records you want to move.

  3. Use one of the following methods to move accounts:

The Move option is available whether you are in a proposed state or not.

  1. From the grid actions menu, click Move.

    Move option highlighted in the grid actions menu.

  2. Select the territory you want to move the records to.

  3. Click Confirm.

    Note

    You can search by territory name and if you have show role details enabled, you can search for a person's name for the role you've turned on.

Drag and drop is an easy way to move accounts to different nodes.

  1. Drag selected records from the grid to the node in the hierarchy panel you want to move them to.

    Drag and drop accounts from the grid to the node in the hierarchy panel.

  1. In the Move Confirmation window, under the first question select how you want account families to be treated.

  2. Under the second question, select how you want to categorize accounts:

    1. Do not set named type account status: Does not categorize or tag accounts.

    2. Set moved accounts as Named Accounts: Categorizes the accounts as Named Accounts.

    3. Set moved accounts as Named Exceptions: Categorizes the accounts as Named Exceptions.

  3. Select to commit or propose the changes:

    1. Commit Changes: Changes are saved in a current state and will export during the next scheduled export job.

    2. Propose Changes: Changes are saved in a purposed state (best if you or another user needs to review changes before they are committed for export).