Upgrade Path

Getting Started > Upgrading to Citect SCADA 2018 > Upgrade Path

Upgrade path refers to the number of versions to which you need to upgrade to get from your current version to Citect SCADA 2018. Historically, some versions of Citect SCADA have included substantial changes to the product, which required incremental upgrades involving several intermediate steps between very distant versions (for example, 5.21 to 7.20). We have improved the upgrade code so that fewer steps are necessary to go from 5.21 to Citect SCADA 2018, and the number of necessary steps will depend on whether you do an offline or online upgrade.

If you plan to perform an offline upgrade, you can upgrade your project from as early a version as 5.21, directly into Citect SCADA 2018.

If you plan to perform an online upgrade, you need to follow an upgrade path that will depend on your starting version:

Prior to v7.20 - If your starting version is prior to v7.20, upgrade to v7.20 SP5A. Compile and run your project in order to restore and convert your historic alarm data.
v7.20 - If this is your starting version, you need to restore your project to SP5A. Compile and run your project in order to restore and convert your historic alarm data.
v7.40 - If this is your starting version, you need to restore your project to SP2. Compile and run the project in order to restore your data.
v2015 - If this is your starting version, you need to restore your project to SP1 Patch 6. Compile and run the project in order to restore your data.
v2016 - If this is your starting version, you need to restore your project to RTM version. Compile and run the project in order to restore your data.