Answers

What is a territory swap?

A territory swap is not a re-carve. The macro model stays. Specific accounts and pipeline change hands under a defined process so no deal, quota dollar, or comp payout gets lost in the handoff.

Short answer

A territory swap is the mid-year or quarterly reassignment of accounts between reps or segments inside a sales organization. It is triggered by a rep departure, a segment migration, a new named-account tier, or a performance rebalance. The swap moves ownership of accounts and open pipeline, adjusts quotas on a prorated basis, defines deferred-opportunity credit for in-flight deals, and sets Day 1 ownership rules. A proper swap is documented and comp-neutral, with every move written to an audit log.

Key points

What matters most.

What a territory swap is, what triggers it, what has to move with the accounts, and what makes a swap defensible.

Definition

Account reassignment, not a re-carve.

A territory swap moves specific accounts and their open pipeline from one owner to another inside an existing carve. The underlying territory model (geo, segment, tier, named lists) stays the same. The swap is the delta: which logos change hands, when the clock starts, and how comp follows the work.

Common triggers

Departures, migrations, tiers, rebalances.

Four triggers drive almost every swap. A rep leaves and their book has to move. An account migrates between segments (SMB to mid, mid to enterprise). A new named-account tier is created and specific logos are pulled up into it. Or leadership rebalances load across reps for performance or coverage reasons.

What moves

Ownership, pipeline, quota, and tasks.

The account record changes owner. Every open opportunity on that account changes owner. Open tasks, next steps, and sequences follow. Quota is prorated between the outgoing and incoming reps. Closed-won revenue stays on the original rep's attainment. The swap is an atomic event, not a drip of manual edits.

Deferred credit

In-flight deals keep their origin story.

A deal mid-cycle at the time of swap carries a deferred-credit rule: the outgoing rep retains a defined percentage of the comp if the deal closes within a stated window (often 30 to 90 days). The incoming rep carries the deal to close and earns the balance. The split is written into the opportunity at swap time.

Day 1 ownership

A clean effective date, no ambiguity.

Every swap has a Day 1: the effective date on which the new ownership and quotas take effect. New activity on the account counts for the incoming rep from Day 1 onward. Any ambiguous activity in the week before Day 1 is resolved by a documented rule, not by whichever rep's manager escalates first.

Documented and comp-neutral

No rep is worse off because of logistics.

A proper swap is written down: trigger, scope, effective date, deferred-credit terms, quota proration. It is comp-neutral by design, which means a rep who loses an account does not lose the comp they earned on it, and a rep who inherits an account is not credited for work the previous rep already did.

Swap triggers

Why a swap happens in the first place.

Swaps are not random. Each one traces back to a specific event in the business. Knowing the trigger shapes the scope, the timing, and the deferred-credit terms. The six patterns below cover almost every swap a sales organization runs between formal territory reviews.

Rep departure

A seller leaves and the book has to move.

A rep resigns, is promoted into a new role, or exits for cause. Their accounts cannot sit unowned while recruiting runs. A departure swap moves the book to one or more inheriting reps, with a short deferred-credit window on any deal the departing rep sourced and advanced before the exit date.

Segment migration

An account grew out of its segment.

An SMB account doubles in headcount and crosses the mid-market line. A mid account signs a Series D and becomes enterprise. The account migrates to the segment pod that now owns it. The outgoing rep gets a deferred credit on any active opportunity; new deals belong to the incoming rep.

New named-account tier

Strategic logos get pulled up.

Leadership introduces a new strategic tier with a dedicated coverage model. Specific logos are pulled out of their current pods and onto the strategic list. The swap moves the logo to the strategic rep with the understanding that the old rep carries their in-flight deals under a deferred-credit split.

Performance rebalance

Load is uneven across the team.

One rep is drowning in logos and another is thin. Leadership moves a subset of accounts to even the load. The rebalance is explicit about which logos, on which date, with what deferred credit, so the giving rep is not punished and the receiving rep is not credited for pipeline they did not build.

