Atlassian Loyalty Discounts: How to Claim and Negotiate Them in 2026

Understanding Atlassian's Loyalty Discount Architecture

Atlassian's Ascend Migration Program offers up to 40% loyalty discounts for Data Center customers migrating to Cloud. With no new DC subscriptions available from March 30, 2026, and the last expansion window closing March 30, 2028, these credits are time-limited—and the negotiation leverage they create is at its peak right now.

The timing is critical. With Data Center reaching end-of-life (no new DC subscriptions for new customers from March 30, 2026, last expansion date March 30, 2028, and full read-only mode March 28, 2029), Atlassian holds genuine urgency to move its installed base to Cloud. This urgency creates negotiation leverage that enterprise customers can exploit—but only if they understand the discount structures available and how to combine them into a comprehensive renewal package.

The Three Pillars of Atlassian Loyalty Programs

Atlassian operates three distinct loyalty mechanisms, each with separate eligibility criteria and negotiation vectors:

1. Cloud Loyalty Discount: Direct credit applied to Cloud annual subscriptions for existing Data Center or Server customers
2. Atlassian Ascend Program: Enhanced discounts (10–20%) for customers committing to Cloud Enterprise before June 2027
3. Step-Up Credits: Pro-rated value of unused Data Center license applied toward new Cloud subscription costs

Understanding how these three systems interact—and how to stack them—is the foundation of effective Atlassian renewal negotiation. Most organizations capture only one discount tier; sophisticated buyers leverage all three in parallel.

Cloud Loyalty Discount: Eligibility and Limitations

The Cloud Loyalty Discount is Atlassian's formal recognition that migrating existing customers to Cloud should carry a pricing incentive. However, the program has strict guardrails that exclude many organizations and create negotiation friction if not addressed early.

Core Eligibility Requirements

To qualify for Cloud Loyalty Discount, your organization must meet all of the following conditions:

• Maintain an active Server or Data Center subscription for 1,001 or more named users
• Purchase an annual (not monthly) Cloud subscription; multi-year commitments are not currently available at list pricing with loyalty discounts applied
• Have purchased the original on-premise license before February 2, 2021—a threshold that excludes recent DC adopters
• Have an instance actively maintained OR expired within 30 days at time of Cloud subscription purchase
• Complete the free Cloud migration trial before finalizing the annual Cloud subscription purchase

Each requirement creates negotiation friction. Organizations that do not meet all five conditions are technically ineligible for the standard discount structure—but this does not mean discounts are unavailable. It means the negotiation moves into exception handling, where individual account teams have discretion to structure alternative arrangements.

The most common barrier we see is the "February 2, 2021 purchase date" requirement. Organizations that began their Server/DC journey after that date lack formal loyalty discount eligibility. However, the Data Center EOL creates sufficient business motivation for Atlassian to waive or restructure this threshold in exchange for committed annual Cloud subscriptions and multi-product bundling.

Step-Up Credit Calculation

If your Data Center license is expiring and you transition within the required window, Atlassian calculates a step-up credit based on the pro-rated value of unused on-premise license capacity. This is not a blanket discount—it is a mathematical credit applied to the Cloud invoice based on remaining value.

Example: A 2,500-user Data Center license costing $180,000 annually expires in six months. The pro-rated credit would be approximately $90,000, applied as a credit toward Cloud subscription costs. This significantly reduces the true cost of entry to Cloud for large organizations.

However, step-up credits are calculated on list prices, not negotiated prices. If your organization has a Data Center discount already negotiated, step-up credits are calculated on the original list value—not your negotiated rate. This creates an opportunity: organizations should prioritize securing step-up credit calculations before negotiating DC renewal discounts.

The Atlassian Ascend Program: June 2027 Deadline and Strategic Leverage

Atlassian's Ascend program represents the company's primary migration incentive mechanism. Customers committing to Cloud Enterprise licensing before June 30, 2027, are eligible for 10–20% loyalty discounts on annual Cloud subscriptions—above and beyond step-up credits.

Ascend Eligibility and Timeline

The Ascend program is open to organizations with active or recently expired (within 30 days) Data Center or Server subscriptions. Unlike the Cloud Loyalty Discount, Ascend does not have the February 2021 purchase date restriction, making it accessible to a broader set of existing customers.

The June 2027 deadline is not arbitrary. It reflects Atlassian's target for moving its largest installed base to Cloud. From a negotiation perspective, this deadline creates time-bound leverage: organizations have approximately 14 months (as of April 2026) to make migration decisions and secure Ascend pricing. Organizations that delay beyond this window lose access to 10–20% discounts regardless of other negotiation factors.

