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

# Move a Rep to a New Territory

> Reassign stores between reps, control what FieldKo transfers when an account owner changes, and refresh both reps' devices.

When stores move from one rep to another, you change the account owner or account team in Salesforce. Because FieldKo is in your org, an owner change does more than a standard Salesforce transfer: FieldKo shares the store's current ranging with the new owner and, if you turn it on, moves future visits and shares last month's orders. Use this checklist for a territory realignment, a rep who changes area, or a rep who takes over a vacant territory.

## User Permissions Needed

| To do this | You need |
| - | - |
| Change account owners | Edit access to the accounts and Transfer Record |
| Change the **Transfer Data On Change Of Account Owner** options | FieldKo Manager Permission Set |
| Create call cycles and transfer visits | FieldKo Manager Permission Set |

## Before You Begin

* List the stores that move, and the rep who takes over each one.
* Ask the rep who's losing stores to tap **Sync** and wait for it to finish, so their unsynced work reaches Salesforce first.
* If the new rep is new to FieldKo, complete [Add a New Rep](/platform/day-to-day/add-a-rep) first.

## What FieldKo Transfers When the Owner Changes

When an account's **Account Owner** changes, FieldKo hands some of the account's data to the new owner. Changing account team members doesn't trigger any of this.

| Data | What Happens | Controlled By |
| - | - | - |
| Current ranging | Always shared with the new owner, with edit access | Always on |
| Future visits | The account's **Not Started** visits that belong to the old owner and are planned after today move to the new owner, with their tasks (up to 250 visits per account). Each visit's **Sales Representative**, owner, and call cycle change to the new owner's. | **Transfer Not Started Future Visits** |
| Last month's orders | The account's orders with a PO date or created date in the previous calendar month are shared with the new owner, with edit access. | **Share Last 1 month Orders** |

The two options are under **Transfer Data On Change Of Account Owner** on the **FieldKo Configuration** tab, under **Basic**. They save to the **Transfer Account Data Configuration** custom setting. For the steps, see [When an Account Changes Owner](/managers/field-campaigns#when-an-account-changes-owner).

<Note>
  FieldKo runs these transfers only when the **Branding** custom setting has a record named **Brands**. Sync needs this record too, so it's usually there. If it's missing, see [Rep Can't Sync at All](/admin/support-diagnostics#rep-cant-sync-at-all).
</Note>

## Move the Rep

Complete these steps in order. Each step links to the full instructions.

<Steps>
  <Step title="Choose What Transfers">
    On the **FieldKo Configuration** tab, click **Basic**. Under **Transfer Data On Change Of Account Owner**, choose whether to move future **Not Started** visits and share last month's orders. Save your changes. See [When an Account Changes Owner](/managers/field-campaigns#when-an-account-changes-owner).
  </Step>

  <Step title="Check the New Owner's Call Cycles">
    Make sure the new owner has active call cycles that cover the dates of the visits that will move. See [Call Cycles](/admin/call-cycles-and-visits#call-cycles).

    If **Transfer Not Started Future Visits** is on and a visit's date isn't covered, Salesforce blocks the owner change with "Sorry! No Call Cycle available. Please Contact your Manager or Administrator".
  </Step>

  <Step title="Change Account Ownership or Account Teams">
    Change the **Account Owner** of each store to the new rep. To move many stores at once, use a mass transfer or a data load. See [Transfer Multiple Accounts](https://help.salesforce.com/s/articleView?id=sf.admin_transfer.htm\&type=5) in Salesforce Help and [Import and Update Data](/platform/data/import).

    If your reps share stores through account teams instead, remove the old rep from each account team and add the new rep. If your org uses the **Public Group** user reporting hierarchy, update the account sharing or group membership instead. See [Accounts in Scope](/admin/offline-data#accounts-in-scope).
  </Step>

  <Step title="Optional: Move the Remaining Visits">
    FieldKo moves visits automatically only when the owner changes and the option is on. To move other **Not Started** visits, such as visits on stores shared through account teams, use the **Transfer Visits** tab. The new rep must own the account or be on its account team. See [Transfer Visits](/managers/field-campaigns#transfer-visits).
  </Step>

  <Step title="Optional: Update Brand Teams">
    If **Enabled** is selected on the **Branding** custom setting's **Brands** record, make sure the new rep is a **Brand Team Member** of the brands linked to their new stores. See [Add a New Rep](/platform/day-to-day/add-a-rep).
  </Step>

  <Step title="Ask Both Reps to Sync and Reset Sync">
    Ask each rep to tap **Sync**, wait for it to finish, and then run **Reset Sync**. Stores that leave a rep's scope stay on their device until they reset, and resetting makes sure the new rep gets the full history for their new stores. See [Reset Your Offline Data](/sync/reset-sync).
  </Step>
</Steps>

**To confirm:** On a moved store, the **Account Owner** (or account team) shows the new rep, and its future visits show the new rep as **Sales Representative**. After the reset, the new rep sees the store and its visits in the app, and the previous rep no longer sees it.

## See Also

* [Run Field Campaigns](/managers/field-campaigns)
* [Control What Syncs to the App](/admin/offline-data)
* [Set Up Manager Visibility](/platform/access/manager-visibility)
* [Remove a Rep's Access](/platform/day-to-day/remove-a-rep)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.