Solution:
The Basics
Vault Server can only be upgraded and migrated two releases at a time. As an example, Vault 2023 can only be migrated forwards to 2024 or 2025. The Vault database is migrated when the ADMS (Autodesk Data Management Server) console is opened and the Administrator logs in.
The CAD Add-ons are installed from the Vault client and match their year version. As an example, AutoCAD 2023 must have Vault Client 2023 installed to use the Vault Add-in. Vault Clients must match the Vault server version.
To avoid downtime always:
-
Test the migration beforehand (for example to determine timeframe needed to complete migration process).
-
Prepare a plan for completing it or rolling back.
-
When moving a Vault Backup folder always zip up the folder.
-
Install the new version on a test system and restore a backup there.
Consider that Vault contains all your company's design data. Vault has an immensely strong track record for upgrading to a newer release with no problems whatsoever. But plan for the worst-case scenario. Never upgrade without first having a full Autodesk Data Management Server (ADMS) Console backup that can be restored to a test environment, first. Restoring your ADMS Console backup to a test server, validates the backup is good and provides a safety net backup server should something go wrong.
The Details
If migrating and upgrading Vault was not done yet in past. It is best to start with
How to plan an Autodesk Vault Migration lesson [23 minutes].
There are different aspects to an upgrade, resulting in information being separated into different areas. The best practice recommendations from Autodesk regarding upgrading Microsoft SQL Server and Autodesk Vault are documented. See
Vault 2025 Help | Upgrade Autodesk Vault.
Note: Vault does not include SQL server licenses and installs SQL Express (a free edition of SQL). Licensed versions of SQL must be purchased separately.
Upgrading a full SQL replicated environment
Upgrading a fully SQL-replicated environment can present extra challenges. The steps required can be found in these articles:
Specifically for migration to Vault 2022 and later. See Autodesk Vaults Underlying SQL Replication Technology Changes in Vault Professional 2022.
Guidance for migrating Inventor data
See Inventor 2025 Help | Data Migration.
If, after reviewing all sections/phases in the Vault's online help. See Vault 2025 Help | Introduction to Upgrading Vault.
Confidence is not high that the process can be completed successfully or unaided. Consider contacting Autodesk Vault reseller for help.
- Upgrading a business-critical service such as Vault can be an anxious time, especially considering that a company's intellectual property has been entrusted to it.
- Autodesk resellers are by far, the most experienced in the practicalities of upgrading Vault environments for their customers and can carry out the process proactively, professionally, and with minimal impact on production.
After upgrading Vault, check if content center libraries need to be upgraded as well. See How to install and configure content center libraries for use with Vault.
Autodesk Support is here to assist you should you encounter any technical issues during migration or upgrade.
Our role is primarily troubleshooting, stepping in to resolve issues as they arise. However, it's important to clarify some common misconceptions about the level of service we provide during a Vault upgrade. These include
- Autodesk Support cannot be used as a consulting service. Your Autodesk reseller can provide this service.
- Should any issues arise, Autodesk Support is always ready to provide guidance and help troubleshoot. However, while we're here to assist you every step of the way, we are unable to perform the upgrade/installation process on behalf of customers.
- Autodesk Support cannot be "booked" or reserved, when your upgrade is performed. Find an Autodesk reseller that can provide this service. Autodesk Support needs to remain reactive and available (at short notice) to customers faced with unexpected production stop scenarios.
- Autodesk Support is available Monday to Friday during your local business hours and does not operate at weekends. If you need this level of service, we would recommend contacting your reseller.
If your current reseller cannot provide any of the previous services, find one that can, in the Autodesk Partner Finder or Autodesk Customer Success Hub.
Migrating Vaults from older, no longer supported versions
Be aware of the Product Support Lifecycle and How to download older updates for Autodesk software.
"Support, including technical support, software updates, and hotfixes, is only provided for the three previous releases listed" in the "Eligible previous versions - subscriptions" page. Migrations from releases earlier than that listed are not supported.
- Autodesk cannot provide versions of software that are not listed in the Product Support Lifecycle page. Nor can it provide access to obsolete software updates. It is possible that an Autodesk reseller may have retained old copies.
- If reseller cannot provide any older versions of the software, find one that can, in the Autodesk Partner Finder.
If you encounter difficulties in obtaining unsupported versions of the software, or if unresolved technical issues occur during data migration, consider these two options.
- Use Get Latest on the root of the Vault Explorer folder, to locally get the tip iteration of each vaulted file. Then use Autoloader to upload the old data into a new Vault. (Note: It might be necessary to migrate the CAD files themselves before using Autoloader).
- Maintain the old Vault Server, creating a new, current Vault Server. Getting the files from the old server on an "as needed" basis, before adding them to the current Vault Server.
How to access older versions of Autodesk Applications?
Preparation and familiarity with the process are the keys to success
Preparation and familiarity with the upgrade process are mandatory and critical. Do not upgrade a production environment unprepared. This is true for single users or a corporate enterprise. Set up a test environment, separate from production, and go through the process before doing it live. Virtualization solutions such as VMWare or Hyper-V are great tools for this.
- Understand how long each phase will take.
- Document every step needed with screenshots and text.
- Document any problems encountered and also the solutions.
- Once the database has been migrated, test business-critical workflows, add-ons, and customizations.
- Think of the worst that can happen and build a plan for it.
- It is not intended to sound contrite, but do not hope everything will go smoothly, "hope" is not a good business strategy. "Know" it will go smoothly. The only way to know it will go smoothly is through a trial run.