This is where engagement timing becomes critical. Organizations should initiate renewal and migration conversations 60–90 days before their Data Center license expiration, not 30 days prior. A 60–90 day runway allows time to evaluate migration logistics, negotiate dual licensing arrangements (running Cloud and DC in parallel during transition), and structure multi-year Cloud commitments that lock in favorable terms.

Dual Licensing Strategy During Migration

One of the most overlooked aspects of Atlassian migration strategy is the Dual Licensing Programme—the ability to run Cloud and Data Center in parallel during the migration window. This is not a workaround or exception; it is an officially supported configuration that organizations should actively structure into renewal agreements.

Why does this matter for discounts? Dual licensing creates three negotiation advantages:

1. Extended Transition Window: Organizations can run both systems in parallel for 6–12 months, reducing cutover risk and allowing gradual user migration. This justifies requesting longer step-up credit windows and extended renewal terms.
2. Reduced Cutover Risk: Atlassian account teams view dual licensing as a risk-mitigation strategy that increases Cloud adoption success. This risk reduction can be leveraged into better pricing concessions.
3. Multi-Product Bundling Opportunity: While running dual systems, organizations can negotiate bundled pricing across Jira, Confluence, Service Management, and other products. This bundling often yields 12–18% additional discounts beyond standard loyalty programs.

When negotiating renewal terms with your Atlassian account team, explicitly request dual licensing configuration support and include this in your multi-year agreement. Organizations that structure this proactively often secure 15–25% better pricing than those that negotiate renewals and migrations separately.

Enterprise Negotiation Context: Leverage and Benchmarks

Atlassian pricing is not fixed for organizations with meaningful scale. Atlassian publicly acknowledges that customers with 50+ users can negotiate with account teams. However, the negotiation leverage varies dramatically based on organization size and spending profile.

Spending-Based Leverage

• $203,964+ annual Atlassian spend (Large Enterprise): Meaningful negotiation leverage. Large enterprise organizations typically achieve 20–40% discounts below list pricing when combining loyalty programs, multi-year commitments, and multi-product bundling. This segment has legitimate alternatives (Jira alternatives exist, though Confluence has less direct competition) and Atlassian accounts prioritize retention.
• $170,283–$203,963 (Mid-Market Enterprise): Moderate leverage. This segment is attractive to Atlassian but competitive enough that you should expect 12–18% discounts below list with proper negotiation strategy. Organizations at this tier often have Data Center contracts with existing discounts; preserving those in Cloud transition is a key negotiation objective.
• $50,000–$170,282 (Growth/Scale): Limited leverage for direct pricing negotiation. However, Ascend program eligibility and step-up credits can still yield 20–30% total cost reduction. Multi-year commitments become more valuable at this tier.
• Below $50,000 (SMB): Loyalty program discounts and multi-year billing apply. Expect 14–20% savings from annual billing vs. monthly, plus loyalty discounts if eligible.

The critical insight: even SMB organizations can achieve meaningful savings if they structure negotiations properly around programs and commitment terms, rather than attempting direct price negotiation.

Multi-Year Commitments and Annual Billing Impact

Atlassian offers significant discounts for annual billing vs. monthly (14–20% savings) and for multi-year prepayment commitments. However, the Data Center end-of-life has created a structural change in renewal options:

• Data Center multi-year renewals: No longer available. As of 2025, Atlassian only offers annual renewal terms for Data Center—a policy shift that forces organizations to choose between accepting single-year renewal terms or accelerating Cloud migration.
• Cloud multi-year prepayment: Available, but typically at list pricing with loyalty discounts applied on top. Multi-year Cloud commitments are less common than they were for Data Center, partly because Cloud pricing changes are more frequent.

This creates a negotiation vector: organizations using single-year DC renewals as a bridge to Cloud can request price-hold guarantees or escalation caps as part of the annual renewal agreement. Organizations that stay on annual DC renewals through 2028 should explicitly negotiate maximum price escalation percentages (typically 5–8% per year is achievable) as part of their annual renewal terms.

Negotiation Positioning: The Five-Part Conversation Framework

Effective Atlassian loyalty discount negotiations follow a structured conversation framework that Atlassian account teams expect. Organizations that deviate from this framework often leave 10–15% on the table.

1. Establish Ascend Program Eligibility Early (Months 3–4 Before Renewal)

