How an Autodesk subscription compares with a perpetual license

The choice facing a design department is framed a little inaccurately. You can no longer buy a new perpetual license for most Autodesk products from the manufacturer. Current access options center on subscriptions and Flex. The honest comparison is therefore between buying three named-user subscription seats and continuing to use three perpetual licenses that the company legally acquired in the past.

If the old licenses are paid for, activated on suitable workstations, and do not need to be moved, they almost always win on direct payments over the next five years. Yet a zero license bill does not mean zero cost. A replaced computer, an unsupported operating system, a client's newer project format, an incompatible add-on, or an inability to reactivate can turn those savings into a departmental shutdown.

A subscription costs more in the quiet scenario, but it buys manageable access: current versions, some previous versions, updates, fixes, and the ability to assign a vacated seat to another employee through an account. It does not allow three people to share one seat, and it does not preserve working access after payments finally stop.

The decision requires two calculations. The first shows payments to the supplier over five years. The second estimates the cost of keeping the old software environment alive and the consequences if it fails. As long as these figures sit in separate spreadsheets, a perpetual license looks free and a subscription looks like simple rent. Both estimates are incomplete.

You can no longer buy a new Autodesk perpetual license

Autodesk classifies perpetual licenses, serial number licenses, and multi-user network options as retired access types. Its official end-of-sales notice says that new perpetual licenses for individual products stopped being sold on January 31, 2016. The manufacturer now describes a subscription as named access for a defined term, while Flex charges for use through prepaid tokens.

This does not cancel the right to use a legally acquired perpetual license. Autodesk Product Support Lifecycle says that the owner of such a license may use it for as long as they want. The next sentence in the same document changes the practical meaning of that right: for a version that has reached the end of support, Autodesk will not provide a new activation code to reactivate it on another device. That version will not receive updates or hotfixes either.

A department must therefore separate three situations that people often call the same purchase. In the first, the company already owns a license, can locate its agreement and proof of entitlement, and has the software working on the current computer. In the second, the company is moving an old license to another computer or changing the legal entity. In the third, a reseller offers a new Autodesk perpetual license today. These cases carry different risks.

You cannot treat a reseller's offer like an ordinary boxed-software purchase. First request the agreement number, access type, permitted territory, ownership history, and written confirmation that the transfer is allowed. Autodesk General Terms require consent to transfer rights and obligations to another organization. A seller's invoice alone does not prove that the manufacturer recognizes the new user. Without confirmation, the department is buying a dispute rather than perpetual access, and that dispute will surface during the first audit or activation.

A new department has no practical choice between a new subscription and a new perpetual license. A department with an old license estate does have a choice, but the objects being compared must be named precisely: future subscription payments versus the cost and risk of running an already purchased version.

Three permanent designers need three named seats

One subscription seat is assigned to one authorized user with a unique Autodesk ID. Autodesk states directly in its user-management guidance that two people cannot use the same seat and that account credentials must not be passed to colleagues. If three designers regularly open the software, budget for three seats even when they work different shifts or rarely run demanding functions at the same time.

An administrator can unassign a seat from an employee who has left and give it to a new one. That is a normal staffing operation, not a way to pass one seat among engineers every day according to a schedule. The Single User terms require the seat to be assigned to the person who actually accesses the software. Reassignment solves a resignation, several months of leave, or a move to another department. It does not turn a named subscription into a floating network license.

Before calculating, list people rather than computers and record how each person works:

• employees who need the software on most working days;
• managers and reviewers who only need a viewer or an agreed export;
• temporary contributors with clear project start and end dates;
• occasional users for whom the economics of Flex deserve a separate check;
• external contractors whose licensing responsibility must be stated in the contract.

This list often reduces the purchase without breaking the rules. A department head who only reviews finished files and adds comments in an agreed format, for example, may not need a full seat. If that person edits the model once a week, however, infrequent use does not permit them to use a designer's account.

