Migrating WinCC V7.3 to TIA Portal V13/V14: Resolve PDL Errors

Migrating WinCC V7.3 to TIA Portal V13/V14: Compatibility Matrix and PDL Workflow

Engineers porting an existing WinCC V7.3 SCADA/HMI project to a TIA Portal engineering suite encounter a non-descriptive "project version not supported" error in the migration wizard. TIA Portal V13 (including V13 SP1 and V13 SP1 Update 2) accepts only WinCC V7.0, V7.0 SP1, and V7.2 source projects. The migration dialog's source-version filter silently rejects V7.3, V7.4, and V7.5 before any conversion logic runs, producing no log entry, no remediation hint, and no line reference. The same limitation blocks direct PDL (Process Display Language) export from V7.3 to TIA Portal V13; there is no standalone PDL-only export tool, and the Siemens Migration Suite's WinCC Project Extension does not provide a V7.3 → TIA Portal screen transfer capability.

This reference documents the WinCC V7 → TIA Portal compatibility matrix, the root cause of the silent rejection, the upgrade path to TIA Portal V14 (the first TIA release that accepts V7.3), the manual PDL rebuild workflow when an upgrade is not feasible, and a verification matrix for commissioning the migrated project.

1. Compatibility Matrix: WinCC V7 Source → TIA Portal Target

Source: Siemens Support Entry ID 109963167 – Migration of WinCC V7 projects to TIA Portal; TIA Portal V20 documentation – Migration (WinCC V7).

2. Root Cause Analysis

The TIA Portal migration wizard reads the version stamp embedded in the WinCC V7 .mcp project file header. Each WinCC V7 SP incremented that stamp and introduced new screen objects, runtime APIs, and configuration schema elements:

• WinCC V7.2: Standard PDL schema, classic alarm classes, VBScript engine v1, OPC DA / HDA channels.
• WinCC V7.3: Added .NET controls, additional SmartOptions, revised alarm-class semantics, raw-value tag logging triggers.
• WinCC V7.4+: Further schema revisions, WPF control support, OPC UA channel additions.

The migration DLLs shipped with TIA Portal V13 SP1 Update 2 carry a frozen version whitelist that terminates at V7.2. When the wizard opens the file dialog, it inspects the version stamp and filters V7.3+ entries out of the visible file list. Because the filter operates before the conversion engine runs, no diagnostic log is written and no error number is surfaced to the user.

For PDL files specifically, the runtime format also evolved between V7.2 and V7.3. The TIA Portal V13 PDL importer understands only the V7.0/V7.2 PDL schema; any V7.3-specific screen object (e.g., a .NET control instance or a V7.3-only SmartOption) would require a runtime translation layer that TIA Portal V13 does not include.

Decision Path

1. If target TIA Portal = V13 (any SP): V7.3 migration is not possible with the shipped toolset. Manual rebuild or tool upgrade required.
2. If target TIA Portal = V14 (no SP): V7.3 is the highest source version accepted by the migration wizard. This is the first viable automated path.
3. If target TIA Portal = V14 SP1 or later: V7.3 migration is documented in Siemens support ID 109963167; verify the specific TIA Portal release notes for any service-pack-specific restrictions.

3. Project-File Internal Markers

When diagnosing a migration failure, the following markers in the WinCC V7 .mcp archive identify the source version:

4. Diagnostic Workflow: Confirming the Rejection

1. Open TIA Portal at the target version (e.g., V13 SP1 Update 2).
2. Select Project → Migrate project.
3. Browse to the WinCC V7.3 .mcp file.
4. Inspect the "Files of type" filter: only V7.2 and earlier WinCC SCADA projects are listed.
5. If the source file does not appear in the filter, version rejection has occurred at the file-open stage.
6. To confirm independently, rename project.mcp to project.zip, extract, and inspect the project header for the WinCC version stamp.
7. Open the extracted version.info or top-level project manifest; the version field will read 7.3.x.

Time estimate: 5 minutes to confirm the rejection; 30-60 minutes to capture full diagnostic state.

