Cancelling Asana: 30 days' notice in the terms, seats sold in increments, refunds and your projects

A paid Asana plan renews automatically, monthly or annually, until a billing owner or admin cancels it. Asana's help centre says you can cancel at any time, that the cancellation takes effect at the next renewal date, and that you keep paid features until the end of the current billing period. The same article says your ability to downgrade, adjust or cancel is subject to Asana's Subscriber Terms, and those add a deadline: notice at least 30 days before the renewal date if you do not want to renew, and written notice at least 30 days before the end of the term if you want fewer paid users or a lower plan. The other things that catch small teams out are seats sold in fixed increments, an upgrade that has to cover every member of a workspace or organisation, a refund policy that is simply no, and projects that become inaccessible when you drop to the free Personal plan.

This guide covers how Asana bills, how seats are added and reduced, the notice rules, how to cancel or downgrade, refunds, renewal prices and what happens to your projects and data. It is based on Asana's Subscriber Terms (last updated 1 September 2026, and applying to new order forms and renewals effective on or after 16 September 2026; if you agreed to an earlier version, the terms say the new one applies from your next renewal), Asana's pricing page, and Asana's help centre articles on cancelling a plan, upgrading or changing a plan, billing settings in the admin console, payment methods and invoices, managing organisation settings and importing and exporting projects, all checked on 31 October 2026. The Subscriber Terms are between your business and Asana, Inc., and their definition of an order form includes an online order, so a plan bought in the app is covered as well as a signed one. If your business has a separate written agreement with Asana, the terms say the online Subscriber Terms do not apply, so check that agreement first. Prices are left out.

How an Asana plan bills

• The current plans: Asana's pricing page lists Personal, which is free and described as for one or two people, with 2 users; Starter; Advanced; and Enterprise, priced through Asana's sales team, with Enterprise+ for the highest security and compliance needs. The help centre still refers to legacy plans called Premium, Business and Legacy Enterprise, so an older account may be on one of those.
• What you upgrade: Asana's upgrade article says you can upgrade a workspace, a team within an organisation, a set of teams collected in a division, or an entire organisation. Upgrading a workspace or organisation means upgrading for all its members; upgrading a team covers only that team's members. Subscriptions cannot be transferred between separate workspaces and organisations, so if you upgrade the wrong one, you have to cancel it and upgrade the right one.
• Monthly or annual: you choose the billing cycle when you upgrade, and Asana says annual plans receive a discount equivalent to two months. Section 4.2 of the terms says that, unless the order form specifies otherwise, subscription fees are based on annual periods.
• Automatic renewal: section 4.4 says that, unless the order form says otherwise, a subscription renews automatically at the end of its term for a period equal to the previous one, at Asana's then-current rates, and that you authorise Asana to charge the fees on or after the renewal date.
• The billing owner: during the upgrade you appoint a billing owner, who must be a member of the space being upgraded. The upgrade article says the billing owner can update billing information, upgrade, downgrade or cancel the plan, appoint a new billing owner, and receives a copy of the latest invoice every billing cycle. In a paid organisation they also become an admin. Asana's billing settings article says admins and super admins can now manage billing too, but only on auto-pay plans; a manually invoiced plan may still only be managed by the billing owner. When an admin makes changes in the Billing tab, the billing owner gets an email.
• Paying: the billing owner can switch between card and PayPal from the Billing tab. Asana offers invoice payment for annual plans of 20 or more members. Section 4.1 says invoiced amounts are due within 30 days of the invoice date, and that Asana can suspend an account that is overdue and not brought up to date within ten business days of notice.
• Taxes: section 4.3 says fees exclude taxes. Asana's pricing page says that if you are registered for VAT, you should add your VAT number at checkout to have the exemption processed.
• Resellers: section 2.8 says that if you bought through an authorised distributor, reseller or marketplace, references to the order form mean the ordering document you signed with that partner, so its renewal terms are the ones to read.

Seats: sold in increments, and cuts wait for renewal

Asana sells paid plans by the seat. The upgrade article says Asana does not offer paid plans for one user, and offers 2, 3, 4 and 5 seat plans for smaller teams. Beyond that, the pricing page says seats are added in increments:

• Between 2 and 5 users in total: one seat at a time.
• Up to 30 users in total: increments of 5.
• Up to 100 users in total: increments of 10.
• Up to 500 users in total: increments of 25.
• More than 500 users: increments of 50.

