Dual licensing for Atlassian Cloud migrations done right

Keep Server/Data Center running while setting up Cloud, without security gaps or budget shocks. Get clear dates, costs, and audit coverage.

Atlassian dual licensing hero infographic

you can trust our experts

Dual licensing support backed by Atlassian certifications


Recognition and expertise:
Double Platinum Partner (Solution and Marketplace)
Finalist for Atlassian Partner of the Year 2024–2025 (Emerging Markets)
Extensive experience with Jira, Confluence, Jira Service Management, and Assets
50+ Atlassian-certified professionals across all key products
Comprehensive support ecosystem:
Full-service offering covering audits, licensing, implementations, migrations, integrations, and custom app development
22,500+ app installations on the Atlassian Marketplace
More than 11 million end users supported globally

Atlassian Dual Licensing: what we do for you

Dual licensing tasks we own


Plan a license overlap window
Define the exact overlap period, seat tiers, and milestones to ensure teams can continue working during the move.
Set a hard budget cap with exit triggers to prevent the overlap from drifting (and costs from creeping).
Align Cloud contract terms
Co-term Cloud start/end dates to your fiscal calendar and legacy renewals to reduce off-cycle spend.
Create a seat-down plan tied to migration waves to avoid double payment for the same users.
Procure and activate temporary licenses
Source the right mix of Cloud + Server/DC entitlements, trials, and short-term tiers for pilots.
Manage app licensing (trial extensions, dual terms, co-terming) and ensure user counts stay compliant.
Support test and pilot phases
Set up sandboxes and staging with the correct license coverage, including test users and service accounts.
Document who can access what, for how long, so QA and UAT run smoothly and pass audit checks.
Track usage and milestones
Monitor adoption by group/project; cut Server/DC seats as soon as teams switch to Cloud.
Issue monthly variance reports (plan vs. actual) and update the overlap plan to keep spending on target.
Decommission legacy licenses
Time-box final shutdown, revoke keys, and remove access to avoid accidental overuse after cutover.
Provide a close-out pack: license inventory, dates, approvals, and proof of decommission for auditors.

The value our clients get from Atlassian double licensing

What we hand over

Logo image

Predictable overlap costs with an agreed ceiling and exit plan

A fixed cost cap with clear “reduce or end” triggers by date and adoption level. Monthly plan vs. actual report so finance sees no surprises.
Logo image

No audit gaps: entitlements mapped to environments, users, and dates

One entitlement map linking each instance, user group, and time window. Evidence pack: keys, approvals, and change logs ready for auditors.
Logo image

Zero “license stops work” moments during migration testing and cutover

Pre-cutover checks to confirm seats, apps, and access for all pilots. Fallback coverage for rollbacks or extended testing windows.
Logo image

Contract dates aligned to your fiscal calendar; fewer off-cycle renewals

Co-termed end dates across Cloud, Server/DC, and key apps. Renewal rhythm moved to quarter- or year-end to simplify budgeting.
Logo image

Marketplace apps covered with the right terms (trial/dual, co-terming)

Correct trial extensions or dual entitlements for test and prod. App renewals synced to primary contracts to avoid double-pay.
Logo image

Seamless handover assurance: every transition step documented and accountable

Named owners for each migration phase with sign-off checkpoints. Shared progress log so everyone sees what’s done, pending, or at risk.
atlassian dual licensing: process
Your path from plan to cutover
Assessment
  • Review contracts, renewals, user counts, and app list; flag risks and deadlines.
  • Gather inputs (quotes, instances, admins) and map them to the migration plan.
Overlap plan
  • Define Cloud + Server/DC mix, seat tiers, start/end dates, and milestones.
  • Set budget ceiling, exit triggers, and seat-down schedule by migration wave.

Procurement & co-terming
  • Secure licenses, trials, and app entitlements; line up purchase approvals.
  • Align end dates across products and apps to your fiscal calendar.
Activation & tracking
  • Turn on keys/instances; set sandbox/staging access and service accounts.
  • Track adoption vs. plan; publish monthly variance and actions.
Cutover & decommission
  • Execute time-boxed cutover; reduce legacy seats as teams move.
  • Revoke keys, remove access, and log changes to prevent overuse.
Close-out pack
  • Deliver the entitlement map, dates, costs, and approvals for audit.
  • Confirm renewals cadence and hand over the runbook for future changes.

Contact us about Atlassian dual licensing

Book a free consultation about dual licensing at your company


Book a consultation

We will reply in 24 hours with detailed information. Our expert will invite you for a meeting (or e-mail you) to determine the exact scope of your needs.

Call our consultant

Consultant image

Katarzyna Dorosz-Żurkowska

Head of Atlassian Services

Our consultant is at your disposal for any additional questions.

FAQ about Atlassian dual licensing

  • Do I need to pay double for Cloud and Server/Data Center during migration?

    No, that’s the whole point of dual licensing done right. We define an exact overlap window with a hard cost ceiling and exit triggers tied to adoption milestones. As soon as teams switch to Cloud, Server/DC seats are reduced, so you’re not paying twice for the same users. You’ll also receive monthly variance reports so finance can see where every dollar goes.

  • How do you handle Marketplace app licenses during the overlap?

    We coordinate all app entitlements so you stay covered without overspending. That means extending trials, setting up dual terms where needed, and aligning renewals to your primary Cloud and Server/DC contracts. Every app is mapped to the right environment, user group, and timeline, so there’s no confusion, no double payment, and no missing license during testing.

  • What happens if my migration takes longer than planned?

    Your dual licensing plan includes fallback coverage for extended testing or rollback scenarios. If a pilot or cutover phase needs extra time, you stay licensed and compliant throughout. We simply update the overlap plan, adjust seat counts, and document all changes, no scrambling for emergency renewals, no service interruptions.

  • Will auditors accept the dual-licensing setup?

    Yes. Every plan we hand over includes a complete evidence pack with an entitlement map, approval logs, keys, and timestamps. It shows exactly who had access to what, when, and under which contract. That documentation satisfies Atlassian’s compliance standards and makes your internal or external audits straightforward.

  • How do I know when to turn off Server/Data Center license?

    We track usage and adoption by team and project to identify when Server/DC access can safely be removed. Once the final cutover happens, we time-box the shutdown, revoke keys, and produce a decommission report that confirms completion. You’ll have clear proof for finance and audit (and peace of mind knowing no unused legacy licenses are left behind).

  • Do you have security/compliance documentation we can use for vendor due diligence (audits, certifications, privacy)?

    Yes. Deviniti’s Trust Center provides downloadable security and compliance documentation for vendor due diligence, including:

    • ISO/IEC 27001 certificate (ISMS)
    • ISO/IEC 27017 certificate (cloud security controls guidance)
    • SOC 2 Type 1 report
    • Privacy & Security Overview
    • CAIQ Lite – Apps (Cloud Security Alliance questionnaire)
    • Cloud Hosting Locations & Data Residency Options
    • Information Security Policy (AUP)

    For GDPR due diligence, Deviniti provides a Data Processing Agreement (DPA) under GDPR Article 28. As a general rule, personal data processing takes place within the EU/EEA. Where international transfers are necessary, Deviniti uses lawful transfer mechanisms (e.g., EU adequacy decisions and Standard Contractual Clauses) with additional safeguards. For products that support it, you can also choose service delivery exclusively via infrastructure located in the EEA.