Autodesk Perpetual License Rights: What You Actually Own

What Perpetual License Rights Actually Mean

When Autodesk sold perpetual licenses — primarily before 2021, though a limited number of industries received perpetual options until 2022 — the license grant was for the right to use a specific version of the software indefinitely. This is distinct from subscription licensing, where the usage right terminates if the subscription is not renewed.

A perpetual license from Autodesk provides three rights: the right to install the software on permitted machines, the right to use the licensed version indefinitely, and the right to access the software even after Autodesk's support for that version ends. What perpetual licensing did not provide — and this is critical for enterprises managing post-transition compliance — is the automatic right to use newer versions. Version upgrades required either active maintenance plan enrollment or a new license purchase.

The key documentation question is: what version were you licensed for, under what maintenance status, as of when? Enterprises that can answer this question with specific documentation — original order records, license certificates, maintenance plan history — are positioned to deploy and defend their perpetual position. Enterprises that cannot answer it are exposed to Autodesk's interpretation of their entitlement, which historically defaults to requiring subscription for any current version usage.

Maintenance Plan Status and Its Implications

Autodesk's maintenance plan — the annual subscription that provided perpetual license holders with access to new versions, updates, and technical support — was discontinued in August 2021. Maintenance plan holders were transitioned to subscription terms. Enterprises that allowed maintenance plans to lapse before 2021 hold perpetual continuation rights for the version they held at lapse, but do not have contractual rights to any version released after the maintenance lapse date.

The maintenance history creates a version entitlement boundary. An enterprise with a perpetual AutoCAD license purchased in 2018, with maintenance active through 2020, is entitled to AutoCAD 2020 or earlier — not AutoCAD 2021 or later. Running AutoCAD 2023 on a license with this maintenance history creates non-compliance exposure under Autodesk's version entitlement framework.

The practical challenge: many enterprises have lost the documentation trail that establishes their version entitlement boundary. Original order records from 2015 or earlier may not be readily accessible. Maintenance plan history may require Autodesk portal access or vendor records to reconstruct. Without this documentation, the enterprise cannot defend a perpetual license position against an audit that finds newer version usage against an older license.

Perpetual Scenario	Maintenance Status	Version Entitlement	Compliance Risk
Active maintenance through 2021 transition	Converted to subscription	Current version rights included in subscription	Low — subscription governs
Maintenance lapsed 2019–2021	Lapsed — no upgrade rights	Last version available at maintenance lapse date	High if running newer versions
Maintenance lapsed pre-2018	Lapsed — older version only	Version at lapse date only	Very High — likely running unsupported version
Perpetual license, no maintenance ever	None — version fixed at purchase	Licensed version only	High — any upgrade creates exposure
Legacy Collection or Suite perpetual	Varies by component product	Per-product version boundary applies	Medium-High — per product analysis required

Perpetual Licenses in Audit Proceedings

Perpetual licenses are a frequently contested area in Autodesk audit proceedings. Autodesk's LRT detects all installed software regardless of license type — it does not distinguish perpetual from subscription installations in its raw telemetry data. When the audit team sees installations of Autodesk products, the default position is to measure them against the current subscription entitlement. Perpetual continuation rights are not automatically recognized by the audit process; they must be asserted with documentation.

The audit finding challenge for perpetual licenses requires: original license certificates identifying the licensed version and seat count, maintenance plan records establishing the version entitlement boundary, ITAM records showing that the installed version falls within the perpetual entitlement (i.e., the version at or before the maintenance lapse date), and evidence that the perpetual installation is not being used for access to features only available in subscription versions.

This challenge is technically well-founded and accepted by Autodesk's compliance team when documentation is complete. Our data shows that 72% of perpetual overlap challenges succeed when supported by original license documentation. The challenge failure rate — 28% — is almost entirely attributable to missing documentation rather than invalid entitlement claims. This makes documentation preservation the highest-priority action for enterprises retaining perpetual license portfolios.

For the full audit findings challenge methodology, including perpetual overlap as one of the five contestable finding categories, the audit findings challenge article provides the complete framework. The Audit Playbook white paper includes the specific documentation checklist for perpetual license challenge submissions.

Perpetual Licenses as Negotiation Leverage

Beyond compliance management, a well-documented perpetual license portfolio provides commercial leverage in subscription negotiations. The perpetual license represents a demonstrated ability to continue using the software without a subscription — and Autodesk's commercial team knows it. The question for Autodesk's account team is not whether the enterprise can be forced to subscribe (it cannot be forced for perpetual-covered versions), but whether the subscription value proposition justifies a transition at a price the enterprise finds commercially reasonable.

This leverage dynamic is most powerful in three commercial scenarios. First, when the perpetual portfolio covers the core products the enterprise relies on — if 70% of usage is on perpetual-covered versions, the subscription urgency is limited to the remaining 30% plus new version access. Second, when the enterprise's perpetual licenses are for widely-deployed, workflow-critical products like AutoCAD or Revit — these create maximum leverage because the disruption cost of losing access is highest. Third, when the enterprise is evaluating a multi-year subscription commitment or EBA — the perpetual continuation right creates a genuine walk-away alternative that the account team must price competitively to overcome.

Enterprises that have never catalogued their perpetual license holdings cannot deploy this leverage because they cannot quantify the walk-away position. A perpetual license inventory — conducted before any renewal or EBA negotiation — is a commercial preparation step as important as discount benchmark research. The license negotiations advisory service includes perpetual license inventory and leverage quantification as a standard component of renewal preparation.

Documentation Preservation: The Critical Action

The most consequential action an enterprise with perpetual licenses can take is documenting and preserving the license records that establish entitlement. This documentation loses value over time as personnel change, records migrate across systems, and the institutional memory of pre-subscription procurement fades. Taking action now — while the records are still accessible — is the difference between a defensible perpetual position and an undocumentable one.

The documentation package for each perpetual product should include: the original purchase order and invoice, the license certificate or serial number confirmation, the maintenance plan history (if any), and the version available at the maintenance lapse date. This package should be stored in a contract management system with document retention settings that preserve it beyond typical seven-year financial record retention periods — perpetual license rights have no expiration, so the documentation must be preserved indefinitely.

Perpetual Migration Strategy and Compliance

For enterprises planning to migrate remaining perpetual users to subscription — whether proactively or under commercial pressure from Autodesk's subscription push — the migration process itself creates a compliance risk window that requires specific management.

The migration creates potential for concurrent usage of perpetual and subscription versions during the transition period. If the transition is not managed carefully — with a defined cutover date and formal documentation of the perpetual license retirement — LRT may detect both versions simultaneously and report apparent dual-deployment. This is one of the most common audit findings for recently-migrated enterprises, and it is addressable with documentation but requires the documentation to exist.

The migration strategy should include: a formal perpetual license retirement record (specifying which licenses are being retired, the retirement date, and the subscription activation they are being replaced by), a managed deployment cutover rather than an unmanaged parallel running period, and ITAM records confirming that perpetual version installations have been removed from the environment. These three records provide the complete challenge documentation if a post-migration audit raises perpetual overlap findings.

The complete licensing models guide provides the full context for perpetual licensing within the broader Autodesk model landscape, including the compliance pitfalls specific to enterprises in different stages of the perpetual-to-subscription transition.