Acquisition integration

A merger folds two books into one.

The company acquires another business, and overlapping accounts have to be deduplicated and assigned. The swap pulls accounts from the acquired team's reps and routes them into the new combined carve. Historical comp on closed deals stays on the original rep; forward pipeline moves to the new owner.

Specialization change

A rep's focus shifts.

A rep moves from a general territory into a vertical specialist seat (healthcare, public sector, financial services). Accounts outside the new specialty are swapped out to peers; accounts inside the specialty are swapped in from peers. The swap formalizes a role change that would otherwise happen informally over months.

What has to move

The six things a swap transfers.

A swap is more than updating the Owner field on an account. Pipeline, tasks, quota, comp expectations, and audit trails all follow. The next six cards cover what moves, in the order it has to be handled so no revenue or comp dollar falls through the gap.

Account record

Owner changes on the parent.

The account record's owner field is updated to the incoming rep as of the Day 1 effective date. Related contacts inherit the new owner unless they are specifically retained by the outgoing rep for an existing relationship. The team membership on the account updates in the same move.

Open opportunities

Pipeline follows the account.

Every open opportunity on the moving account changes owner to the incoming rep. The forecast rolls up under the new rep from the next forecast cycle. The deferred-credit rule is written onto each open opportunity so the comp engine knows how to split the payout when the deal closes.

Tasks and next steps

Open work goes with the deal.

Open tasks, scheduled calls, pending email sequences, and the next-step field all transfer to the incoming rep. Nothing is left on the outgoing rep's to-do list after Day 1. The incoming rep walks into a clean handoff instead of a backlog of overdue items signed by someone else.

Quota proration

The number splits by effective date.

If the swap happens on day 180 of a 365-day plan, the outgoing rep's quota is prorated to their time with the book (180 days) and the incoming rep's quota is prorated to their time with it (185 days). No rep carries a full-year number on a book they only held for half the year.

Closed-won history

Attainment on past deals stays put.

Revenue the outgoing rep closed before the swap stays on their attainment and comp. A swap never reaches backward into closed-won history. The incoming rep's attainment starts counting on their first closed-won deal on the newly inherited book, from Day 1 forward.

Audit log entry

The move is written down.

The swap writes an audit row for every account and every opportunity touched: previous owner, new owner, effective date, trigger, deferred-credit terms. The log is append-only. When a comp dispute surfaces three months later, the log is what resolves it in one query instead of a committee meeting.

Running the swap

The six steps that make a swap defensible.

A swap goes wrong when the paperwork is missing, the dates are fuzzy, or the deferred-credit terms are debated after the fact. The sequence below is how mature sales organizations run swaps so reps trust the process and leadership can defend every move. Each step is explicit, documented, and in the audit log.

Step 1

Scope the swap in writing.

RevOps drafts the swap scope: which accounts, which opportunities, which outgoing and incoming reps, which trigger, which effective date. The scope is reviewed by sales leadership and finance before any system change. Scoping in writing is what prevents mid-swap edits that break the comp math downstream.

Step 2

Set the deferred-credit terms.

For every open opportunity, the swap defines a deferred-credit percentage and a window (typically 30, 60, or 90 days). If the deal closes within the window, the split applies. After the window, full credit goes to the incoming rep. The terms are the same for every rep on the same swap, no case-by-case negotiation.

Step 3

Notify the reps involved.

Outgoing and incoming reps are told before Day 1 with the full scope: which accounts, which opportunities, deferred-credit terms, prorated quota, and the Day 1 date. No rep learns about a swap because an account disappeared from their view. The notification is attached to the swap record for the audit trail.

Step 4

Execute on Day 1, not in dribs.

The system flips ownership on all accounts and opportunities in the swap as a single transaction on the Day 1 effective date. Nothing is moved early. Nothing is moved late. One atomic event is what keeps the audit log clean and the reps' pipelines coherent for the forecast call the next week.