Billing owners can add seats in the admin console, or in team settings for a team plan; on a manually invoiced plan, the upgrade article says you are directed to Asana's sales team instead. The Billing tab shows your seat utilisation and, according to the billing settings article, lets you add or reduce seats. Section 4.2 of the terms says you can add users at any time on written notice, with email acceptable, and that Asana may count your users periodically and, if you have gone over what you bought, invoice the extra increments pro rata for the rest of the current term. The help centre does not say how a seat you add yourself part-way through a term is charged, so check the confirmation and the next invoice.

Reductions are the trap. Section 4.2 says that to reduce the number of paid users, or to move to a lower plan, you must give Asana written notice, with an in-app notification or email acceptable, at least 30 days before the end of the current term, and that Asana reflects the change in your billable account on the renewal date. So removing people part-way through a term does not change what that term costs, and because seats come in increments, removing a few people may not take you down a band. The pricing page says Starter includes unlimited free guest seats for clients and contractors that do not increase your licence count, so check how your plan counts guests before you add them. Removing leavers belongs on your software offboarding checklist; reducing the seat count, at least 30 days before renewal, is the other half.

Notice: 30 days in the terms, none in the help centre

The help centre gives no deadline. Asana's cancellation article says paid users can cancel at any time, with the cancellation taking effect at the next renewal date, and the pricing page says that if you cancel before your next renewal, you keep paid features until the end of the current subscription period.

The Subscriber Terms do set one. Section 4.4 says the subscription renews and Asana charges for it unless either party tells the other at least 30 days before the renewal date that it does not intend to renew. Section 4.2 sets the same 30 days for cutting seats or moving to a lower plan. That is a real notice period, the same length as monday.com's 30 days and Notion's. Neither clause separates monthly plans from annual ones.

Section 11.2 says notices under the agreement, other than Asana's general notices to all customers, must be in writing and sent to the business postal or email address a party has given in writing, such as on the order form, and count as given when received. Section 4.2 accepts an in-app notification or email for seat cuts and downgrades. The practical route is to cancel or change the plan in the admin console at least 30 days before renewal and keep a record of when you did it. If you are on a signed order form, read its renewal clause and send a notice of non-renewal to the address it gives; see how to serve a notice of non-renewal for keeping proof that will stand up if a renewal charge is disputed.

Cancel or downgrade

Asana's cancellation article says a billing owner, admin or super admin can cancel the subscription of a paid organisation, division or workspace at any time. If the billing owner is leaving the business, reassign the role from the Billing tab before they go, so someone who can still cancel holds it.

Cancel a plan bought online

Click your profile photo in the top-right corner, select Admin console, open the Billing tab and, under Plan details, select Cancel plan. The cancellation takes effect at your next renewal date, not immediately, and paid features carry on until the end of the current billing period. The upgrade article adds that on an annual plan, once you have followed these steps, the subscription is cancelled automatically on the plan's renewal date.

Change tier or size

From the Billing tab, select Change plan, choose between Starter and Advanced and select Confirm and change plan; Edit plan is where you change the plan's size. You must be the billing owner or an admin to change tier or size. Moving from Advanced to Starter removes only the Advanced features, and Starter features stay available. The cancellation article says a downgrade to Personal takes effect at the end of the current subscription period, and section 4.2 says a downgrade or seat cut shows in your billable account on the renewal date, which is why the 30 days matter.

Manually invoiced plans

On a manually invoiced plan you cannot cancel with a button. The cancellation article says to select Contact billing in the Billing tab, or use Asana's support form; the request creates a support case and Asana follows up by email with next steps. Allow time for that exchange before the 30-day point, and keep the case reference.

Trials

To cancel a trial, follow the same steps and select Cancel trial. Asana says that if you cancel on or before the trial expiry date you will not be charged, you keep paid features until the trial ends, and you then go back to the plan you were on before. A trial with no payment details expires without any cost.

Refunds: Asana says no

Asana's pricing page answers the refund question in one line: Asana does not offer refunds. Section 4.1 of the terms says amounts due are non-cancellable and non-refundable unless the agreement provides otherwise. The terms provide two exceptions, and neither is a change of mind:

• The service does not match its documentation: section 3.2.1 says that if a material non-conformity persists more than 30 days after your written notice of it, you can end the order form and, as your only remedy, get a refund of prepaid, unused fees for the rest of the term.
• Asana breaches the agreement: section 5.3 says that if you end an order form under section 5.2, which covers a material breach not put right within 30 days of written notice, or Asana ceasing business or becoming insolvent, Asana refunds a prorated amount of prepaid, unused fees for the rest of the term.

