Migrating SIMATIC PCS 7 Systems from V7.0 to V9.0 SP1

Upgrading a SIMATIC PCS 7 installation from legacy V7.0 to modern V9.0 SP1 requires a phased, multi-step engineering migration, as direct one-step database conversion is not supported across seven major release boundaries. The project must first be migrated to an intermediate version (PCS 7 V7.1 SP4 or V8.0 SP2) on an intermediate engineering station to convert STEP 7 databases, CFC charts, and SFC types before migrating to PCS 7 V9.0 SP1 on Windows 10 or Windows Server 2016. Engineers must choose between two distinct migration paths: 'Software update without utilization of new functions' (retaining existing Standard Library blocks) or 'Software update with utilization of new functions' (converting logic to the Advanced Process Library).

Architectural Migration Paths: Standard vs APL Utilization

Modernizing legacy SIMATIC PCS 7 V7.0 systems to PCS 7 V9.0 SP1 is one of the most critical life-cycle engineering tasks in industrial process plants. Moving across this decade-long technology gap spans major shifts: 32-bit to 64-bit operating systems, classic Standard Library to the Advanced Process Library (APL), PROFIBUS DP to PROFINET IO, and classic S7-400 CPUs to the high-performance CPU 410-5H.

Siemens defines two distinct migration strategies documented in dedicated manuals:

Software Update Without Utilization of New Functions: Minimizes plant risk and commissioning time. Existing AS logic blocks from the legacy PCS 7 Standard Library are retained, and CFC charts are recompiled with the V9.0 compiler. The OS is modernized to WinCC V7.4 SP1, retaining classic block icons and faceplates.
Software Update With Utilization of New Functions: Full modernization. Legacy technological blocks are replaced with APL blocks (MotL, VlvL, PIDConL), SFC types are upgraded, and process screens are converted to high-performance APL faceplates and alarm management.

Intermediate Version Stepping Rules (V7.0 to V9.0 SP1)

Directly opening a PCS 7 V7.0 project in PCS 7 V9.0 SP1 is blocked by internal database format constraints. STEP 7 V5.6 and CFC V9.0 cannot parse pre-V7.1 internal schema structures. The migration requires an intermediate conversion step:

Step 1: V7.0 to V7.1 SP4 or V8.0 SP2: Retrieve the archived V7.0 multiproject on an intermediate engineering station running Windows 7 SP1 or Windows Server 2008 R2. Open the project, reorganize the database (File -> Save As -> With Reorganization), compile charts, and upgrade the Master Data Library.
Step 2: Intermediate to PCS 7 V9.0 SP1: Transfer the reorganized intermediate archive to the target PCS 7 V9.0 SP1 Engineering Station running Windows 10 Enterprise LTSC 2016 or Windows Server 2016. Execute the final database upgrade and OS project migration.

Operating System and Hardware Platform Evolution

Hardware and operating system infrastructure must be replaced during this upgrade. PCS 7 V7.0 ran on Windows XP Professional and Windows Server 2003 on 32-bit platforms, whereas PCS 7 V9.0 SP1 runs exclusively on 64-bit platforms:

Engineering Station (ES) & OS Clients: Windows 10 Enterprise LTSC (64-bit).
OS Servers, Batch Servers, and Process Historian: Windows Server 2016 Standard / Datacenter (64-bit).
Industrial Communications: Legacy CP 1613 communications processors must be replaced with modern CP 1623 cards.

Comparison of Migration Strategies

The table below contrasts the two official Siemens software update paths when migrating to PCS 7 V9.0 SP1.

Engineering DimensionWithout Utilization of New FunctionsWith Utilization of New FunctionsBlock LibraryRetains legacy Standard Library (OB_DIAG, etc.)Fully migrates to Advanced Process Library (APL)Plant DowntimeMinimal; fast cutover during brief shutdownExtended; requires loop-by-loop recommissioningAS Program ModificationNone; existing block interconnections preservedHigh; rewiring to APL structures and feature bitsWinCC FaceplatesLegacy classic faceplatesModern APL faceplates with alarm filteringHardware SupportCompatible with existing S7-400 hardwareUnlocks full CPU 410-5H and PROFINET IO featuresSiemens DocumentationSoftware update without utilization of new functionsSoftware update with utilization of new functions

Step-by-Step Multi-Stage Migration Procedure

Follow this rigorous multi-stage procedure to successfully migrate the multiproject:

Intermediate Migration (V7.0 to V7.1 SP4 / V8.0 SP2):
- Restore the V7.0 project on the intermediate ES.
- Save the multiproject with reorganization (File -> Save As -> With Reorganization (slow)).
- Open HW Config: update module firmware representations if necessary; save and compile.
- Open CFC: update block types from the intermediate library; compile charts.
- Open WinCC Explorer: run the OS Migrator to convert the Sybase/SQL Server 2005 database to SQL Server 2008.
- Create a clean project archive (*.zip).
Final Migration to PCS 7 V9.0 SP1:
- Retrieve the project archive on the PCS 7 V9.0 SP1 Engineering Station.
- Open SIMATIC Manager: allow the database converter to update the project schema to STEP 7 V5.6.
- In the Master Data Library, update block types and SFC types to V9.0 SP1.
- Open CFC: run Options -> Block Types and synchronize blocks to all chart containers.
- Compile CFC charts with Generate Module Drivers enabled.
Migrate WinCC OS Projects:
- Open WinCC Explorer for each OS: the Project Migrator automatically upgrades the database to SQL Server 2014 SP2.
- Run the OS Project Editor: select the target monitor resolution and update basic screen typicals.
- Execute a full OS Compilation (Entire OS with memory reset).
Deploy and Download:
- Download updated connection tables from NetPro to all PC stations.
- Download the compiled OS projects to the new OS Servers and Clients.

Verification

Verify the migrated installation through the following steps:
1. In SIMATIC Manager, check the CFC compile log: confirm that chart compilation completed with 0 errors and 0 unresolved drivers.
2. In WinCC Explorer, verify that the Project Editor status shows 'Configuration completed successfully'.
3. Run WinCC Runtime in simulation mode: confirm that process graphics display live tags and faceplates open without script errors.
4. Check Automation License Manager: verify that modern V9.0 runtime and engineering licenses are recognized.

Limitations and Operational Precautions

Never perform a direct in-place operating system upgrade on an active PCS 7 server (e.g., upgrading Windows Server 2003 to 2016). Always build new server hardware with clean OS installations. Additionally, verify that third-party communication drivers, Modbus gateways, or custom SCL blocks have 64-bit compatible replacements before committing to plant shutdown.

Engineer FAQ

Can I upgrade directly from PCS 7 V7.0 to V9.0 without an intermediate version?

No. The database schemas of STEP 7 and WinCC across V7.0 and V9.0 SP1 are incompatible. An intermediate conversion step in V7.1 SP4 or V8.0 SP2 is mandatory to prevent database corruption.

Why should I migrate to PCS 7 V9.0 SP1 instead of V9.0?

PCS 7 V9.0 SP1 includes critical stability updates, support for Windows 10 Enterprise LTSC, and native PROFINET S2 system redundancy for the PN/PN Coupler.