---
title: "Move accounts from file"
slug: "move-accounts-from-file"
description: "Bulk move accounts to territory nodes by uploading a CSV file. Easily manage account states and track results with our guided wizard."
tags: ["Bulk Account Move", "CSV Upload", "move accounts", "Territory Nodes"]
status: "update"
updated: 2026-07-22T21:49:33Z
published: 2026-07-22T21:49:33Z
canonical: "support.fullcast.com/move-accounts-from-file"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.fullcast.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

> [!NOTE]
> Early access feature
> 
> This feature is currently available for early access. Contact your CSM for more information.

## 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**](/plan-and-pay/docs/how-to-use-named-accounts-and-named-exceptions) and **State**, which indicates whether the account move will be done in a proposed or committed state.

| Field | Required | Allowed values |
| --- | --- | --- |
| Account ID | Yes | Salesforce Account ID; must be unique within the file. |
| Node ID | Yes | Must match an existing node ID in the territory hierarchy. |
| Named Type | No | `Named Account` or `Named Exception` (This is case and spacing sensitive.) |
| State | No | `Proposed` or `Committed`. (This is case and spacing sensitive.) |

> [!NOTE]
> 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**.

![Actions menu open on a territory node, with Move accounts from file highlighted.](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/image(668).png)

> [!NOTE]
> 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.

![File upload screen with a CSV file selected and an option to replace it before continuing.](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/image(629).png)
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.

![Field mapping screen matching CSV columns to the Account ID and Node ID fields.](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/image(626).png)

> [!NOTE]
> 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.![Validation summary with total, valid, warning, and error row counts, plus toggles for state and named type.](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/image-1782958279962.png)
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.

![Error detail dropdown expanded for a flagged row in the preview table.](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/image-1782959933127.png)

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]
> 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](/plan-and-pay/docs/how-to-rerun-rules) 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.

![Error file download and final account count confirmation.](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/image(628).png)