How to Locate and Plan Official Migration Paths from PCS 7 V7.1 to V9.1 SP2

To upgrade a legacy SIMATIC PCS 7 V7.1 system to PCS 7 V9.1 SP2, you must follow a structured multi-stage migration path rather than attempting a direct project conversion. Siemens does not support direct single-step database migration across two decades of software releases (spanning Windows XP to Windows 10 LTSC). The official upgrade strategy requires a two-step intermediate progression: first migrating the V7.1 project to an intermediate version (PCS 7 V8.2 SP1) using intermediate engineering environments, and subsequently migrating from V8.2 SP1 to PCS 7 V9.1 SP2. This process requires evaluating hardware compatibility (replacing obsolete IPCs and CP cards) and acquiring the official SIMATIC PCS 7 Software Update with/without Utilization of New Functions manuals from Siemens Industry Online Support (SIOS).

The Architectural Gap: PCS 7 V7.1 vs. PCS 7 V9.1 SP2

Upgrading from PCS 7 V7.1 (released around 2009) to PCS 7 V9.1 SP2 (released in 2022) bridges major technological generational shifts across all automation layers:
- Operating Systems: Transition from 32-bit Windows XP / Windows Server 2003 to 64-bit Windows 10 Enterprise LTSC / Windows Server 2019.
- Database Engine: Transition from Microsoft SQL Server 2005 to Microsoft SQL Server 2017.
- Control Libraries: Shift from legacy Standard Library (CTRL_PID, VALVE, MOTOR) to the Advanced Process Library (APL).
- Communication Hardware: Transition from legacy CP 1613 communication processors and classic PCI cards to modern PCIe network cards (CP 1623, CP 1628) and PROFINET.

Because database table schemas and cryptographic security mechanisms differ completely, modern PCS 7 V9.1 engineering tools cannot read or convert raw V7.1 project archives directly.

Official Siemens Migration Documentation and SIOS Manual IDs

To plan a compliant migration, consult the official Siemens migration manuals available on SIOS:

Migration StageDocument TitlePrimary FocusPhase 1: V7.1 to V8.2SIMATIC PCS 7 Software Update with Migration from V7.1 to V8.2Migrates WinCC databases, converts Sybase/SQL tables, upgrades CFC/SFC databases, and adapts S7 libraries.Phase 2: V8.2 to V9.1SIMATIC PCS 7 Software Update with Migration from V8.2 to V9.1 SP2Upgrades SQL Server to 2017, modernizes OS Project Editor templates, and integrates APL V9.1 features.General ArchitectureSIMATIC PCS 7 Compendium Part A - Configuration Guidelines (Entry 109742323)Complete reference for hardware sizing, network architecture, and lifecycle rules.

Intermediate Migration Roadmap: The Mandatory V8.2 Step

Attempting to open a V7.1 project directly inside PCS 7 V9.1 SP2 triggers database read failures and corrupts internal pointers. The mandatory migration sequence is:

[PCS 7 V7.1 SP3/SP4] (Windows XP)
         │
         ▼ (Step 1: Execute Project Migrator & Library Update)
[PCS 7 V8.2 SP1] (Windows 7 SP1 / Server 2008 R2)
         │
         ▼ (Step 2: Convert to SQL Server 2017 & Modernize APL)
[PCS 7 V9.1 SP2] (Windows 10 LTSC / Server 2019)

Step 1 (V7.1 -> V8.2): An intermediate engineering virtual machine running Windows 7 SP1 and PCS 7 V8.2 SP1 is created. The V7.1 project is restored, reorganized, migrated via the WinCC Project Migrator, and compiled without errors.
Step 2 (V8.2 -> V9.1): The resulting clean V8.2 SP1 project archive is transferred to the modern PCS 7 V9.1 SP2 engineering station. The project undergoes final migration, OS Project Editor updates, and CFC block type synchronization.

Hardware and Operating System Lifecycle Considerations

