Resolving WinCC Flexible 2008 SP1 to SP5 Project Conversion

David Krause14 min read
SiemensTutorial / How-toWinCC
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview

The most reliable way to move a WinCC flexible 2008 SP1 HMI project off a legacy engineering station is to migrate it directly into a current TIA Portal version rather than chain the project through every intermediate service pack (SP2, SP3, SP4, SP5). When the SP1 project is opened in WinCC flexible 2008 SP5, the converter can report an unhandled error dialog with no further detail text. The same .hmi project can usually be opened, validated and migrated in a single step with the TIA Portal "Migrate project" function, which is the workflow recommended in the WinCC Migration Guide (TIA Portal) V3.0 from Siemens Industry Online Support.

This article documents:

  • Why a direct SP1 -> SP5 upgrade frequently aborts with a generic error
  • How to install the WinCC flexible 2008 SP5 update correctly
  • How to perform the supported two-step migration into TIA Portal (V15, V15.1, V16, V17, V18, V19 or V20)
  • Which SIMATIC panels are supported as migration targets and which require a device substitute
  • Diagnostic steps when the converter dialog still appears with no detail text
Important: Always work on a copy of the original .hmi / .fwx project. Siemens explicitly recommends copying the project before any migration attempt because the TIA Portal migration tool rewrites internal structures and a back-port is not supported.

Prerequisites

Before attempting any SP1 -> SP5 conversion or TIA Portal migration, verify the following on the engineering station:

  1. WinCC flexible 2008 SP1 (compact, standard or advanced) is installed and the original project opens without compile errors.
  2. You have local administrator rights. The setup of every service pack modifies DCOM, OPC and HMI device certificate stores.
  3. The target TIA Portal version is installed. Per the Siemens migration documentation, WinCC flexible 2008 projects can be migrated with TIA Portal V13 SP1 or higher. Use V15 or later if you want the most current conversion libraries and panel image support.
  4. A current license for the target TIA Portal (STEP 7 Basic / Professional and WinCC Basic / Comfort / Professional as appropriate to the panel family).
  5. The TIA Portal installation media matches the language of the source project. Mixed-language projects (e.g. English text library + German operator messages) require either a multilingual TIA Portal install or a language add-on.
  6. Backups: copy the .hmi file, the associated .log, .pdf, .ldb, .lck, .alf and any linked graphics folders to a separate location before starting.

Why SP1 to SP5 Fails With a Generic Error

WinCC flexible 2008 SP1, SP2, SP3, SP4 and SP5 are all minor maintenance releases of the same major version. The project file format was nominally held stable across the SP line, but the converter logic, runtime file generator and integrated device image database changed in SP3 and again in SP4 to support the new OP 177 / TP 177 4" / KP 300 Basic panels introduced mid-cycle. When SP1 encounters these updates, two patterns are typical:

  • Pattern A - Silent abort: The "Convert project" dialog appears, the progress bar runs, then a modal error is shown with only a generic message such as "An internal error has occurred. The project was not converted" and an OK button. No error code is logged to the Windows Event Viewer under "Applications and Services Logs / Siemens Automation / WinCC flexible" because the failure happens before the converter hooks the logger.
  • Pattern B - DP/F-Master mismatch: The project contains an OP/TP with PROFIBUS DP master or fail-safe (F) tag references that were compiled against an older PCS 7 or STEP 7 version. The SP5 converter refuses to advance the project unless the referenced STEP 7 integration component is present.

Because the SP1 -> SP5 path provides no diagnostic detail, the cleanest solution is to skip the SP-line entirely and migrate with the TIA Portal converter, which writes detailed messages to the migration log file <ProjectName>.MigrationLog.xml in the destination project directory.

Option 1: Convert In-Place With WinCC flexible 2008 SP5

If the deployment target is still a WinCC flexible 2008 SP5 runtime (for example on a PC-based HMI that cannot be upgraded), the SP5 conversion is possible. Use the procedure below; if the error dialog reappears, jump to Option 2.

  1. Install WinCC flexible 2008 SP5 on top of the SP1 installation. SP5 is a cumulative update and contains all hotfixes of SP2, SP3 and SP4.
  2. Close WinCC flexible and the WinCC flexible Explorer. The CCFlexMon.exe and CCStudio.exe processes must not be running.
  3. Stop the service SIMATIC HMI (display name "SIMATIC WinCC flexible Runtime") from services.msc.
  4. Right-click the .hmi project, choose Open With -> WinCC flexible 2008 SP5. Confirm the UAC prompt.
  5. The converter dialog opens. Enable Create backup of original project and confirm the destination folder.
  6. After conversion, open Project -> Compiler -> All -> Rebuild to force a clean re-compile. SP5 re-emits all .rt / .rtb / .srt runtime files.
  7. Run Project -> Check Consistency and resolve every entry in the result list before transferring the runtime to the panel.