Price changes

Section 4.4 says a subscription renews at Asana's then-current rates. The Subscriber Terms checked for this guide set no minimum notice period for a price rise before renewal, and the pricing page's current discount offer is labelled for new customers only. Ask Asana in writing what your renewal price will be before the 30-day notice deadline, not after it; see how to cap a renewal uplift. Section 11.11 also lets Asana revise the terms by posting a new version, which you accept by carrying on using the service, so it is worth rereading them before each annual renewal.

Projects and data after you cancel

Downgrading does not delete your data: both the cancellation and upgrade articles say upgrading or downgrading will not result in any data loss. On the free Personal plan, though, you cannot use paid features such as rules, goals or portfolios, and you lose access to projects and tasks that use paid features, although you can still export them to CSV. The pricing page puts it more bluntly: when your subscription expires, you lose access to paid features and all data associated with them. Export first.

People are the other question. The pricing page describes Personal as for one or two people, with 2 users. The cancellation article does not say what happens when a larger team drops to Personal, so if more than two people still need access, ask Asana before you cancel.

If you are leaving Asana altogether, section 5.4 applies once all your subscriptions under the agreement have expired or ended: Asana may deactivate the account straight away, makes your data available for export only if it receives your written notice within 30 days after the end date, and after that has no obligation to keep it and may delete it. You can also ask, through Asana's help centre, for your data to be destroyed, which section 5.4 says happens within 180 days, with backups deleted within a further 30 days.

To keep a copy, export each project from the drop-down menu next to its title: hover over Export/Print and choose JSON or CSV. Search views and My Tasks can be exported the same way. A full export of the whole organisation as JSON, with or without attachments, is available to super admins only on Enterprise+ and Legacy Enterprise, under Domain settings, then Domain export, and Asana says some attachment types are not included. On Starter or Advanced, plan for a project-by-project export.

A routine for Asana

1. 1Write down each paid Asana space: what was upgraded (a workspace, team, division or organisation), the plan, monthly or annual billing, the number of seats, the renewal date, the billing owner and admins, and whether you pay by card, PayPal, invoice or through a reseller.
2. 2Make sure the billing owner is a current member who reads their email, and reassign the role before they leave.
3. 3Through the term, remove leavers and watch seat utilisation on the Billing tab, remembering that adding people can take you into the next increment.
4. 4At least 30 days before renewal, decide whether to renew, cut seats, downgrade or cancel, act in the admin console or in writing, and keep the confirmation.
5. 5If you are downgrading to Personal or leaving, export the projects that use paid features to CSV or JSON before the plan ends, or on Enterprise+ request a domain export.

UK consumer protections around subscriptions mostly do not reach a business customer; see the UK subscription rules for business software. Section 11.1 of Asana's Subscriber Terms says they are governed by the laws of the State of California, with disputes going exclusively to the courts in San Francisco. Read the terms for each tool you run rather than applying one rule of thumb to all of them.

Tracking Asana in StackTrackr

Record each paid Asana space as its own tool. On annual billing, enter the cost of the full year with an annual billing cycle; on monthly billing, enter the monthly cost with a monthly billing cycle. Tick Auto-renews, set the renewal date, and under License key and seats enter the number of paid seats on the plan, not the number of people using it, updating it when you add an increment. Say in Notes what was upgraded and whether the plan is invoiced. Make the tool's owner the Asana billing owner or an admin, so the reminders reach someone who can change the plan.

Enter a notice period of 30 days and StackTrackr works out the cancellation deadline, shows it in the register's Cancel by column, and reminds you ahead of it and again on the day. The same 30 days covers both rules in the terms, not renewing and cutting seats or downgrading, and the terms do not separate monthly plans from annual ones. Starter alerts at 30 and 7 days; Team and up use a cadence you set, 90, 60, 30 and 7 days by default. Once you have cancelled, switch auto-renew off and set the renewal date to the day the plan ends, so the reminders count down to the move to Personal.

If Asana tells you your renewal price, schedule the price change with the date it applies so your forecasts include it. Keep your invoices, any order form, the cancellation confirmation and copies of written notices in the tool's document vault. Have a look at what it tracks, or start a free trial and add your Asana plan first.