In this article
A new pricing page can go live while existing customers still have the old commercial deal. The harder question is what else changes before their next bill. In its 2025 billing update, Figma separated migration to new seats and workflows from the renewal that triggered higher Full-seat prices. That split is useful for product teams: changing the product’s structure, changing access, and changing what an existing customer pays do not have to happen on one date.
A launch date cannot describe every customer state
A customer can be using the new product structure at the old price. Another can have old add-on access that expires at renewal. A third may need to approve a paid change before a colleague can continue a task. Calling all three “migrated” hides the decisions that matter to the customer.
Separate four questions when planning a change: what the account is entitled to use, how people request or approve additional access, which prices apply, and when the next commercial decision takes effect. Those states may move together. When they do not, the product, billing system, and support team need the same explanation.
Two published migrations make the distinction concrete. They are historical examples of rollout design, not evidence that either approach improved retention.
Figma changed the seat structure before every customer paid the new price
Figma’s December 2024 announcement placed existing-plan migration to Full, Dev, Collab, and View seats and the new upgrade workflows on March 11, 2025. The higher Full-seat price and prorated-billing changes followed at each customer’s first renewal on or after that date. The announcement also described administrator approval by default for seat upgrades that incurred additional cost.
The important product distinction is between what an account can do and the commercial terms currently attached to it. A new seat label need not mean that the account has already paid the new price. Similarly, a changed approval workflow can affect daily collaboration before the price change appears on the renewal invoice.
A migration plan should make those combinations explicit. Otherwise, an administrator can see the new interface while a colleague or support agent assumes the old billing behavior still applies.
Slack made renewal the boundary for an old add-on
Slack’s published transition rules moved self-serve Business+ customers to the new plan at their first renewal after August 17, 2025. Customers who had bought the Slack AI add-on through the website kept it until that renewal, then received the AI features included in their paid plan.
That could change access as well as billing. The page says Pro customers needed Business+ to retain features such as recaps and translations. It also separates feature controls from commercial terms: turning off AI features does not reduce the plan price.
The lesson for migration design is that “the add-on is now included” may be an incomplete explanation. The account’s destination plan determines which parts of the former add-on continue. Customers need an account-specific answer about what they keep, what they lose, and which choice preserves the work they value.
Put the dates beside the changes they control
Historical documentation checked October 15, 2026. Slack rows concern purchases through its website; negotiated contracts require their own terms.
| Decision | Figma announcement | Slack transition rules |
|---|---|---|
| Product structure | New seats and approval workflows from March 11, 2025 | New plan version at the applicable renewal |
| Price or commercial boundary | First renewal on or after March 11, 2025 | First renewal after August 17, 2025 for the described self-serve transition |
| Legacy access | Existing plans migrate to the new seat structure | Existing AI add-on continues until the applicable renewal |
| Customer control | Administrator approval for additional-cost seat upgrades | Feature access can be restricted, but disabling AI does not lower the price |
The exact comparison operator matters. “On or after” includes the boundary date; “after” does not. Preserve that wording when turning an announcement into billing or entitlement rules. A loosely paraphrased date can become a different cohort of customers.
Build a migration record for each affected account
Your migration design should be able to answer the following without relying on the public pricing page:
- Which plan and price does the account have now?
- Which product, seat, or permission changes happen before renewal?
- Which legacy features remain available, and until when?
- What changes automatically at renewal, and what requires a customer decision?
- What will happen if the customer adds a user, changes a plan, or renews early during the transition?
The last question is easy to miss. Customers continue using and changing the product while a migration is in progress. A rule that works for an untouched account may not explain an account that adds seats or changes its contract midway through the transition.
Turn these questions into explicit examples for product, billing, support, and customer communications. Give each example an initial state, a customer action, and the resulting access and charge. Where a contractual exception exists, represent it as an exception rather than allowing it to disappear into a generic plan name.
Evaluate the whole transition, including the next renewal
A successful technical migration means the intended states changed correctly. It does not establish that customers understood the offer or continued to receive worthwhile value.
Follow affected accounts through the point where they encounter the new commercial terms. Examine access problems, unexpected charges, support requests, plan changes, and renewal decisions alongside revenue. Keep accounts that have not yet reached the relevant renewal separate from those that have. The product may have migrated them already; the customer has not yet made the same commercial decision.
Sources
Something we should clarify?
Suggest a correction