Step 5

Reprorate the quotas.

Finance updates the quota records for both reps to reflect the prorated number. The attainment dashboards show the new quota and the new book from Day 1 forward. The old book continues to show on the outgoing rep's history but no longer counts toward their active target.

Step 6

Write the retrospective.

Thirty days after the swap, RevOps writes a short retrospective: did the handoff hold, how many deferred-credit deals closed in-window, were there disputes, did the incoming rep's early activity match the plan. The retrospective informs the next swap, so the process compounds instead of resetting every time.

Run the swap as a single event, not a month of edits.

Strkr executes territory swaps as atomic transactions on the Day 1 effective date, moves accounts and open pipeline together, writes deferred-credit rules onto each open opportunity, prorates quotas automatically, and logs every move to an audit trail. Reps trust the process. Finance trusts the math.

People also ask

Related questions.

What is the difference between a territory swap and a re-carve?

A re-carve redraws the whole territory model: new segment lines, new named-account lists, new coverage pods. A swap moves specific accounts within the existing carve from one owner to another, usually mid-year or quarterly. Re-carves are big, infrequent events (typically annual). Swaps are smaller, more frequent adjustments driven by a specific trigger like a departure, a segment migration, or a performance rebalance.

What triggers a territory swap?

The common triggers are a rep departure (someone leaves and their book has to move), a segment migration (an account grew or shrank out of its current segment), a new named-account tier (strategic logos pulled up into a dedicated coverage model), a performance rebalance (load is uneven across the team), an acquisition integration (two books fold into one), or a specialization change (a rep moves into a vertical seat and their non-vertical accounts swap out).

What is deferred-opportunity credit in a territory swap?

Deferred credit is the rule that says the outgoing rep retains a defined percentage of the comp on an open deal if that deal closes within a stated window after the swap (commonly 30, 60, or 90 days). The incoming rep carries the deal to close and earns the balance. The split is written onto the opportunity at swap time so the comp engine applies it automatically when the deal closes.

How are quotas handled when accounts swap mid-year?

Quotas are prorated based on the effective date. If a swap happens on day 180 of a 365-day plan, the outgoing rep's quota is prorated to the 180 days they held the book, and the incoming rep's quota is prorated to the 185 days they will hold it. No rep carries a full-year number on a book they only held for half the year, and no rep gets a free ride on a book they just inherited.

What are Day 1 ownership rules?

Day 1 is the effective date of the swap. From Day 1 onward, every new activity on the swapped accounts (meetings, emails, new opportunities, forecast rollups) counts for the incoming rep. Activity that happened before Day 1 stays on the outgoing rep. Any ambiguous activity in the days immediately before or after Day 1 is resolved by a written rule set at swap time, not by escalation.

Does a territory swap affect closed-won deals?

No. A swap never reaches backward into closed-won history. Revenue the outgoing rep already closed stays on their attainment and their comp. The swap only affects account ownership going forward, open pipeline, and quota proration from the effective date. This is a core property of a comp-neutral swap: no rep loses credit for work they already finished.

How often should a sales organization run territory swaps?

Most mature sales organizations run swaps as needed between formal territory reviews, with a lightweight quarterly cadence to clear accumulated migrations and rebalances. Big triggers (rep departures, acquisitions, new tiers) run on their own timeline. The goal is to swap often enough that the carve reflects reality, but not so often that reps lose confidence in the stability of their book.

What makes a territory swap defensible?

Four things: a written scope (which accounts, which opportunities, which reps, which effective date, which trigger), explicit deferred-credit terms that apply uniformly across the swap, an atomic Day 1 execution with no drip of manual edits, and an audit log that records every ownership change with the previous and new owner, the effective date, and the deferred-credit terms. With those four, a swap holds up to any comp dispute or leadership review.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.