Do not count installed copies. One employee may work on permitted devices within the terms for the specific product, but that does not create another user. Conversely, three workstations do not prove a need for three seats if the same assigned specialist uses them in sequence. The unit of calculation remains the person with actual access.

Use quotations, not memory, for a five-year subscription total

The budget needs a current commercial quotation for the specific product, territory, and term, not a price copied from last year's email or a foreign web page. Let A be the annual cost of one seat including all applicable taxes and charges. If the price does not change, three seats for five years cost 15A. This is the baseline against which the other scenarios are compared.

If finance assumes annual price growth g, calculate the total as 3A × ((1 + g)^5 - 1) / g. When g = 0, use the simple 15A formula. Calculate a multi-year agreement according to its payment schedule rather than assuming the price is frozen. The quotation or contract must state any price commitment.

The figures below demonstrate the method and are not a market price. Suppose a supplier quotes 1,000,000 tenge for one seat in the first year, and the budget scenario assumes 5 percent annual growth.

1. In year one, one seat costs 1,000,000 tenge and three seats cost 3,000,000 tenge.
2. In year two, one seat costs 1,050,000 tenge and three seats cost 3,150,000 tenge.
3. In year three, one seat costs 1,102,500 tenge and three seats cost 3,307,500 tenge.
4. In year four, one seat costs 1,157,625 tenge and three seats cost 3,472,875 tenge.
5. In year five, one seat costs 1,215,506 tenge and three seats cost 3,646,519 tenge. The total is 16,576,894 tenge.

With no growth, the same starting figures would produce 15,000,000 tenge. The difference of 1,576,894 tenge shows why procurement needs a price-change scenario, although no one should present the assumed 5 percent as an Autodesk forecast. Replace A, g, and the taxes with values from your quotation. If the offer is issued in another currency, add a separate exchange-rate scenario instead of hiding currency risk in a footnote.

The payment table also needs costs that easily disappear between budgets: implementation services, training for a version change, paid add-ons, product-specific cloud limits, and administrator time. Include them only when they appear in the offer or your work plan. Do not attribute separately sold capabilities to a standard subscription.

Model headcount changes separately. If the third designer leaves halfway through a paid year, do not record half a seat as an immediate saving. Whether and when the quantity can be reduced depends on the term, product, region, and renewal status. Until the supplier confirms a refund or adjustment, cash flow retains the full payment for the current period. If a new employee starts in two months, record the exact date when a seat must be added and check how the supplier will align its term with the other subscriptions.

A finance director should see an annual schedule, not only one final total. A subscription creates a recurring payment and preserves the choice not to buy the next term. An old license creates no payment to the manufacturer, but a major workstation replacement or emergency recovery can cause a large one-off expense at an awkward time. Discounting cash flows is reasonable if the company uses it for all investment decisions, but the discount rate must not conceal technical risk. Show nominal payments, present value, and the largest single cash requirement on separate lines.

Do not choose an option solely by whether accounting calls it operating or capital expenditure. The accounting treatment depends on the contract and company policy, while the department's ability to work does not change with that label. Compare access rights and failure scenarios first, then give the agreement to accounting for classification.

It helps to request three comparable options: three annual seats, an available multi-year term, and a mixed arrangement with subscriptions for permanent users and Flex for occasional users. Product, edition, territory, taxes, support level, and start date must match across all options. Otherwise, the spreadsheet compares different goods.

A perpetual license is cheap only in a stable environment

For an already paid perpetual license, the historical purchase price does not belong in a decision about the next five years. It is a sunk cost. The calculation includes the money and working time required from today onward to keep the old version delivering projects.

A useful model is Kp = M + I + D + C. M covers migration and reactivation, I covers support for the old software environment, D is downtime cost, and C is compatibility expenditure. Compare Kp with 15A or with the price-growth total. Do not force every risk into an exact tenge amount. A range based on honest assumptions is better than false precision.

