Upgrade VI to a Newer LabVIEW Version

Updated Jul 21, 2021



  • LabVIEW

LabVIEW is forward compatible, meaning that you are able to open VIs from previous versions of LabVIEW in more recent versions of LabVIEW. Upgrading to later versions of LabVIEW allows code reuse while also integrating the latest improvement to LabVIEW.

This tutorial walks you through how to upgrade your LabVIEW files to a newer version of LabVIEW.


Before upgrading your LabVIEW code to newer versions, take the following into account:
  • When upgrading code, there is no guarantee that LabVIEW code will run properly without editing.
  • If your LabVIEW files utilize API from LabVIEW modules, note LabVIEW Modules are only compatible with the version they are built for. For more information about compatibility, review the readme file of each module.
  • Please check the upgrade notes for the version of LabVIEW you are trying to upgrade to for more information.
  • If you are upgrading code that was created before LabVIEW 6.0, see the Note on Upgrading from Legacy Versions of LabVIEW section below

If you are in the process of upgrading your system and would like to ensure compatibility of your new software version with your existing hardware or OS, contact Sales by calling the number associated with Purchase and Quote on the NI - Contact Us page.

Upgrade LabVIEW Files

  1. [Suggested] Before beginning your upgrade, read through the upgrading to a newer version of LabVIEW Help material for your version of LabVIEW. This will prepare you to detect and correct upgrade difficulties as efficiently as possible.
  2. Launch the version of LabVIEW you wish to upgrade your code to.
  3. From the File menu, select Open… and navigate to the location of the file you wish to upgrade.
  4. Select OK to open your files.
  5. From the File menu, select Save As to save this newer version of your LabVIEW code.
    • Note: If you use Save instead of Save As, this will save over the original version of the code
    • Code from various versions can exist alongside each other. Best practice is to keep the original version of your code while in the process of upgrading.
  6. [Suggested] Mass Compile your code to ensure that links between VIs and subVIs are maintained. This will also check for any corrupted VIs. A single file or an entire directory can be selected for mass compile and the items will be opened in the new version, saved, and then closed.

Note on Upgrading from Legacy Versions of LabVIEW

To open a VI created before LabVIEW 6 in LabVIEW 8.5 or later, you must first convert the VI to a LabVIEW version between 6 to 8.2. 
  • In this situation, NI recommends upgrading to LabVIEW 8.2.1 as an intermediate version because it is the version of LabVIEW closest to the current.
  • Customers with Standard Service Program (SSP) can access older versions of LabVIEW by contacting NI support.
Once you have upgraded to a version after 6.0, you can continue with the steps above.