Upgrading SIMATIC PCS 7 from V7.1 SP4 Directly to V9.1 Without Intermediate Service Packs

Upgrading SIMATIC PCS 7 from V7.1 SP4 directly to base V9.1 (without SP1 or SP2) is technically supported by the project migrator, but deploying base V9.1 is strongly discouraged in industrial production. Base V9.1 lacks support for newer Windows 10 Enterprise LTSC releases and contains known SQL Server and runtime synchronization defects that were subsequently resolved in V9.1 SP1 and SP2. Migration procedures described in the V9.1 SP1 update manual apply directly to V9.1 base, but proceeding directly to V9.1 SP2 is the manufacturer-recommended upgrade path.

Migration Stepping Stones and OS Compatibility Limits

Upgrading across multiple major generations of SIMATIC PCS 7—specifically from V7.1 to V9.1—spans more than a decade of core software architecture evolution:
* Operating System Transition: PCS 7 V7.1 operated on 32-bit Windows XP Professional or Windows Server 2003. PCS 7 V9.1 operates exclusively on 64-bit Windows 10 Enterprise LTSC (2019/2021) or Windows Server 2019.
* SQL Server Database Evolution: WinCC evolved from Microsoft SQL Server 2005 (in V7.1) to SQL Server 2017 (in V9.1). SQL database schemas cannot bridge this jump in a single automated step without intermediate migration tools.
* Mandatory Stepping Stone (V7.1 SP4): A PCS 7 V7.1 base system cannot be converted directly to V9.1. It must first be brought to PCS 7 V7.1 SP4. From V7.1 SP4, the project can be migrated directly into the V9.1 engineering environment.
* Service Pack Considerations: While the project database structures of base V9.1 and V9.1 SP1/SP2 are identical, base V9.1 does not support Windows 10 LTSC 2021 and lacks critical updates for Automation License Manager, CFC compiler stability, and APL faceplate scaling.

Step-by-Step Multi-Stage Upgrade Procedure

Follow this structured procedure to migrate a legacy V7.1 project into PCS 7 V9.1.

Prerequisites

Complete project archive (*.zip) generated in SIMATIC Manager on the healthy V7.1 system.
Project already compiled and verified under SIMATIC PCS 7 V7.1 SP4.
Target Engineering Station pre-installed with Windows 10 Enterprise LTSC and SIMATIC PCS 7 V9.1 (or V9.1 SP2).
All required software licenses installed via Automation License Manager V6.0+.

Step 1: Pre-Migration Health Check in V7.1 SP4

On the V7.1 SP4 engineering station, open the project in SIMATIC Manager.
Perform a complete consistency check:
* CFC: Select Chart -> Check Consistency -> Entire Program.
* HW Config: Open each station and execute Station -> Save and Compile.
* OS: Open WinCC Explorer and run the consistency check tools.
Eliminate all syntax errors and missing block warnings before archiving.
Execute File -> Archive to generate a pristine migration archive.

Step 2: Retrieve and Migrate Project in PCS 7 V9.1

On the new Windows 10 PCS 7 V9.1 engineering station, open SIMATIC Manager.
Select File -> Retrieve and select the V7.1 SP4 archive.
Specify a local target directory on the engineering disk (e.g., D:\Projects\Plant1_V91).
Upon retrieval, SIMATIC Manager displays the Convert Project prompt:
* Acknowledge the database upgrade dialog.
* Allow the internal project migrator to convert database tables and symbol structures.

Step 3: Migrate WinCC OS Projects

In SIMATIC Manager, right-click the OS project and select Open Object to launch WinCC Explorer.
The WinCC Project Migrator launches automatically to convert the SQL Server 2005 database to SQL Server 2017.
Follow the wizard prompts and execute migration. Do not interrupt this process; database conversion may take several hours on large archives.
Once migration completes, open WinCC Explorer and run the OS Project Editor to update standard pictures, scripts, and screen resolutions.

Step 4: Update Block Types and CFC Charts

Open the Master Data Library or Chart folder in SIMATIC Manager.
Select Options -> Block Types....
Check for outdated block versions and execute New Version or transfer updated blocks from the PCS 7 V9.1 library.
Open CFC and execute a full compilation: Chart -> Compile -> Entire Program.

Verification

In SIMATIC Manager, confirm that the project tree displays without missing software package warning flags.
In WinCC Explorer, verify that the Project Migrator log reports Migration completed with 0 errors.
Open Graphics Designer and confirm that converted .pdl pictures display process tags, text fonts, and faceplates correctly.
Execute a test compile of the OS (Right-click OS -> Compile -> Entire OS). Confirm clean completion.

Limitations and Operational Precautions

Standard Library vs. APL: PCS 7 V7.1 projects built using the legacy standard library (e.g., CTRL_PID, MOTOR) can run in V9.1 using the backward-compatible Standard Library package, but cannot mix APL faceplates without full block re-engineering.
Driver Block Obsolescence: Legacy channel drivers (CH_AI, CH_DI) must be updated to their V9.1 equivalents or replaced with APL drivers (Pcs7AnIn, Pcs7DiIn) during planned outages.
No Rollback: Once converted to V9.1 SQL Server 2017 format, the project cannot be opened in V7.1 or V8.x. Always preserve the original V7.1 SP4 archive.

Engineer FAQ

Can I use the V9.1 SP1 migration manual if I am installing base V9.1?
Yes. The core engineering steps, database conversion rules, and prerequisite checklists in the V9.1 SP1 manual apply directly to base V9.1.
Why does Siemens recommend V9.1 SP2 over base V9.1?
Base V9.1 is an early major release containing known issues with Windows 10 security updates, SQL performance, and CFC memory management that were permanently resolved in SP1 and SP2.
Do I need to upgrade hardware when moving from V7.1 to V9.1?
Legacy S7-400 CPUs (such as 414-3 or 416-2) may not support newer PCS 7 V9.1 firmware features, but existing 417-4H or modern 410-5H controllers are fully supported.
Can WinCC clients run V7.1 while servers run V9.1?
No. Client-server architectures strictly require all WinCC OS servers and clients to operate on the identical software version and service pack.
Are license keys for V7.1 valid for V9.1?
No. PCS 7 V7.1 licenses cannot authorize V9.1 runtime or engineering software; official upgrade license packages (V7.x to V9.1) must be purchased.

Technical References

Siemens Industry Online Support Entry ID 109801081: PCS 7 Software Update Guide (V7.1 SP4 to V9.1).
Siemens System Manual: Migration from SIMATIC PCS 7 Standard Library to Advanced Process Library.
Siemens Compatibility Tool: Operating System and Database Matrix for PCS 7 V9.1.

Upgrading SIMATIC PCS 7 from V7.1 SP4 Directly to V9.1 Without Intermediate Service Packs