For M, list planned replacements of the three workstations over five years and verify whether the specific version can be activated after each replacement. For I, count administrator hours spent preserving a compatible operating system, drivers, installers, patches, and add-ons. For D, multiply the likely hours of a full or partial stop by the department's hourly cost. For C, estimate file conversion, a separate workstation for old projects, and repeated model checks after exchanges with clients.

A break-even test is simpler than a long forecast. If three subscription seats cost 15A over five years at the current quote, the old estate saves money while future M + I + D + C remains below 15A. Then test a hard constraint: can the department tolerate even one failure lasting as long as it takes to restore the license or environment? A company may accept an average expected cost yet still be unable to accept a one-week shutdown under its client contract.

Run one recovery test day before approving the five-year plan. Use a spare workstation, a clean drive, and a copy of a real completed project. The administrator must deploy an acceptable system, install and activate the software and add-ons, open the project, recalculate it, and produce a control output set. Measure the time to a result a designer is willing to approve, not the time needed to copy an image. If the test stalls on a missing installer, incompatible driver, or rejected activation, you have found a specific Kp item rather than an abstract risk.

The test also reveals dependence on one specialist. Have another employee repeat the procedure from the instructions. If that person cannot find the agreement, image, or add-on settings without spoken guidance, add documentation time and a second verification to the plan. This work costs less than an emergency search and is necessary under either licensing model.

The most common mistake is setting D to zero because no serious shutdown has happened yet. That conclusion does not follow from a quiet history. Use a concrete failure rather than an abstract probability: the system drive dies two days before documentation is due, the new computer refuses the old activation, and source files open only in the old version with one specific add-on. Record who restores service, where the installer is stored, which computer becomes the spare, and how long the result check will take.

If a test confirms those answers, a perpetual license can remain sensible for stable archival projects. If the answers exist only in one system administrator's memory, risk cost is already above zero even though accounting has not received an invoice.

Updates buy compatibility but still demand discipline

An active subscription provides access to the current version and to certain previous versions shown in Autodesk Account under Previous Version Rights. Supported versions receive technical support, updates, and fixes within the product's rules. This reduces the chance of being trapped on an unsupported build, but it does not mean the department must install every release on publication day.

A design environment contains more than the application itself. It includes templates, part libraries, add-ons, fonts, printers, drivers, macros, naming rules, and client requirements. An update that has not been tested against this whole setup can stop document production just as effectively as an obsolete version.

Set aside a validation workstation and run four project types on it: a current typical project, the heaviest one, an archived project, and a file received from an external partner. Test opening, recalculation, printing, export, add-ons, and the return transfer of the file. A successful application launch does not prove that the production environment is ready.

A perpetual version offers another kind of predictability: its interface and behavior do not change. The department pays for that stability with a shrinking compatibility envelope. The operating-system vendor ends support for an old release, a graphics-card supplier changes a driver, the client moves to a newer version, or an add-on developer stops building for the old application. Any one of these links may force the company to keep a frozen computer or convert data manually.

Never updating sounds cautious because it rules out a failure caused by the update itself. For an active department, it is the wrong policy. A sound policy separates projects: long-running active projects may stay on an approved version until a control point, new projects start on a tested supported version, and archives open in an isolated environment. A subscription makes that policy possible, but an administrator still has to define the versions and transition dates.

Moving a seat between people does not create shared access

A subscription seat can be reassigned when the department's staff changes. An administrator manages access by user, product, or group in Autodesk Account. Changes generally take effect immediately, although the user may need to sign out and back in. This is much easier than moving an old activation between computers, but the operation should leave a clear record.

A working procedure takes five actions:

1. The manager confirms the former employee's access end date and the owner of that person's project files.
2. The administrator unassigns the product from the former Autodesk ID.
3. The new employee receives an individual Autodesk ID at a work address, not another person's password.
4. The administrator assigns the free seat and verifies sign-in on the prepared workstation.
5. The user, seat, product, and date are entered in the license register.

