WinCC V7.2 to TIA Portal V12 Migration: Resolving TP1500 HMI 56% Failure

Overview

Engineers who attempt to migrate a SIMATIC WinCC V7.2 SCADA project into TIA Portal V12 for a TP1500 Comfort panel frequently see the migration wizard terminate with the dialog "Software encountered with problem and it asks to restart or close" at roughly 56 % of the import. The intermediate .am12 file generated from V7.2 (or V7.3) contains object layouts, graphics paths, and structure tag metadata that the V12 importer cannot parse, and the crash is non-resumable. The root cause is a documented version compatibility gap: TIA Portal V12 accepts only WinCC V7.0 SP3 as a migration source. Any newer V7.x source falls outside the supported matrix and the importer fails partway through, normally right when it begins parsing the graphics folder of the GraCS container.

This article documents the supported source version matrix, the cause of the 56 % crash, the three engineering workarounds that allow ~1200 structure tags and the matching graphics to land on a TP1500 Comfort HMI without losing the SCADA logic already built in WinCC V7.2, and a field-tested commissioning checklist.

Prerequisites

• TIA Portal V12 SP1 Update 5 (or later V12 service pack) installed on the engineering station
• SIMATIC WinCC V7.0 SP3 source project as the direct migration source
• SIMATIC WinCC V7.2 / V7.3 source project (current) — used to rebuild parts dropped during the downgrade
• TP1500 Comfort (article number 6AV2 124-1QC02-0AX0 or later index) with a WinCC Comfort V12 image
• License key for WinCC Comfort (TIA Portal) on the engineering PC
• Second engineering PC with WinCC V7.0 SP3 installed for the compatibility build (do not co-install V7.2 on the same machine)
• SIMATIC S7-1200 or S7-1500 controller project to host the new HMI tags
• Reference: SIMATIC TIA Portal V12 SP1 - Release notes / readme

Supported Migration Source Matrix

The TIA Portal V12 migration wizard enforces a fixed source version per target product. Importing a project outside this matrix is the primary cause of crashes at non-zero percentages.

A no entry means the migration wizard either rejects the .am12 file up front, or terminates with a fault partway through. A crash at 56 % with the restart or close prompt is the signature of the V7.0 SP3 boundary: the importer accepted the header of the V7.2 container, then failed when it began parsing V7.2-specific XML nodes.

Root Cause of the 56 % Crash

The .am12 file is a TIA V12-specific container that holds screens, tags, alarms, and graphics references. When generated from WinCC V7.2 or V7.3, the container includes:

• Compiled graphics with references to the V7.2 graphics library paths (for example \\<server>\WinCCProj\GraCS\...)
• Structure tag UDTs whose internal layout changed between V7.0 SP3 and V7.2 (added @UserData XML nodes, multi-language text references, OPC UA mapping metadata, and the V7.2 audit-trail element)
• Alarm classes that reference V7.2-only message blocks and the V7.2 chronological messaging schema

The TIA V12 importer reads the .am12 sequentially. It processes tag DBs, then graphics references, then alarm and message structures. At the 56 % mark it begins parsing the V7.2 graphics folder, fails to resolve one or more graphic references, and falls into an unhandled exception that the host process surfaces as the Software encountered with problem dialog. The migration is non-resumable from that point — closing the dialog leaves the partially imported TIA project in an inconsistent state, and the wizard refuses a second run on the same partially-built project tree.

Solution Path

Three engineering approaches resolve the migration failure, ordered from least effort to most complete:

1. Rebuild the project in WinCC V7.0 SP3 and migrate the resulting .am12 into TIA V12.
2. Upgrade the engineering station to TIA Portal V14 SP1 or later (V13 already accepts V7.2, V14 SP1 is the recommended production baseline), and migrate the V7.2 project directly.
3. Use the TIA Openness API to import individual graphics and tag XML into the V12 project when neither a downgrade nor a TIA upgrade is possible.

Approach 1 — Rebuild in WinCC V7.0 SP3

1. Install SIMATIC WinCC V7.0 SP3 (with Hotfix 6 or later) on a dedicated engineering station. Do not install V7.2 on the same PC — the project converter will silently fail on shared DLLs.
2. Open the original V7.2 project in V7.2, then export to a V7.0 SP3-compatible project file. The export drops V7.2-specific features (V7.2 audit trail, OPC UA server, the modern web navigator controls, and the V7.2 user administration schema). Document the dropped features in a migration delta sheet.
3. Open the project in WinCC V7.0 SP3 and verify that all 1200 structure tags still resolve, and that every graphic listed in the GraCS folder is reachable through a local path (not a UNC path to the original V7.2 server).
4. Generate the .am12 from the V7.0 SP3 project. The exact command is Project → Migrate to TIA Portal V12 in WinCC Explorer, or Project → Export → TIA Portal V12 in the WinCC project manager.
5. In TIA Portal V12, choose Project → Migrate project and select the .am12 file. Migration should complete to 100 % and the resulting project will contain the screens, structure tags, and graphics.
6. Compile the migrated TIA project (HMI_1 → Compile → Software (all)) and download to the TP1500 Comfort target over PROFINET.