Confirm with your Atlassian account team whether your organization qualifies for Ascend. If you are ineligible due to purchase date or other factors, begin exception request process immediately. Atlassian account teams can waive Ascend eligibility restrictions in exchange for committed Cloud Enterprise annual subscriptions and bundled product adoption.

2. Calculate Step-Up Credit Value (Months 2–3 Before Renewal)

Request an explicit step-up credit calculation from Atlassian before finalizing any Cloud subscription terms. This should show: (1) current DC license value, (2) pro-rated unused capacity, (3) proposed Cloud subscription cost, and (4) credit applied. Do not proceed without this written calculation. Account teams sometimes optimize this value against their quarterly targets; pushing for explicit numbers forces transparency.

3. Structure Dual Licensing Terms (Months 1–2 Before Renewal)

If your organization plans any transition period, explicitly request dual licensing support in your renewal agreement. This should specify: (1) parallel licensing window (typically 6–12 months), (2) whether both systems remain fully supported, (3) how step-up credits are applied across the transition, and (4) what multi-product bundling applies during the dual period.

4. Negotiate Multi-Product Bundling and Expansion Rights (Months 1–2)

Organizations often operate Jira and Confluence separately or through different business units. Migration periods create opportunities to consolidate licensing and negotiate bundled pricing across the entire Atlassian portfolio. Atlassian often provides 12–18% additional discounts for bundled multi-product agreements vs. point-product renewals.

Additionally, secure expansion rights in your agreement. Enterprise customers should negotiate the right to add users at the negotiated rate (not list price) through the contract term. This is typically cost-free to request and valuable to lock in.

5. Agree on Contract Terms and Escalation Caps (Final Month Before Renewal)

Your final-month negotiation should lock in specific contract terms:

• Credit Overage Caps: If step-up credits exceed Cloud subscription costs, negotiate whether excess credits carry forward or are forfeited. Organizations should request carryover to subsequent years.
• Price Escalation Limits: For multi-year Cloud commitments, negotiate maximum annual price escalation (typically 5–8% per year). This limits surprise renewal increases.
• Marketplace App Discounts: Organizations using Atlassian Marketplace applications should negotiate whether Marketplace app costs are included in loyalty discounts or priced separately. Including them often yields 2–5% additional savings.
• Contract Term Flexibility: Lock in what happens if organization size changes (user count increases/decreases) during the term. Ensure expansion rights are not penalized with higher pricing.

Common Buyer Mistakes and How to Avoid Them

In working with enterprise organizations navigating Atlassian renewals, we consistently observe patterns of negotiation friction that could be avoided with better timing and positioning.

Mistake 1: Engaging Too Late (30 Days Before Renewal)

Organizations that initiate renewal discussions 30 days before expiration face compressed timelines and reduced negotiation leverage. Atlassian account teams operating under time pressure optimize for deal closure, not price. Begin engagement 60–90 days before renewal. This gives Atlassian time to model Ascend eligibility, calculate step-up credits, and structure dual licensing—all of which improve pricing outcomes.

Mistake 2: Not Leveraging Data Center EOL Urgency

Atlassian faces significant pressure to move installed customers from Data Center to Cloud. The Data Center end-of-life dates (March 2026 for new customer sales; March 2028 for expansions; March 2029 for read-only transition) create urgency on Atlassian's side that organizations often fail to capitalize on. During negotiations, explicitly reference the DC EOL timeline and position your Cloud migration as mutual benefit: Atlassian achieves its strategic migration goal, your organization achieves pricing concessions in exchange.

Mistake 3: Switching Partners Without Strategy

Organizations sometimes believe switching resellers or implementation partners during renewal will unlock additional discounts. In practice, switching resellers yields only 1–3% price reduction—far below what strategic program negotiation can achieve. Before switching partners, evaluate whether the current partner is adequately leveraging Ascend, step-up credits, and dual licensing. Poor negotiation positioning (not poor partner selection) is typically the actual problem.

Mistake 4: Not Bundling Products

Atlassian products are often deployed in business unit silos: Jira in Engineering, Confluence in multiple departments, Service Management in IT. Renewal periods create opportunities to consolidate under single contracts. Single-product renewals typically receive smaller discounts than bundled agreements. If your organization uses multiple Atlassian products, consolidate under one renewal negotiation and secure bundled pricing.

Mistake 5: Ignoring Rovo AI Licensing

Atlassian's new AI platform, Rovo AI, is available for Cloud customers and represents a new revenue stream for the company. Organizations implementing Rovo AI (for search, incident management automation, or other use cases) should negotiate Rovo AI costs as part of their Cloud agreement rather than as separate SKU. Bundling Rovo AI with Cloud commitments often yields better unit economics than pricing them separately.