Caution: Converting SP1 -> SP5 alters the internal revision number. Down-converting back to SP1 / SP2 / SP3 is not supported and will corrupt the project. Treat the converted file as read-only by source.

Option 2: Migrate Directly to TIA Portal (Recommended)

The migration path documented in Siemens TIA Portal help: Migrating WinCC flexible 2008 projects is the supported replacement for the SP-line upgrade. The procedure is identical for TIA Portal V15, V15.1, V16, V17, V18, V19 and V20; only the supported target panel set grows with each TIA Portal release.

2.1 Copy the source project

Per the WinCC Migration Guide (TIA Portal) V3.0 (entry ID 77430539), the first step is to copy the WinCC flexible 2008 project to a working directory. Do not migrate in place.

xcopy /E /I /H "C:\Projects\Line01.hmi" "C:\Projects\Line01_TIA"
attrib -R "C:\Projects\Line01_TIA\*.*" /S /D

2.2 Launch TIA Portal and start the migration

  1. Start TIA Portal V15 (or the version installed on the engineering station).
  2. Open the project view (Project -> Open is not used; instead open the TIA Portal portal view).
  3. From the Start portal, choose Migrate project. In V15 this entry is in the "Open existing project" task card; in V17 / V18 / V19 / V20 it is in the "Migrate project" portal.
  4. Browse to the copied .hmi file. TIA Portal auto-detects the WinCC flexible 2008 SPx format and starts the migration wizard.
  5. The wizard performs four sub-steps:
  • Read - parses the .hmi and lists every HMI device found in the project.
  • Convert - rewrites the project into the TIA Portal HMI schema.
  • Adjust - maps the old WinCC flexible device to a TIA Portal device substitute when an exact match is unavailable.
  • Generate - compiles the migrated project and writes the migration log.
  1. Accept the default target location. No additional settings are required for a standard WinCC flexible 2008 SP1 source.
  2. When the wizard completes, open the resulting <ProjectName>.ap<version> project.

2.3 Review the migration log

The TIA Portal migration tool writes <ProjectName>.MigrationLog.xml in the same directory as the migrated project. Open it in Internet Explorer / Edge or any XML viewer. The log uses three severity levels:

Severity Meaning Action
Information Element migrated successfully. Common for tags, screens, alarms. None.
Warning Element migrated with a substitute. Examples: color palette remapped, OPC server connection rebuilt, faceplate downscaled. Verify in the engineering view.
Error Element could not be migrated. Common causes: unsupported script function, missing optional package, custom ActiveX control. Manual fix in TIA Portal or re-create the element.

Panel Compatibility Matrix

Not every WinCC flexible 2008 device is supported as a one-to-one TIA Portal target. The mapping below is derived from the device catalog that ships with TIA Portal V17 and remains valid for V18 / V19 / V20. Always confirm against the installed device catalog before commissioning.

WinCC flexible 2008 source device TIA Portal substitute (recommended) Migration behavior
OP 73 / OP 77A / OP 77B KTP 400 Basic (mono / color) Substitute required. Re-layout screens.
TP 170A / TP 170B (mono) KTP 600 Basic mono PN Substitute. Re-layout for 320x240 -> 320x240 (1:1).
TP 177A / TP 177B 4" KTP 600 Basic color PN Substitute. Tag / alarm names preserved.
TP 177B 6" / TP 177C TP 700 Comfort Substitute required - new image catalog.
TP 270 6" / TP 270 10" TP 700 Comfort / TP 900 Comfort Substitute.
MP 270 6" / MP 270 10" MP 700 Comfort Substitute.
MP 370 12" / 15" TP 1500 Comfort / TP 1900 Comfort Substitute - resolution change.
PC Runtime (WinCC flexible RT) WinCC Runtime Professional / HMI RT Substitute - script engine changes from VBScript to VBScript + C.
Mobile Panel 170 / Mobile Panel 277 KTP 700F Mobile / KTP 900F Mobile Substitute required; F-channel mapping must be re-validated.
OP 277 6" / OP 277 10" TP 700 Comfort / TP 900 Comfort Substitute. Key/IO layout redraws.
Engineering note: When a substitute device is assigned, TIA Portal re-emits every screen at the new resolution. Touch areas, button positions and trend axis scaling must be re-checked manually. The migration tool only re-emits geometry; it does not re-flow the layout.

