Step-by-Step Migration Paths from Legacy PCS 7 V6.1 and V7.1 to PCS 7 V9.1

Direct migration from SIMATIC PCS 7 V6.1 to V9.1 is impossible due to major database architecture changes, the introduction of 64-bit operating systems, and the shift from Microsoft SQL Server 2000 to SQL Server 2017. Migrating V6.1 requires intermediate upgrades: V6.1 -> V7.1 SP4 -> V8.2 SP1 -> V9.1. For PCS 7 V7.1, projects can upgrade directly to V9.1 if applying a 'Software update with utilization of new functions' starting from V7.1 SP4, or via V8.2 SP1 if performing a standard upgrade. Custom blocks can be preserved but require header adaptation and SCL recompilation for S7-410 compatibility.

Database and Architectural Barriers to Direct Migration

Engineers tasked with modernizing aging industrial facilities running PCS 7 V6.1 (released circa 2005) or V7.1 (circa 2009) to modern PCS 7 V9.1 face profound underlying architectural transformations:
1. Operating System Transition: Legacy V6.1/V7.1 systems run on 32-bit Windows XP, Windows Server 2003, or Windows 7. PCS 7 V9.1 operates strictly on 64-bit Windows 10 Enterprise LTSC or Windows Server 2019.
2. Microsoft SQL Server Evolution: WinCC underlying databases shifted from Microsoft SQL Server 2000 (V6.1) and SQL Server 2005 (V7.1) through SQL Server 2008/2014 to SQL Server 2017. Database file structures (*.mdf/*.ldf) cannot bridge four major SQL generation jumps in a single step.
3. CFC and Technological Database Formats: Internal Step 7 database tables and cross-reference indexes underwent major schema rewrites in V8.0 and V9.0 to support Control Module Types (CMT) and Advanced Process Library (APL).

Attempting to open a V6.1 project directly in PCS 7 V9.1 results in project opening errors, corrupted chart data blocks, or unreadable WinCC project files.

Certified Multi-Stage Migration Sequences

Siemens publishes strict migration stepping-stone requirements. Follow these staged conversion paths:

Migration Path 1: From PCS 7 V6.1

Stage 1 (V6.1 to V7.1 SP4):
* Perform database reorganization on the V6.1 engineering workstation.
* Open the project on a transition workstation running PCS 7 V7.1 SP4 (Windows 7 / Server 2008).
* Update WinCC project databases via the WinCC Project Migrator. Compile AS and OS.
Stage 2 (V7.1 SP4 to V8.2 SP1):
* Transfer the project to an intermediate VM running PCS 7 V8.2 SP1 (Windows 7 64-bit).
* Upgrade project blocks and compile charts.
Stage 3 (V8.2 SP1 to V9.1 / V9.1 SP2):
* Open the project in PCS 7 V9.1. Convert the OS project database, recompile hardware configurations, and update library blocks.

Migration Path 2: From PCS 7 V7.1

With Utilization of New Functions (Full APL Modernization): Supported directly from PCS 7 V7.1 SP4 or higher directly to PCS 7 V9.1 SP1.
Without Utilization of New Functions (Maintaining Legacy Blocks): The original project must first be updated to PCS 7 V8.2 SP1, after which it can be brought into V9.1.

Handling Legacy Libraries and Custom Regional Blocks

A critical engineering concern during migration is preserving custom, proprietary, or regional function blocks:
* Classic Library vs. APL: In PCS 7 V6.1 and V7.1, many plants utilized the standard Classic PCS 7 Library (CH_DI, CTRL_PID). In V9.1, standard projects utilize the Advanced Process Library (APL). While classic library blocks can technically execute in legacy compatibility mode, Siemens recommends planning an APL modernization.
* Custom SCL Blocks: Proprietary user blocks written in S7-SCL must be reviewed:
* Ensure source code files (*.scl) are exported from the original project.
* Recompile SCL sources in the V9.1 environment to verify that syntax complies with strict 64-bit compiler rules and S7-410 CPU instruction sets.
* Update message numbers: Ensure that ALARM_8P message identifiers are assigned unique 32-bit project-wide IDs.

Verification

In SIMATIC Manager on the V9.1 station, execute File -> Save As... -> With Reorganization (Slow). Confirm that the project rebuilds cleanly without database integrity errors.
In HW Config, replace obsolete hardware modules (e.g., CP 1613, legacy CP 443-1, and older S7-400 CPUs) with modern equivalents (e.g., CP 1623, CPU 410-5H). Execute Save and Compile.
Compile CFC charts with Generate module drivers enabled. Confirm zero errors.
Open WinCC Explorer, run the OS Project Editor, and verify that the Text Library, Alarm Logging, and Tag Logging databases compile successfully.

Limitations and Operational Precautions

Never perform an in-place operating system upgrade on an engineering workstation containing active industrial projects. Always build clean migration virtual machines.
Obsolete hardware modules that lack 64-bit drivers or modern firmware must be upgraded or replaced in HW Config.
S7-410 controllers do not support legacy communication blocks from obsolete PCS 7 libraries; ensure that communication driver blocks comply with modern APL standards.

Engineer FAQ

Can I keep my old WinCC graphics from V6.1?
Yes. WinCC picture files (*.pdl) can be migrated using the WinCC Project Migrator tool across the transition versions, though dynamic wizards may require re-linking.
Where can I obtain legacy PCS 7 versions for migration stepping stones?
Siemens Technical Support provides temporary migration software media packages (Migration Toolkits) through formal support requests.
What is the difference between upgrading with and without new functions?
Upgrading "without new functions" retains legacy block types and faceplates to minimize plant recertification. Upgrading "with new functions" replaces blocks with modern APL counterparts to utilize modern features.

Technical References

SIMATIC PCS 7 Software Update and Migration Manuals (V6.x to V9.x).
Siemens Industry Online Support Entry ID 109801081: PCS 7 Migration Paths and Compatibility Overview.
Siemens Support Guide: Upgrading PCS 7 from V7.1 to V9.1 with Minimum Downtime.

Related Tags

PCS 7, Migration, Upgrade, V6.1, V7.1, V9.1, WinCC, Engineering System, S7-400

Step-by-Step Migration Paths from Legacy PCS 7 V6.1 and V7.1 to PCS 7 V9.1