For detailed guidance on Rovo AI cost negotiation, see our dedicated guide on Atlassian Rovo AI licensing cost negotiation.

Strategic Context: Understanding Atlassian's 2026 Positioning

To negotiate effectively with Atlassian, you must understand the company's strategic motivations. Atlassian's fiscal year ends July 31, and the company faces several key objectives that create pricing leverage:

• Cloud Migration Targets: Atlassian has publicly committed to shifting its revenue base toward Cloud. This means Data Center customers negotiating in 2026 have leverage; Atlassian will offer pricing concessions to accelerate migrations and meet fiscal targets.
• Data Center EOL Execution: Managing the transition of Data Center customers to Cloud without losing them to competitors (Jira alternatives, Confluence alternatives in specific verticals) is Atlassian's primary focus. Organizations with alternatives (or those threatening to evaluate them) have negotiation leverage.
• Isolated Cloud Launch (2026): Atlassian is launching Isolated Cloud for regulated industries (healthcare, government, financial services). Organizations in these sectors may have negotiation options Atlassian does not currently offer. This is worth mentioning if your organization has compliance requirements that single-tenant Cloud would address.

For comprehensive context on Atlassian's 2026 strategy and product roadmap, see our guide to Atlassian pricing changes 2026.

Mapping to Your Broader Renewal Strategy

Atlassian loyalty discounts don't exist in isolation. They are one component of a broader Cloud migration and infrastructure renewal strategy. Your organization should evaluate:

• Data Center EOL Timeline for Your Organization: When does your DC license expire? How does this align with the March 2026–2029 EOL timeline? This drives urgency and negotiation positioning.
• Migration Capability and Timeline: How long will your Cloud migration actually take? Can dual licensing support it? This determines whether step-up credits can be fully utilized or whether multiple renewal periods will be required.
• Multi-Cloud vs. Single-Cloud Architecture: Some organizations run Cloud in multiple regions or with multiple tenants. Loyalty discounts may apply to individual subscriptions; understand whether your architecture receives proportional discounts or negotiation adjustments.

For end-to-end Cloud migration planning, see the Atlassian Cloud migration guide for 2026. For contract negotiation specifics, see our resource on Atlassian Cloud contract negotiation.

The Broader Context: Enterprise Negotiation Principles

Atlassian loyalty discounts are most effective when positioned within an enterprise negotiation framework that extends beyond price. Understanding your organization's: (1) product usage depth, (2) competitive alternatives, (3) migration timeline, and (4) expansion plans—allows you to position loyalty discounts not as a discount request, but as a mutual value creation opportunity.

For organizations operating multiple Atlassian products or preparing multi-year Cloud migrations, consider whether a comprehensive enterprise licensing agreement (ELA) might provide better economics than loyalty discounts alone. ELAs typically include: fixed pricing, volume discounts, product expansion rights, and contract flexibility—often resulting in 25–35% total cost reduction vs. standard renewal terms.

Review the Atlassian enterprise negotiation and cloud pricing guide for more detail on enterprise licensing approaches.

Next Steps: Your Negotiation Timeline

If your organization's Data Center license expires within the next 14 months, the Ascend program deadline and step-up credit opportunities create a narrow window for strategic negotiation. We recommend:

1. Confirm Your Ascend Eligibility (This Month): Contact your Atlassian account team and request written confirmation of Ascend program eligibility. If ineligible, ask what conditions Atlassian would require to grant an exception.
2. Calculate Your Step-Up Credit Value (This Month): Request a written step-up credit calculation showing DC license value, pro-rated credit, and Cloud subscription cost. Do not proceed without this document.
3. Map Your Migration Timeline (Month 2): Determine realistic Cloud migration timeline. If longer than 6 months, plan dual licensing. If shorter, evaluate whether step-up credits fully offset Cloud onboarding.
4. Identify Multi-Product Bundling Opportunities (Month 2): List all Atlassian products your organization uses across departments. These become negotiation components.
5. Initiate Formal Negotiation (Month 3): 60–90 days before your DC license expiration, begin formal renewal discussion with your account team using the five-part conversation framework outlined above.

Organizations that follow this timeline typically achieve 25–35% total cost reduction (combining loyalty discounts, step-up credits, multi-product bundling, and multi-year annual billing). Organizations that negotiate ad-hoc or under time pressure typically see only 10–15% reduction.