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, two downloads help you build your file:

• Node ID reference - a CSV of every node in your territory hierarchy, with each node's Node ID, Node Name, and a Level 1, Level 2, … column showing where it sits. It covers the whole hierarchy, not just the node you start from, so you can look up the right destination Node ID for each account.

• CSV template - a blank file with the exact import headers ready to fill in: Account ID, Node ID, Named Type, and State.

Tip

Before you plan a big move, export your current accounts so you can see each one's status and territory in your spreadsheet while you decide where things should go - and so you can carry the values you want to keep into your import file. Go to Territories > Manage Accounts, add the columns you need with the Column Chooser, then click the Export icon.

Helpful columns to add before you export:

• Named Type - each account's current Named Account or Named Exception status, so you can carry it into your import and not clear it by accident (see the warning below).

• Current Node and Current Node Id - where each account sits today.

• Ultimate Parent and Parent Id - to plan how corporate families should move together.

• Owner Name - the current owner of each account.

For how to add columns and what each field means, see How to use Column Chooser and Fullcast account system fields reference. For the export itself, see Export Grid Data.

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 limit on the number of accounts. Very large files run in the background: Fullcast finishes the move behind the scenes and notifies you when it's done, with a result report you can download. For these background runs, use the result report to confirm what moved - the on-screen, row-by-row validation is lighter than it is for smaller files that finish right away.

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.

   Warning

   The Named Type in your file (or the value you set here) overwrites each account's current status. The wizard doesn't show an account's existing Named Account or Named Exception status, and your file takes precedence:

   • If you leave Named Type blank for an account that moves to a new node, its existing Named Account or Named Exception status is cleared.

   • An account that's already in the node you're moving it to keeps its current status.

   To keep current designations, include the Named Type column in your file with the right value for each row. Exporting your accounts first (see the tip above) gives you those values to start from.

   Note

   A move can also handle corporate families as a group - for example, keeping child accounts where they are, moving children with their parent, or consolidating a family at the destination. If account families matter for where these accounts should land, review Treatment of account families before you run the move.

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

   

5. Rows are flagged according to the rules listed below. 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.

6. 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 that moved to a new node.

• Skipped: records that weren't moved because they were already in the destination node, or because of a warning - for example, an account or node ID that isn't in your data, or a duplicate account ID within the file.

• Failed: records left out of the move because of an error, such as missing or invalid data or a permissions problem.

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.