When your project tool changes its plans: what to do in the next 30 days
When your project tool changes its plans, read the notice for three things: what changes, when it reaches your account and what you keep if you do nothing. Then price the next 12 months at your real team size, export your data whatever you decide, and make the call within 30 days: stay, move to a cheaper plan, or leave.
Most changes in 2026 did not hit existing customers on day one. New plans went to new accounts first, and current customers kept their old terms until a renewal or a later notice. Use that gap to compare the cost of staying with the work involved in moving.
Contents
- What should you look for in the notice?
- SaaS price increases in 2026: what changed in project tools?
- What will the next 12 months cost?
- Why export before you decide?
- Should you stay, downgrade or move?
- What does a 30-day plan look like?
- How do you move before renewal?
- Questions about plan changes
What should you look for in the notice?
Look for the date the change reaches your account, what you keep until then, and what would make you lose it early. The headline price may describe new accounts. Your renewal terms determine what your team will pay.
Read the email, then open the vendor's pricing FAQ or help article, because the detail is usually there rather than in the announcement. Write down the answers to these questions in one place:
- Does it apply to you yet? Many 2026 changes applied to new accounts first. ClickUp's new plans went to new workspaces while existing ones kept their plan and price until a notice, with price updates no earlier than January 2027 and only at renewal. Teamhood's pricing FAQ says Classic customers keep their plan, price and workspace.
- When exactly? A renewal date, a fixed calendar date, or "at a later date". Your own renewal date matters most, so find it in your billing settings before anything else.
- What triggers the new terms early? Adding a seat, opening a new workspace, changing plan or changing billing term can each move an account onto current pricing. If the notice does not say, ask support in writing.
- What is removed, not just repriced? A feature moving to a higher plan, a free plan getting a user cap, or an add-on that can no longer be bought. These change what the tool does for you, not only what it costs.
- What happens at the limit? If the change adds a cap or a usage allowance, find out whether work stops, slows or gets billed when you pass it.
Some changes arrive with no notice at all. Basecamp added user caps to its plans around October 20, 2026, and the change showed on its pricing page without a separate announcement. Reviewers describe the same thing from the inside: one ClickUp reviewer wrote that their plan was switched and features reduced without notice, and a Wrike reviewer said things were discontinued and changed with little warning. Checking your vendor's pricing page once a quarter costs five minutes and catches most of these.
SaaS price increases in 2026: what changed in project tools?
Three kinds of change ran through project and collaboration tools in 2026: AI moving into the seat price or a separate credit allowance, user caps and seat minimums on plans that used to be flat, and free plans shrinking or disappearing. Two well-known tools also changed owners. The table separates dated plan changes from acquisitions where no price change was announced.
| When | Tool | What changed |
|---|---|---|
| 30 April 2026 | Smartsheet | The viewer seat was replaced by a free contributor seat; existing users moved automatically |
| 6 May 2026 | monday.com | New accounts must buy an AI credit bundle with their seats; older accounts keep their terms |
| 4 September 2026 | Airtable | Bending Spoons completed its acquisition; no price change confirmed |
| September 2026 | Asana | AI Teammates moved into paid plans with a monthly request allowance, capped per account |
| Autumn 2026 | Asana | The free Personal plan went from 10 seats to 2 per project and team; the older free plan is being phased out |
| Early October 2026 | Teamhood | Four plans became one paid plan with no free plan for new customers |
| 13 October 2026 | Jira | Seat prices rose, Standard from $9.05 to $9.70 per user on monthly billing (Atlassian's changes) |
| 19 October and 2 November 2026 | Notion | A new AI credit system on Business and Enterprise, first for new workspaces, then existing ones |
| Around 20 October 2026 | Basecamp | User and project caps added to every plan below Pro Unlimited (Basecamp's plans) |
| 26 October 2026 | Miro | Bending Spoons completed the deal; no plan change announced |
| 10 November 2026 | Teamwork.com | Some AI features started using monthly credits; plan prices unchanged |
| 3 December 2026 | Jira, Confluence, Rovo | Usage above the included automation and Rovo allowances will be billed separately |
| January 2027 at the earliest | ClickUp | Price updates for existing workspaces, at renewal and after a notice; new workspaces are already on the new plans |
Two patterns stand out. First, most changes reached new customers before existing ones, which gives current customers time if they use it. Second, an acquisition on its own changed nothing for customers on the day it closed. Neither Airtable's nor Miro's new owner had announced a plan or price change when the deals completed. The useful step after an acquisition is to record what you pay today, so that any later notice can be compared with your own invoice.
What will the next 12 months cost?
Work out what your team will pay over the next year on the plan you would actually need, then compare that with what you pay now. A per-user price on a pricing page is a starting point, not a bill, because seat steps, minimums, billing terms and usage charges all change the total.
ClickUp's plan cards show the kind of figure most pricing pages lead with: a monthly rate per user on yearly billing, before you multiply it by your team and add anything charged by usage.
The same change costs very different amounts depending on the team. These figures come from the vendor pages linked above:
| Change | Team | Effect over 12 months |
|---|---|---|
| Basecamp user caps | 12 people, previously on Studio at $59 a month | Now needs Pro Plus at $99 a month: $480 more a year |
| Jira Standard seat rise | 10 users, monthly billing | $9.05 to $9.70 per user: $78 more a year |
| Teamhood, new workspace | 10 people who would have fitted the old free plan | $1,440 a year billed yearly at $12 per user |
| monday.com seat steps | 4 people | Pays for 5 seats, because plans start at three and then step up in fives |
A small rise on a small team can be cheaper to absorb than any move. A cap that pushes you up a whole plan, or a free plan that ends, is a different decision. Calculate the annual difference before comparing alternatives.
What should a software price comparison include?
Comparing tools fairly means pricing each one the same way. Count these for every option, including the one you have now:
- People who need a paid seat: including contractors, and clients if the tool charges for guests.
- Seat rounding: minimum seats and the steps between them, as with monday.com's buckets.
- Billing term: yearly billing is cheaper per month but commits you; monthly costs more and keeps the exit open.
- Usage charges: AI credits, automation runs or storage beyond what the plan includes.
- The plan you would really need: if the feature you rely on sits one tier up, price that tier, not the entry plan.
Free plans have their own costs that a price comparison misses, such as user caps and missing exports. Include free-plan limits and costs in the comparison if a free tier is one of your options.
Why export before you decide?
Export your data before deciding whether to stay. An export gives you a copy of your work and reveals what a move would involve. A tool whose export misses comments or attachments is harder to leave than its price suggests.
In Miro, for example, the board menu's Export option lists a PDF, an image, a CSV spreadsheet and a board backup, and the CSV holds only the text from sticky notes, cards, tables, text boxes and shapes.
Each tool exports differently, and most leave something out. The guides for Asana exports, ClickUp exports, monday.com exports, Basecamp's archive, Notion exports, Airtable exports and Trello exports cover what each format holds. Compare what each backup saves before treating an export as a complete archive.
Open the export once you have it. Check that the projects you care about are there, that comments and files came across, and that dates and assignees survived. Store it somewhere the whole team can find, with the date in the file name.
Should you stay, downgrade or move?
Stay if the new cost is small next to what moving would take, downgrade if you are paying for features nobody uses, and move only if the change removes something you depend on or the new total is out of line with the alternatives. Moving has a real cost in setup and retraining, so a notice alone is not a reason to leave.
| If the change | Usually |
|---|---|
| Applies only to new accounts and you are not adding people | Stay, and diary your renewal date |
| Adds a few dollars per seat | Stay, and check yearly against monthly billing |
| Adds usage charges for features you do not use | Stay, and switch the add-on off or cap it where the vendor allows |
| Moves a feature you rely on to a higher plan | Price the higher plan against two alternatives |
| Ends or caps the free plan you are on | Price the paid plan against two alternatives |
| Forces a rebuild of how you work | Compare the rebuild with a move; both take effort |
The last row is easy to underestimate. One monday.com reviewer described the move from automations to workflows as meaning everything built on automations had to be rebuilt. A rebuild inside the same tool can take as long as setting up a new one, so it is worth pricing both. A Notion reviewer added a different warning: downgrading after trying a higher plan was harder than expected, which is a reason to read the downgrade terms before upgrading to escape a change.
Include setup and retraining when calculating whether switching pays off.
What does a 30-day plan look like?
Spend the first week understanding the change, the second pricing the options, the third trying the most likely one, and the fourth deciding and acting. Use this 30-day schedule to reach a decision before renewal; shorten it if the change reaches your account sooner.
- Days 1 to 3, read and record. Answer the notice questions above, find your renewal date and export your data.
- Days 4 to 10, price it. Work out 12 months on your current tool after the change, then the same for two alternatives, counted the same way.
- Days 11 to 20, test the front runner. If an alternative looks better, move one real, active project into it and run it for a week with the people who work on it.
- Days 21 to 25, decide. Stay, downgrade or move. Write down why, so the next notice does not restart the argument.
- Days 26 to 30, act. Change plan, set usage limits, or start the move. If you are moving, cancel the renewal only once the new tool holds everything you need.
How do you move before renewal?
Move the active projects first, keep the old account readable until your paid term ends, and archive a full export for everything else. Prioritize active work and keep completed-project history available in the archive.
- Use the importer if there is one. Most project tools import from the big names directly or from CSV, which keeps task names, lists and dates. Check what an import leaves out, often comments or attachments, before relying on it.
- Move by project, not by person. Move everyone working on a project together so its updates stay in one place.
- Keep the old tool read-only. Until the paid period ends, people can look things up there instead of asking for them to be moved.
- Agree a cut-over day. From that day, put new work only in the new tool and ask the team to stop updating the old one.
Breeze, for example, imports projects directly from Trello, Asana, ClickUp, monday.com, Basecamp, Notion, Airtable and Todoist, or from a CSV file, and the import steps only read from the old tool, so nothing there changes. Whatever you move to, run the import on one project first and check the result before moving the rest.
What is the first thing to do with the email?
Find your renewal date and export your data today. Then compare the next 12 months of costs and try any replacement on one active project. Decide whether to stay, downgrade or move before the new terms reach your account.
Questions about plan changes
- Do price changes apply to existing customers straight away?
- Often not. In 2026 several project tools gave new plans to new accounts first, while existing customers kept their plan and price until a renewal or a later notice. Read your vendor's pricing FAQ for your account type, and note anything that would move you onto the new terms early, such as adding seats or changing plan.
- How much notice do software vendors give before a price change?
- It varies. Some vendors send a notice and apply the change at your next renewal, while others change the public pricing page with no separate announcement. Check your billing settings and the vendor's pricing page every few months rather than relying on an email.
- Should you export your data when a vendor changes its plans?
- Yes. Exporting costs little, gives you a copy if the change goes badly, and shows how hard leaving would be. Open the export to check that the projects, comments, files and dates you need are actually in it.