Script and Function Migration

WinCC flexible 2008 supported a VBScript subset. TIA Portal extends that engine with the WinCC Scripting Engine (WCCSE) and adds ANSI-C as a first-class language. Most VBScript constructs migrate, but the following call sites require manual rework:

WinCC flexible 2008 function TIA Portal status Workaround
SmartTags("Tag") Supported - aliased to HMIRuntime.Tags None.
ShowAlarmWindow Supported - object model renamed to ShowAlarmWindow on HMIRuntime.Screens Verify parameter order.
SetLanguage Supported - moved to HMIRuntime.SysFct.SetLanguage Update call site.
PrintScreen Partially supported - print to network printer only Add a local spooler or use HMIRuntime.Trace for log output.
ActivateScreenWithNumber Supported as HMIRuntime.Screens.SysFct.ActivateScreenWithNumber None.
Read / Write file (FSO) Supported - FSO active, but restricted to C:\ProgramData\Siemens\Automation\ Move file paths to the approved sandbox directory.
Custom ActiveX controls Not migrated Re-add the OCX from the TIA Portal "Add-ons" catalog and re-bind the tag interface.
VB DLLs (external .dll calls via Declare) Not migrated Wrap in TIA Portal VBS functions or move logic to a S7-1500 / S7-1200 user function block.

Common Migration Errors and Fixes

Symptom Root cause Fix
"The project was created with a newer version of WinCC flexible and cannot be opened." Project was opened and saved in a WinCC flexible version newer than the one installed on the engineering station. Install the matching SP level or older. Confirm the project header with the WinCC flexible Explorer before opening.
Generic modal error with no detail text during SP1 -> SP5 conversion Converter exception before logger hook - usually a corrupted internal object (faceplate, script, library reference). Run WinCC flexible 2008 SP1 Project -> Save As with "Recompile all" enabled, then attempt the SP5 conversion again. If still failing, go straight to TIA Portal migration.
Migration aborts at the "Read" step with a Win32 / file-access error Source .hmi file is read-only, on a network share without write permission, or the path contains Unicode characters outside the basic plane. Copy to a local NTFS path with no spaces and no Unicode supplementary characters. Re-run the migration.
Device substitute dialog does not show the expected target panel TIA Portal device catalog is filtered to a specific firmware range. Open Options -> Support Packages and install the matching HSP (Hardware Support Package) for the panel family.
Migration log shows Function <name> not migrated Custom VB script using a deprecated API. Replace with the equivalent TIA Portal system function. See the script table above.
Tags show question marks after migration Source tags referenced a STEP 7 DB that was not present in the migration bundle. Add the STEP 7 project to the TIA Portal multi-project before migrating the HMI.
Compile error "Library <XYZ> not found" Source referenced a WinCC flexible option (e.g. Audit, Sm@rtAccess) not licensed in TIA Portal. Install the matching TIA Portal option or remove the library reference.

Step-by-Step: Full SP1 -> TIA Portal V17 Example

The most common case encountered in 2024 - 2026 is an SP1 project that must end up on a current Comfort Panel running TIA Portal V17 / V18 / V19 / V20. The full procedure is:

  1. Make a working copy of the project: xcopy /E /I /H "D:\HMIs\Boiler.hmi" "D:\HMIs\Boiler_work"
  2. Open the copy in WinCC flexible 2008 SP1. Run Project -> Check Consistency. Resolve every entry. Save.
  3. Install TIA Portal V17 (or current version) with the Comfort Panel HSP and any option packages used by the project.
  4. Start TIA Portal V17. In the portal view click Migrate project -> WinCC flexible 2008.
  5. Browse to Boiler.hmi. Confirm the device list. Click Migrate.
  6. Wait for the wizard to complete. Open Boiler.MigrationLog.xml and address every error.
  7. Open the migrated project. TIA Portal will prompt to assign a substitute device for the original panel. Pick the closest match from the catalog.
  8. Run Compile -> Software (rebuild all). Resolve all warnings and errors.
  9. Use Project -> Device proxy & IO check to verify tag bindings to the STEP 7 program.
  10. Download to a test panel and exercise every screen, alarm and script path before production transfer.

Verification

