Move SaaS seats between customer workspaces without double billing

Establish which legal entity owns each subscription and whether the agreement permits moving seats or prepaid value between them. Two workspaces under the same corporate group can have different payers, terms and renewal dates. Obtain the customer's authorized instruction and the business's commercial approval before changing quantities or applying one account's credit to another.

Record whether the transfer moves users, purchased capacity or both. A user can gain access to a new workspace while the old subscription remains contractually active. The transfer plan should identify the retained services and any overlap needed for migration, including whether that overlap is paid or provided as a documented concession.

List the service periods already paid on each account and the proposed effective date. Stripe's billing-cycle guidance explains how anchors align renewal periods. When two subscriptions have different anchors, copying the same quantity change to each can produce mismatched partial periods. Review both previews together rather than accepting them independently.

For illustration, the source workspace may be paid through December 31 while the destination renews monthly on the tenth. Write down how the remaining source commitment and the first destination period will be handled. If there is an approved credit, identify exactly where it will be recorded and whether the destination can use it under the platform's rules.

Create one transfer record linking the source and destination subscriptions, quantities and effective timestamps. Assign a coordinator so product access and billing changes occur in the intended order. Preserve enough overlap to avoid interrupting authorized work, while making any overlapping commercial charge explicit and approved.

After the change, compare the purchased seats on both subscriptions with the approved combined total. Check invoices and credits generated by each action. A successful user move is incomplete if the source still renews at the old quantity or the destination bills for seats already covered by another approved arrangement. Keep exceptions open until both sides are reconciled.

Compare the source and destination license features as well as their seat counts. A seat in one workspace may include a different service tier, usage allowance or support arrangement. Confirm what the customer authorized and whether any change in value requires an amendment, rather than treating all seats as interchangeable units.

For a hypothetical move of ten seats, retain the old product, new product and agreed pricing treatment beside the paired quantity changes. If the destination offers different functionality, ask the product owner to verify the access result and the commercial owner to approve the terms. Finance can then explain any price difference as part of the transfer rather than leaving it as an unexplained billing variance.

Retain the original invoice and payment history on the appropriate accounts. Give the customer a statement that explains the transfer and identifies the next renewal amount for each remaining subscription. If one workspace closes, review outstanding balances and access to historical billing documents before disabling it.

Provide accounting with the paired adjustment record and the applicable service dates, including any change in payer. Check the first full renewal after transfer and reconcile it to the customer confirmation. Keep the transfer identifier in both account records so future support and finance staff can understand why quantities moved without interpreting the source reduction as churn and the destination increase as an unrelated new sale.