How To Upgrade SolidWorks: The Definitive Enterprise Migration Guide

Upgrading SolidWorks requires a methodical synchronization of client installations, administrative image servers, and Product Data Management (PDM) vaults to prevent data corruption and version mismatch errors. Maintaining continuity across engineering teams demands meticulous pre-planning, validation of hardware compliance with certified graphics drivers, and adherence to strict database backup protocols.

Pre-Operation & Equipment Checklist

Transitioning to a new major release of SolidWorks involves more than simply running an installation executable; it requires an evaluation of your entire engineering infrastructure. Workstation hardware must meet or exceed the Certified Graphics Card requirements specified by Dassault Systèmes for the target year release. Ensure that your operating system meets the minimum build standards, as newer iterations of SolidWorks drop support for older Windows versions.

• Essential Tools & Software: Administrative permissions on all target machines, SolidWorks Installation Manager, active SolidWorks Subscription Service credentials for license access, and a dedicated network share for administrative images.
• Prerequisite Knowledge & Standards: Familiarity with your organization's PDM vault architecture, knowledge of active client serial numbers, and a clear understanding of your current license activation model (Standalone vs. SolidNetWork License Manager).
• Duration & Budget Benchmarks: Allocate 2 to 4 hours per workstation for clean installs and client testing, and up to 8 hours for server-side PDM and SolidNetWork License (SNL) upgrades. Ensure maintenance contracts are renewed to avoid licensing downtime costs.

Step-by-Step SolidWorks Upgrade Workflow

Step 1: Backup and Vault Data Preservation

Before initiating any installation routines, safeguard all existing engineering data, custom templates, design libraries, and database configurations. If your organization utilizes SolidWorks PDM, perform a full SQL database backup alongside an archive server backup. For standalone or network users, manually copy custom drawing templates, weldment profiles, and macro directories to an isolated backup location outside the default installation paths.

Warning: Never attempt an upgrade directly over an existing major release without backing up your active vault database. Failure to secure an up-to-date SQL backup risks permanent data loss if the database schema migration encounters a conflict.

Step 2: Upgrade the SolidNetWork License (SNL) Manager

If your organization utilizes floating network licenses, the license server must be upgraded before any client machines are updated. Uninstall the existing SolidNetWork License Manager or use the Installation Manager to perform an upgrade on the license server host. Input your updated serial number, activate the new licenses over the internet or via email, and verify that the Dassault Systèmes SolidWorks License Server service is running smoothly in Windows Services.

Pro-Tip: Always verify TCP/IP port communications (ports 25734 and 25735 by default) through your organization's firewall rules before and after upgrading the SNL manager to prevent client checkout timeouts.

Step 3: Deploy or Update Administrative Images

For multi-user environments, creating or updating an administrative image via the SolidWorks Installation Manager ensures uniform deployment across all engineering workstations. Extract the installation files, modify the deployment options to include your company's specific add-ins, toolsets, and file locations, and push the installation package via group policy or local execution scripts. Test the administrative image on a single pilot machine before mass deployment across the enterprise.

Step 4: Execute Client Workstation Installations

On individual client machines, run the SolidWorks Installation Manager or execute the setup from your administrative image share. Choose the option to upgrade existing major versions or perform a clean installation if transitioning across multiple release years. Ensure that third-party add-ins such as CAMWorks, DraftSight, or FEA packages are compatible with the new major release before initiating the client setup.

Step 5: Post-Upgrade Validation and Service Pack Application

Launch SolidWorks on the upgraded client machines and verify that all necessary add-ins load correctly without throwing licensing or DLL errors. Open a legacy assembly and drawing to test backward compatibility and ensure proper feature tree rebuilding. Finally, check the Dassault Systèmes support portal for the latest Service Pack (SP) release and apply it to all clients and servers to patch known stability bugs.

SolidWorks Version Compatibility and System Requirements

Common Upgrade Failures and Field Fixes

• Root Cause: License checkout failure after upgrading the SNL Manager.
  
  
  • Actionable Fix: Restart the SolidNetWork License Manager service and ensure the client machines are pointing to the correct server hostname and port combination (e.g., 25734@servername).
• Root Cause: Graphics display corruption, viewport lag, or crashing upon opening assemblies.
  
  
  • Actionable Fix: Update your workstation's graphics driver directly from the official SolidWorks certified hardware driver portal, rather than relying on generic manufacturer updates.
• Root Cause: PDM vault login rejection due to version mismatch between the client and archive server.
  
  
  • Actionable Fix: Verify that the SolidWorks PDM client version installed on the workstation matches the exact major and service pack version of the PDM server environment.
• Root Cause: Custom templates, materials, or design libraries disappearing after installation.
  
  
  • Actionable Fix: Re-establish file location paths within SolidWorks System Options, pointing directly to your backed-up custom data directories on the network or local drive.

Frequently Asked Questions

Can I have multiple major versions of SolidWorks installed on the same computer?

Yes, SolidWorks supports side-by-side installations of different major release years (e.g., SolidWorks 2023 and SolidWorks 2024). However, once a file is saved in a newer version, it can no longer be opened in older versions without being saved down to neutral formats like STEP or IGES.

What happens to my custom macros and keyboard shortcuts during an upgrade?

Customized keyboard shortcuts, mouse gestures, and system options are stored in separate configuration files that may be overwritten during a clean install. Always use the SolidWorks Copy Settings Wizard prior to upgrading to export and safely restore your personalized user interface settings.

How do I verify if my graphics card is certified for the new SolidWorks release?

Dassault Systèmes maintains an online graphics card testing and certification directory on their official website. Search your specific GPU model and workstation manufacturer to download the exact driver version validated for optimal OpenGL performance and stability.

Why is my installation failing midway through the process with a rollback error?

Installation rollbacks are frequently caused by active background Windows processes, pending system reboots, or insufficient local administrative permissions. Clear out your local temp folder, restart the workstation, temporarily disable third-party antivirus software, and run the Installation Manager as a local administrator.

Secure Your Engineering Infrastructure Today

Plan your next major software transition carefully by auditing hardware configurations, testing administrative images, and safeguarding critical vault data to guarantee zero unscheduled downtime. Partner with certified technical specialists to ensure your engineering workflows remain robust, secure, and fully optimized for peak performance.