Approach 2 — Upgrade TIA Portal

1. Move the engineering station to TIA Portal V14 SP1 or later (V15.1, V16, V17 are the common modern targets). V13 already accepts V7.2 as a source, but V14 SP1 is the recommended production baseline for the TP1500 Comfort.
2. From WinCC V7.2, run Project → Migrate to TIA Portal V14 directly. The wizard creates a .ap14 file rather than .am12.
3. Open the .ap14 in TIA V14 SP1, retarget the HMI from the generic TP1500 Comfort to the exact article number in use (6AV2 124-1QC02-0AX0 or later), and recompile.
4. Validate the 1200 structure tags using the HMI tag simulation table. Structure element access in V14 is identical to V12, so no client code change is required in the S7-1500 project.
5. Download the rebuilt V14 project to the TP1500. The panel accepts the V14 image only if the panel firmware is ≥ V14.0.0; use ProSave to update the panel image first.

Approach 3 — TIA Openness Graphics Import

When neither a V7.0 SP3 rebuild nor a TIA upgrade is possible, individual graphics can be imported through the TIA Openness API. The supported XML format is documented in the TIA Portal Openness API reference. Each graphic is referenced by relative path inside the XML, and all language variants of the graphic are bundled in the same import call.

Reference: Importing graphics to a project — TIA Portal Openness API

Skeleton of the import call (C# against TIA Openness):

// Open the TIA Portal as automation interface
var tia = new TiaPortal();
var project = tia.Projects.Open(@"C:\Projects\TP1500.ap12");
var hmiTarget = project.GetObject<HMITarget>("TP1500_1");

// Load the graphics XML that references all PNG/BMP/SVG files by relative path
var graphicsImport = hmiTarget.Graphics.Import(
    @"C:\Imports\graphics_index.xml",
    ImportOptions.ReplaceExisting
);

project.Save();
project.Close();
tia.Dispose();

Use this approach only for the graphics subset; structure tags still require a supported source migration because the TIA Openness API does not expose a direct UDT-to-HMI-tag import path for V7.x projects.

Importing Structure Tags

After a successful migration the structure tags appear under HMI tags → [tag table] → [structure]. To preserve the V7.2 structure definition (element name, data type, access method, length, PLC connection):

1. In the migrated TIA project, right-click the HMI tag table and choose Add new structure tag.
2. Map the structure 1:1 to the matching S7-1500 PLC data type (DB or UDT). On a TP1500 Comfort connected to an S7-1500, the structure can be tied directly to a DB with Access mode = Symbolic.
3. Re-bind the V7.2 structure elements to the new HMI structure. Use the HMI tag simulation tool to verify that all 1200 tags still update at the expected cycle (default 1 s, configurable down to 100 ms in the connection properties).
4. For each tag, confirm the following carry-over items:

5. Recompile the HMI and download to the TP1500.

Importing Graphics to the TP1500

The TP1500 Comfort supports the standard WinCC Comfort graphic set: BMP, JPG, PNG, GIF, SVG, EMF, WMF, DXF. After migration, all V7.0 SP3 graphics appear in the project under Graphics. Verify each graphic against the table below before downloading.

If any graphic was originally linked by absolute network path in V7.2, the migration wizard will preserve the path, and the TP1500 will fail to resolve it at runtime. Use Project tree → Graphics → Reset reference to convert all absolute paths to project-relative before downloading.

TP1500 Comfort Hardware Reference

Verification

1. Compile the TIA V12 project: HMI_1 → Compile → Software (all). Resolve any remaining warnings before continuing.
2. Start the WinCC Comfort simulation. Each of the 1200 structure elements should appear with the same name, data type, and connection as in the V7.2 source.
3. Toggle a few HMI tags in the simulation table and confirm the connected S7-1500 DB updates within one acquisition cycle.
4. Download the project to the TP1500 Comfort over PROFINET. Expected transfer time for a 30 MB project over 100 Mbit/s is 8 - 12 s.
5. On the panel, run a manual tag test. Cycle power, then verify that all structure tags read 0xFF / Good on the diagnostics screen (Settings → OP → Diagnostics → Tags).
6. Force a value on the S7-1500 DB and confirm the corresponding HMI tag updates on the TP1500 within the configured acquisition cycle.

Troubleshooting Matrix

Commissioning Checklist

• WinCC V7.0 SP3 source project archived with timestamp and SHA-256 hash
• Migration delta sheet signed off (V7.2 features dropped during downgrade listed)
• All 1200 structure tags visible in the TIA project and bound to a symbolic DB
• All graphics references relative to project root, no UNC paths remaining
• PLC connection tested with S7-1500 online diagnostics (no quality code 0x00 entries)
• TP1500 firmware ≥ V12.0.1 (verify via Panel → Diagnostics → System information)
• Operator authorization levels migrated from V7.2 user administration
• Backup of the migrated .ap12 file stored on the engineering server
• Panel image (RS image) backed up via ProSave to allow recovery to a known state

FAQ