After either the SP1 -> SP5 conversion or the TIA Portal migration, the following checks are mandatory before any production transfer:

  1. Compile clean. "Compile -> Software (rebuild all)" returns zero errors and zero warnings.
  2. Consistency check. "Project -> Check consistency" returns zero entries in the result list.
  3. Tag cross-reference. Verify that every tag used on a screen is mapped to a real PLC address or internal tag. TIA Portal highlights unmapped tags in red.
  4. Alarm simulation. Use the HMI runtime simulator to trigger at least one bit, one analog, one discrete and one operator-triggered alarm. Confirm the alarm line, alarm window and alarm log all show the expected text.
  5. Script dry run. Open the runtime simulator and exercise every "Change value", "Execute function" and "Activate screen" input. Look for VBScript exceptions in the TIA Portal output window.
  6. Recipe round-trip. If the project uses recipes, transfer a recipe set, modify a value and write it back. Confirm the file is created under the runtime's recipe folder.
  7. Audit trail. For Audit / GMP projects, generate a user action and confirm the audit trail XML is written to the configured network share.
  8. Backup of the converted project. Store the converted / migrated project together with the migration log and the original SP1 project in a versioned archive.

Troubleshooting Matrix

Failure point Diagnostic step Recovery
SP1 open in SP5 Check %TEMP%\Siemens\WinCCflexible\Converter_*.log Reinstall SP5; repair WinCC flexible 2008 base via the setup.
SP5 -> TIA Portal read Check MigrationLog.xml Address each error; re-run migration from the working copy.
TIA Portal compile Inspect the "Compile" output window Right-click the error and use "Show cross-reference".
Panel download Open the panel web server (https://<panel>/) and check the event log Reset the panel to factory, re-transfer the project.
PLC connection Use TIA Portal online diagnostics on the S7 connection Re-enter the connection parameters; verify S7 subnet routing.
Script runtime Check SIMATIC HMI\Trace\ folder on the panel Wrap suspect calls in error handlers; re-test.

Field-Proven Caveats

  • Projects that integrate WinCC flexible with STEP 7 V5.5 must be migrated as a multi-project (STEP 7 + HMI) so that the S7 connection is rebuilt correctly. Migrating the HMI alone leaves the tag interface bound to a placeholder PLC.
  • If the source project uses the ProAgent diagnostic view, ProAgent is discontinued in TIA Portal V14 and later. The diagnostic screens must be re-implemented with the standard TIA Portal alarm view.
  • PROFIBUS DP direct keys (used on OP 270 / OP 277) are not supported in TIA Portal Comfort Panels. The IO behavior must be re-routed through PROFINET.
  • WinCC flexible 2008 used a 32-bit DCOM configuration. TIA Portal enforces 64-bit DCOM. If the engineering station also runs STEP 7 V5.5, the DCOM tuning must be applied per Siemens migration guide entry 77430539.
  • For Audit / Electronic Signature projects, the audit database schema changed between WinCC flexible 2008 SP1 and TIA Portal V17. The migration tool writes a warning for every audit tag; verify against the audit specification before GMP sign-off.

FAQ

Can I migrate WinCC flexible 2008 SP1 directly to TIA Portal in one step?

Yes. Open the .hmi project with TIA Portal V15 or later and use the "Migrate project" function. No intermediate WinCC flexible SP upgrade is required, and the migration wizard writes a detailed log to <ProjectName>.MigrationLog.xml.

The SP1 -> SP5 conversion shows a generic error with no detail text. What now?

The WinCC flexible 2008 SP5 converter often aborts before the diagnostic logger is attached. Skip the SP-line upgrade and migrate directly to TIA Portal V15 or higher, where every error is recorded in the migration log and can be addressed systematically.

Which TIA Portal versions can migrate WinCC flexible 2008 SP1 projects?

TIA Portal V13 SP1 and all later versions support migration of WinCC flexible 2008 projects. For current device support and the most recent Comfort Panel catalog, use V17 / V18 / V19 or V20.

What is the recommended substitute for a TP 177B 6" panel after migration?

TP 177B 6" projects migrate to a TP 700 Comfort panel. The screen is re-emitted at 800 x 480; touch areas and button positions must be re-checked, and the runtime image must be loaded from the current Comfort Panel HSP.

Do WinCC flexible VBScript projects run unchanged in TIA Portal?

Most VBScript functions migrate, but external .dll calls (Declare statements), custom ActiveX controls and the legacy ProAgent diagnostic view do not. Replace them with TIA Portal system functions, add-ons from the device catalog, and the standard TIA Portal alarm view, respectively.

Back to blog