A software update from V7.1 to V9.1 cannot be performed on existing V7.1 plant computers:
* Industrial PCs (IPCs): Legacy Siemens IPCs (such as Microbox 427B, Rack PC IL 43, Box PC 627B) lack UEFI firmware, 64-bit multi-core processors, and sufficient RAM (minimum 16 GB to 32 GB required for V9.1). Complete IPC hardware replacement with modern IPC647E / IPC547J stations is required.
* Controllers (AS): Classic S7-400 CPUs (e.g., 414-3, 416-3, 417-4) can remain in service if their firmware is upgraded to the minimum supported revision (typically FW V5.3 or higher). Older S7-400 CPUs (e.g., 6ES7 416-2XK02-0AB0) must be replaced by CPU 410-5H Process Automation.
* Network Infrastructure: Obsolete AUI/BNC transceivers and legacy OSM/ESM optical switches must be replaced with modern SCALANCE X-200 / X-300 switches supporting PROFINET and Gigabit Industrial Ethernet.

Verification

To verify that migration planning and execution are sound:
- Verify intermediate project consistency: in the PCS 7 V8.2 intermediate environment, execute Check Block Types and compile all charts with 0 errors before proceeding to V9.1.
- In PCS 7 V9.1 SP2, verify that the project opens cleanly in SIMATIC Manager with no missing software package warnings.
- Run an OS Compile in V9.1: confirm that WinCC generates tags, alarm lists, and picture hierarchies without database schema errors.
- Validate safety programs: if the plant includes S7 F Systems, confirm that F-signatures are documented and safety CRCs compile cleanly in S7 F Systems V6.4.

Limitations and Operational Precautions

Never Perform In-Place OS Upgrades: Never attempt to upgrade an existing operating system in-place (e.g., upgrading Windows XP to Windows 7, then Windows 10). Always deploy clean operating system installations on new or freshly formatted industrial workstations.
License Upgrades: Legacy authorizations (yellow floppy disk licenses from V7.1) cannot run PCS 7 V9.1. Purchase official Software Upgrade Packages (Upgrade licenses for ES, OS Server, OS Client, and AS Runtime POs) managed via Automation License Manager (ALM).
Legacy Standard Library Deprecation: While PCS 7 V9.1 includes compatibility libraries for legacy Standard blocks, Siemens strongly recommends modernizing control loops to the Advanced Process Library (APL) during the migration window.

Engineer FAQ

Can I migrate directly from V7.1 to V9.0 without going through V8.2?

Siemens officially mandates PCS 7 V8.2 as the bridge version. Skipping V8.2 frequently leads to corrupted WinCC graphics scripts and broken Alarm Logging archives due to major SQL database transformation boundaries.

Where can I download the intermediate PCS 7 V8.2 software if I do not own it?

Contact your local Siemens Technical Sales Representative or open a SIOS Support Request. Siemens provides temporary trial or migration software media for verified customers performing approved multi-version upgrade projects.

Will my old WinCC process graphics (*.pdl) work in V9.1 SP2?

Yes, but they must be converted using the WinCC Project Migrator and updated using the OS Project Editor. Any legacy ActiveX controls or 16-bit C-scripts must be replaced with standard WinCC .NET controls or modern VBScripts.

What happens to running batch recipes in SIMATIC BATCH?

SIMATIC BATCH data must be exported and migrated using the BATCH Migration Tool. Historical batch data cannot be actively executed during controller cutovers; active batches must be completed or aborted prior to the migration shutdown.

Technical References

Siemens Industry Online Support: SIMATIC PCS 7 Software Update with Migration from V7.1 to V8.2 (SIOS Manual).
Siemens Industry Online Support: SIMATIC PCS 7 Software Update with Migration from V8.2 to V9.1 SP2 (SIOS Manual).
SIOS Entry 109742323: PCS 7 Compendium Part A - Configuration Guidelines (Section: Software Upgrades and Lifecycle).
SIOS Entry 109809264: SIMATIC Process Control System PCS 7 Released Modules.