5. Solution Path A: Upgrade TIA Portal to V14 (WinCC Professional V14)

TIA Portal V14 (released 2015) is the first TIA Portal release that accepts WinCC V7.3 as a migration source. SP1 of V14 and later TIA Portal releases (V15, V15.1, V16, V17, V18, V19, V20) also accept V7.3, subject to release-specific verification against current TIA Portal documentation.

Prerequisites

• TIA Portal V14 or later with WinCC Professional license
• Original WinCC V7.3 project (all referenced PDL files, tag database, alarm configuration intact)
• Valid license key / license dongle for the target TIA Portal version
• Disk space: TIA Portal runtime container is typically 3–5× the source WinCC V7 project size
• Backup of the WinCC V7.3 project before migration

Step-by-Step Procedure

1. Install TIA Portal V14 (or higher) on the engineering workstation. Parallel installation with V13 is supported — do not uninstall V13 first.
2. Launch TIA Portal V14.
3. Select Project → Migrate project.
4. Browse to the WinCC V7.3 .mcp file. Verify that V7.3 is now listed in the "Files of type" filter.
5. Select the file and confirm the migration target (e.g., a WinCC Runtime Professional V14 PC station or a Comfort Panel target).
6. Click Migrate. The wizard performs project conversion, screen conversion, tag conversion, and alarm conversion.
7. Review the migration log. Any screens, scripts, tags, or alarms that did not convert automatically appear under "Warnings" or "Errors" with line references.
8. Open the migrated TIA Portal project and inspect each screen for layout fidelity (1:1 PDL → TIA screen mapping).
9. Re-bind any PLC tag connections that did not migrate automatically; tag names from WinCC V7 do not auto-map to TIA Portal HMI tags.
10. Compile the HMI project: HMI device → Compile → Software (all). Target zero errors before proceeding.
11. Run the offline simulation: HMI device → Start runtime → Simulation. Verify screen navigation, alarm triggering, and tag updates.

For the full Siemens procedure, refer to Siemens support entry ID 109963167.

6. Solution Path B: Manual PDL Rebuild in TIA Portal V13

When the target TIA Portal version cannot be upgraded to V14 (due to license cost, plant standard, operator training, or qualification status), the only practical approach is to recreate the PDL screens natively in TIA Portal V13. PDL files cannot be exported standalone from WinCC V7.3 and imported into TIA Portal V13; the runtime format mismatch makes any direct screen transfer unreliable.

Step-by-Step Manual Rebuild

1. Open the WinCC V7.3 source project in WinCC Explorer.
2. For each PDL screen, export the screen as a high-resolution PNG (Graphics Designer → File → Export → Image). Use 1:1 pixel resolution so screen coordinates map directly to TIA Portal graphics editor coordinates.
3. Document the I/O tag references for each dynamic element: tag name, trigger address (DB offset / bit), update cycle, and scaling function.
4. Document all scripts (VBScript and C-Script) associated with each screen — trigger events, function names, and expected return values.
5. Open TIA Portal V13 and create a new HMI device (e.g., WinCC Runtime Advanced on a Comfort Panel, or WinCC Runtime Professional on a PC station).
6. Configure the HMI ↔ PLC connection in Connections, matching the WinCC V7.3 channel configuration (e.g., MPI / PROFIBUS / Ethernet).
7. Recreate each screen using the TIA Portal graphics editor. Import the PNG as a background layer (Image → Graphic IO field or background graphic).
8. Re-bind tags from the PLC connection. WinCC V7 tag names do not auto-map; create HMI tags with the same names where possible to minimize PLC-side rework.
9. Recreate animations (visibility, flashing, movement) using the TIA Portal animation table.
10. Recreate faceplate instances and picture-in-picture modules as separate screens with navigation logic.
11. Port scripts. VBScript remains the primary scripting language in TIA Portal, but the HMIRuntime object namespace differs from WinCC V7.7. Update object references accordingly.
12. Compile the HMI project and run the offline simulation to verify behavior.

