How to Cancel Atlassian: Complete Guide

What is Atlassian

Atlassian offers a suite of team collaboration and software development tools, including Jira, Confluence, Bitbucket, Trello and associated Marketplace apps. Products are sold as per-user cloud subscriptions (Free, Standard, Premium and Enterprise tiers) with monthly or annual billing options and per-seat scaling for teams.

Atlassian publishes tiered plans and a cloud licensing model where monthly subscriptions use progressive per-user pricing and annual subscriptions are billed by user tier; features differ by plan (storage, support levels, automation limits and uptime SLAs).

Atlassian also operates original and improved billing experiences and has updated billing models such as maximum quantity billing, which affects how user changes and prorations appear on invoices.

How Atlassian subscriptions are structured and what that means

Plans are sold per product and per user, with Free, Standard, Premium and Enterprise options; billing can be monthly or annual and some products or Marketplace apps carry separate charges.

Key service-specific details: Atlassian generally treats fees as non-refundable except where an initial purchase is returned within defined windows, and monthly renewals are enabled by default unless otherwise changed.

Customer experiences and cancellation analysis

What users report

Independent reviews and community threads show repeated customer complaints about billing surprises, difficulty locating cancellation and account-deletion paths, and mixed outcomes on refund requests.

Common user comments include unexpected renewals, invoices larger than anticipated after seat changes, and frustration at trying to reverse charges or delete sites created during trials. Several reviewers cite long response times from support when disputing a charge.

Recurring issues and practical takeaways

Users often misunderstand how seat-based billing and maximum quantity billing work: charges may reflect peak user counts during a billing period and prorations may be added on subsequent invoices. Tracking your billed user quantity is essential to avoid surprises.

Refund requests are time-sensitive. Atlassian’s published return/refund windows are narrow and tied to initial purchases: monthly purchases may be eligible only within the first paid month, and annual purchases within 30 days of payment. Users who request refunds outside those windows frequently report denials.

What to expect from Atlassian policies and timing

Cancellation effect: for many cloud subscriptions, cancellation is scheduled to take effect at the end of the current billing period and sites remain accessible for a short grace period after the subscription expires. In some product docs Atlassian states that a canceled subscription will be deactivated 15 days after the end of the subscription period.

Data retention and reactivation windows vary by product: typical retention windows noted in documentation include short access periods after deactivation and longer retention for paid subscriptions; reactivation within those windows can restore data.

Refund eligibility is limited: Atlassian’s published policy allows refunds for initial purchases within the stated days and generally disclaims refunds for renewals or charges outside those windows. The customer agreement also states that fees are non-refundable except as provided.

Billing mechanics that cause surprises

Maximum quantity billing means your invoice may be based on the largest number of users during the billing period rather than the lowest or average, and adding users can create prorated charges added to the next invoice. This can create higher-than-expected bills if user numbers spike.

Proration and seat adjustments: proration applies differently for monthly versus annual plans; examples in documentation show prorated increases when seats are added mid-period and limited or no credits when seats are removed under certain billing models.

Documentation checklist

• Invoice and payment dates: record invoice numbers and exact dates of charges.
• Billing account identifier: note any billing account, order or site IDs shown on invoices.
• User counts and timing: keep a snapshot of your active user count on billing start and end dates.
• Plan and tier details: note product, plan name and whether the charge was monthly or annual.
• Support/ticket references: record any case or ticket IDs and the date/time of interactions.
• Screenshots: capture billing pages, invoices and any messages that reference renewals or charges.

Common pitfalls and mistakes to avoid

• 1. Confusing peak user billing with per-day user counts - review your billed user quantity rules to avoid seat-driven spikes.
• 2. Missing narrow refund windows - initial purchase windows are limited; act quickly if you want a return.
• 3. Assuming immediate credit on cancellation - many plans retain access until period end and do not issue prorated refunds.
• 4. Not exporting data before deactivation - data retention windows can lapse and permanent deletion policies apply after set periods.
• 5. Relying only on public comments - community threads help set expectations but may not reflect case-by-case outcomes.

Disputes, refunds and escalation paths

Best practice is to compile complete billing documentation and raise a formal dispute promptly if a charge appears incorrect. Refund requests are judged against published policy windows and the Customer Agreement return policy.

If a dispute concerns reseller-managed purchases, refunds and remediation may be handled by the reseller rather than directly by Atlassian; contract terms can vary.

How billing types affect refunds and timing

Monthly subscriptions are typically eligible for refunds only within the first paid month, while annual subscriptions have a 30-day return window for initial purchases; renewals are usually excluded. These conditions are documented in Atlassian policies and the Customer Agreement.

Enterprise and partner-managed contracts may include different terms, so check your specific order or agreement for bespoke refund language.

Note: Local pricing displays on Atlassian’s site vary by region and billing engine; where exact A$ list prices are not published uniformly, prices are shown as "Varies" to avoid incorrect conversions. Use your billing statements for exact amounts.

Practical checklist before you act

• Confirm billing dates and your billed user quantity - check the exact charge and the user tier used for the invoice.
• Export critical data - export repositories, pages and attachments if you might lose access after deactivation.
• Gather invoices and receipts - collate invoice numbers, amounts and timestamps for any dispute or refund request.
• Note plan type and purchase date - these determine refund eligibility under published windows.
• Track correspondence IDs - keep any support case numbers and dates for escalation records.

Address

• Address: Level 6, 341 George Street Sydney NSW 2000 Australia

What to do after cancelling Atlassian

After cancellation, verify that the subscription appears inactive on your billing records and monitor subsequent bank or card statements for unexpected charges. Keep all documentation for at least one billing cycle in case you need to dispute a post-cancellation invoice.

If you have data to retain, export it immediately and confirm the exported files open correctly; retention windows are finite and differ between free, paid and Marketplace products.

Finally, if a refund or billing discrepancy persists, escalate with clear documentation of purchase dates, invoice numbers, user counts and dates when charges occurred; reference the published policy windows when you present your case.