This transfer fits a departure, a new hire, a long-term role change, or the end of a contractor's project. It does not fit daily sharing of one seat among three employees. Constant rotation also breaks accountability beyond the license issue: a log identifies the account, not the person who actually made a change.

For a perpetual license, the word transfer may describe an entirely different operation. Assigning it to a new employee within the same organization, moving the installation to another computer, and transferring the license to another legal entity must not be mixed together. Check the agreement, version, support status, and new-activation path before any change. Do not remove a working activated installation until the recovery route is confirmed.

A register for three seats can be simple. It needs the rights holder, product and version, access type, subscription or agreement identifier, assigned user, workstation, end date, administrator, and location of proof documents. One completed register is more useful than a folder of screenshots with no connection between people and entitlements.

The application and files behave differently after payments stop

Ending a subscription does not transfer ownership of completed projects to Autodesk. The General Terms explicitly leave rights to files, models, and other materials with the customer. Yet the right to own a file is different from the right to keep editing it in paid software.

Autodesk renewal guidance describes the stages after nonpayment: a subscription moves from Expired to Suspended and then to Cancelled. Product access is removed at the Suspended stage. Timing and the possibility of recovery depend on the subscription type and purchase terms, so a design department must not base continuity on a grace period. Treat the end date in Autodesk Account as the working payment deadline.

Local project files remain on their drives. Autodesk says that some files can continue to be viewed with the free Autodesk Viewer, but not every file and format is supported. Access to cloud storage included with a subscription may end after a period that varies by product. The phrase the files are not going anywhere is therefore too vague for an exit plan.

Before deciding not to renew, the department should complete five checks:

• export local copies of all project data and related materials;
• preserve deliverables in their native format and in the agreed exchange format;
• test file opening with an independent viewer or approved archive environment;
• record the application and add-on versions used to issue the documentation;
• appoint an archive owner and perform a trial project recovery.

If payment fails by accident, service depends on the speed of procurement, the bank, the partner, and the account administrator. Auto-renewal reduces part of the risk but does not replace control. A payment method can expire, a limit can be exceeded, and a notice can go to someone who has left the company. Schedule status and contact checks 90, 45, and 15 days before expiry. These are internal control points, not Autodesk-promised grace periods.

A perpetual license does not depend on an annual payment, but it does depend on preservation of the activated environment. Its exit plan becomes a recovery plan: a backup system image, tested hardware, installation materials, essential add-ons, and a documented startup procedure. A disk image without a trial restoration provides only the appearance of readiness.

The department's project model should decide

For a new design department with three permanent users, the workable option will usually be three named subscriptions. The manufacturer does not offer a new recognized perpetual license, while replacing it with a questionable transfer of old rights adds legal and operating risk. Budget 15A over five years with an unchanged price and add a separate growth scenario.

For a department with three lawful perpetual licenses, the answer depends on the environment. Keeping the old version is justified when projects do not require new formats, workstations can be maintained, activation is already complete, add-ons are preserved, and recovery has been tested. This arrangement is especially suitable for an archive and for a long project with a fixed version.

A mixed option often fits better than a binary choice. The current team receives subscriptions for new projects and exchanges with partners, while an isolated old installation remains available for the archive. This does not reduce the subscription count for three active users, but it avoids migrating every historical project without a business reason.

Before procurement, approve a one-page decision with four blocks:

• a quote for three named seats stating the product, term, taxes, and renewal conditions;
• a five-year calculation with no price growth and with the approved finance scenario;
• a map of versions, add-ons, formats, and requirements for active projects;
• a tested operating plan for an activation failure or subscription termination.

GSE sells and integrates Autodesk software, so the integrator can be asked for a comparable configuration together with workstation and support requirements, without mixing those costs into the license price.

Do not approve an option whose savings depend entirely on an old computer never failing, and do not buy a subscription only for the word updates. Record A, the three actual users, the controlled version for each project, and the maximum tolerable downtime. The decision then stops being an argument about owning software and becomes a testable departmental budget.