Time estimate: 2–6 hours per screen for a typical 30-element process display, depending on script complexity, dynamic element count, and alarm wiring.

7. What Does Not Migrate Cleanly (Even with TIA Portal V14)

Even when using TIA Portal V14 (the first TIA version that accepts V7.3), certain WinCC V7 constructs require manual rework. Always review the migration log after the wizard completes:

8. Verification Checklist (Post-Migration)

Verify the following before commissioning the migrated TIA Portal HMI:

• [ ] All screens open in the TIA Portal graphics editor without warnings.
• [ ] HMI compilation completes with 0 errors.
• [ ] All tag connections resolve to live PLC addresses (offline simulation test).
• [ ] Runtime simulation: start RT in simulation mode; verify screen navigation and faceplate pop-ups.
• [ ] Alarm system: trigger a test alarm; verify class, priority, acknowledgment, and logging behavior.
• [ ] Tag logging: verify logging cycles, archive triggers, and CSV export operate as in V7.3.
• [ ] User administration: verify role-based access matches V7.3 configuration; test login / logout.
• [ ] Print / Report jobs: trigger a sample print and verify template rendering.
• [ ] Scripts: execute each VBScript and verify return values; check HMIRuntime object resolution.
• [ ] OPC channels: verify OPC DA or OPC UA server connection on runtime PC.
• [ ] Licensing: confirm TIA Portal runtime license is active and recognized.

9. Troubleshooting Matrix

10. Field-Engineering Notes

Why TIA Portal V13 cannot be patched to accept V7.3: The migration DLLs are part of the TIA Portal installation media and are frozen at the SP level. There is no SP-level patch, hotfix, or registry entry that adds V7.3 support to TIA Portal V13. The only path is a full TIA Portal upgrade to V14 minimum.

Parallel installation: TIA Portal V13 and V14 can coexist on the same engineering workstation. The migration can be performed on V14, and the resulting TIA Portal V14 project can subsequently be opened in a higher V14 SP or V15 via project upgrade (not downgrade — the V14 project will retain V14 features). If a true downgrade to V13 is required, the migrated project must be stripped of any V14-only features first.

Migration Suite (third-party / extended toolset): Siemens offers a Migration Suite toolset that includes a WinCC Project Extension module. This tool extends screens and adds new content but does not provide direct PDL export from V7.3 to TIA Portal V13. The Migration Suite is intended for incremental expansion, not for wholesale V7.3 → V13 conversion.

Licensing impact: A successful migration from V7.3 to TIA Portal V14 requires a WinCC Professional V14 license (or higher), not the V13 license. Budget for the upgrade before committing to the migration path. License transfer from V7.3 to V14 is generally not permitted under Siemens licensing terms.

Why the silent rejection: TIA Portal V13's migration wizard uses a file-open filter (rather than a post-load validator). This design choice prevents accidental conversion of unsupported projects but also means the user receives no diagnostic information when the source version is outside the supported range. Always check the "Files of type" dropdown before assuming the file path is incorrect.

11. Recommended Decision Flowchart

1. Can the target TIA Portal be upgraded to V14?
   • Yes → Use Solution Path A (automated migration per Siemens ID 109963167).
   • No → Use Solution Path B (manual PDL rebuild).
2. Does the V7.3 project use C-Scripts, custom ActiveX, or redundant configuration?
   • Yes → Budget additional rework time per Section 7 (table). Expect 20–40% manual rework even with automated migration.
   • No → Proceed with migration; expect <10% manual rework.
3. Does the plant standard allow TIA Portal V14 SP1 or V15+?
   • Yes → Use the latest SP for improved migration coverage and better long-term support.
   • No → Stay on V14 baseline; verify behavior against the TIA Portal documentation release notes.
4. Is the project >20 screens?
   • Yes → Path A is almost always more cost-effective.
   • No → Either path is viable; choose based on engineering time vs. licensing cost.

12. Migration Time Estimates

FAQ