Move accounts from file

Move accounts to territory nodes in bulk by uploading a single CSV (comma-separated values) file. Each row moves one account to the node ID you specify, so a single file can send different accounts to different territory nodes in the same upload. A wizard guides you through the process.

Before you begin

• Contact your CSM or the Customer Support team (customersupport@fullcast.com) to enable this feature.

• Ensure you have sufficient permissions. Role-based users with read-only permissions for territory account moves cannot move accounts.

Prepare your CSV file

Your file needs to include at least the account ID and the Node ID, which is the unique system ID of the destination territory. It may also include columns for Named Type and State, which indicates whether the account move will be done in a proposed or committed state.

Tip

When you get to the upload screen in the next step, click Node ID reference to download a CSV of every node ID in your territory hierarchy — the list covers the whole hierarchy, not just the node you start from. You can also download a blank CSV template from the same screen.

Start a bulk move

1. From any node in the territory hierarchy, open the node's Actions menu (⋮).

2. Select Move accounts from file.

Note

The node you have selected when you start the wizard has no effect on where accounts move. Each row's Node ID column in your CSV sets its own destination, so one upload can send accounts to multiple different territory nodes.

Upload and map your file

1. Drag and drop your CSV file, or browse to select it.

2. Optional: Click Replace to swap in a different file before continuing.

   

3. On the mapping screen, match each of your columns from the CSV to the corresponding Fullcast field. Account ID and Node ID must both be mapped before you can continue.

   

Note

There is no hard row count limit. Large files process in the background and notify you when they finish.

Review and set the account state

1. Review the validation summary, which shows how many rows are valid and flags any warnings.

2. Next to State, click Proposed or Committed to determine what state the moved accounts will have. Note that the State you select here only applies to rows that did not have a value for State in your uploaded file.

3. Optional: Update the Named Type. If a named type was included in the CSV, that selection sticks. If no selection was made in the CSV, then the selection made here will apply.

4. In the preview table, rows with errors will provide a dropdown so you can inspect the issue.

   

   Rows are flagged against the following rules. Rows with an error are left out of the move entirely; rows with a warning still move, but are worth reviewing afterward.

   Issue	Classification	Behavior
   Missing Node ID	Error	Row skipped.
   Missing Account ID	Error	Row skipped.
   Duplicate Account ID within file	Warning	First occurrence wins; later duplicates are ignored.
   Unknown Node ID (not in the territory tree)	Warning	Import allowed; the account moves to that node ID even though it doesn't currently exist in your hierarchy.
   Invalid Named Type	Error	Row skipped.

5. Click Move Accounts.

   Warning

   If you do not pin accounts by selecting a Named Type, they may get moved to their rule-determined territory if a rerun rule happens later.

Finish and review the results

After the import runs, the summary breaks down the results:

• Moved: records successfully moved.

• Skipped: records with invalid data.

• Failed: records already in the target node, or other errors.

If any rows are skipped or failed, click Download error report to see the reason for each one. Click Done to complete the import and confirm the updated account counts in the target node.