1. Problem Overview
When a user attempts to migrate a WinCC flexible or WinCC (TIA Portal) project that originated in WinCC flexible 2008 SP2/SP3/SP4/SP5 into a TIA Portal V16 project, the migration wizard fails immediately with a generic dialog reading "An error occurred". The dialog provides no error code, no log path, and no further detail; clicking OK closes the wizard and the source project remains untouched.
The same symptom is documented in the TIA Portal release notes for V16 through V19 and is explicitly tied to the absence of a single optional setup component: the Migration Tool. This component is not installed by default in the standard TIA Portal V16 setup because it is only required for legacy WinCC flexible and STEP 7 V5.x migration scenarios. Users who never plan to migrate a legacy HMI or PLC project will not need it, which is why the setup dialog shows the package as unchecked out of the box.
The error is independent of the TIA Portal project being opened. It can be reproduced on a freshly installed engineering station that has both WinCC flexible 2008 SP5 and STEP 7 V5.5 (or V5.6) installed before TIA Portal V16. The order of installation is critical: WinCC flexible and STEP 7 V5.x must be installed before TIA Portal V16, because the TIA Setup reads their registry entries to build the migration package list.
Siemens.Automation.Portal.Migrator.exe when the Migration Tool assemblies are not present in the TIA Portal installation directory.2. Root Cause Analysis
Three layered conditions must all be true for the migration to succeed. If any one of them is missing, TIA Portal V16 fails with the generic error:
- Source product installation: WinCC flexible 2008 SP2 or later must be installed and registered. WinCC flexible 2007 is not a supported source.
- STEP 7 V5.x installation: STEP 7 V5.4 SP5, V5.5, V5.5 SPx, or V5.6 must be installed because the migration tool resolves tag references and cross-references against the STEP 7 V5 symbol table.
- TIA Portal V16 Migration Tool: The optional "Migration Tool" package must be selected during the TIA Portal V16 setup or added through a setup modify operation. This package contains the WinCC flexible → WinCC (TIA Portal) converter, the STEP 7 V5.x → S7-1500/1200 converter shell, and the licensing metadata required for the migration entry point to load.
When the third condition is missing, the migration wizard loads, performs a registry probe for WinCC flexible, finds it, attempts to load the migration assemblies from %ProgramFiles%\Siemens\Automation\Portal V16\Bin\Migration, fails to locate WinCCFlexibleMigration.dll, and throws an unhandled exception that the UI surfaces as the generic "An error occured" dialog.
2.1 Log Locations and Diagnostic Files
| File | Default Path | Purpose |
|---|---|---|
Siemens.Automation.Portal.exe.log |
%LOCALAPPDATA%\Siemens\Automation\Portal V16\Log\ |
Main TIA Portal startup log |
MigrationTool.log |
%LOCALAPPDATA%\Siemens\Automation\Portal V16\Log\Migration\ |
Per-migration trace including missing DLL events |
Setup.log |
%ProgramData%\Siemens\Automation\Setup\Logs\ |
TIA Setup component selection audit trail |
S7MigrationDiag.xml |
Generated on demand from menu Tools > Migration > Diagnostics | Lists detected legacy products and required packages |
If MigrationTool.log does not exist or contains no entries after a failed migration attempt, the migration assemblies were never loaded — confirming the absence of the Migration Tool package.
3. Prerequisites for a Clean Migration
Before re-running the TIA Portal V16 setup, verify the engineering station meets the following prerequisites:
| Component | Required Version | Notes |
|---|---|---|
| Windows 10 (64-bit) | 1809 / 1903 / 1909 / 2004 / 20H2 / 21H1 / 21H2 | Per TIA Portal V16 Release Notes |
| Windows Server | 2016 / 2019 Standard | Supported for engineering workstation use only |
| WinCC flexible | 2008 SP2 / SP3 / SP4 / SP5 | Must be installed before TIA Portal V16 |
| STEP 7 V5.x | V5.4 SP5 / V5.5 / V5.5 SP1–SP4 / V5.6 | Required for PLC program cross-reference |
| SQL Server | 2014 SP2 / 2016 SP2 / 2017 / 2019 | For TIA Portal project backend |
| .NET Framework | 4.7.2 / 4.8 | Required by WinCC flexible migration helper |
| Administrator rights | Required for setup modify | No uninstall needed |
3.1 Installation Order
The correct order on a single engineering workstation is:
- Install Windows and apply updates.
- Install STEP 7 V5.x (V5.5 SP4 or V5.6 recommended).
- Install WinCC flexible 2008 SP5.
- Install TIA Portal V16 with the Migration Tool package selected.
Reverse order or installing TIA Portal V16 first will not prevent the migration tool from running, but the legacy product detection will be incomplete and additional registry patches may be required.
4. Step-by-Step Solution: Activate the Migration Tool Without Uninstall
The TIA Portal V16 setup supports a modify operation that adds or removes individual packages without uninstalling the rest of the installation. This is the documented recovery path and takes 5–10 minutes depending on the packages already installed.
4.1 Launch the TIA Portal V16 Setup in Modify Mode
- Close all open TIA Portal instances and any running WinCC flexible Runtime instances.
- Insert the TIA Portal V16 installation DVD or mount the
SIMATIC_TIA_Portal_V16.iso. - If autorun is disabled, run
Start.exefrom the DVD root as Administrator. - The setup opens on the Product Language selection page; confirm and click Next.
- On the Product Selection page, TIA Portal V16 is already detected as installed. Click Next.
- The setup wizard switches to Modify / Upgrade mode automatically when it detects an existing installation of the same version.
4.2 Select the Migration Tool Package
- On the Products / Packages dialog, expand SIMATIC TIA Portal.
- Expand Options.
- Locate the entry Migration Tool (catalog name
TIA_Portal_Migration_Tool). - Change the drop-down from "Not installed" to "This program and all features will be installed on the local hard drive."
- Optionally, also enable WinCC flexible 2008 SP5 Runtime / Configuration support libraries if migrating panel configurations targeting OP 77A, TP 177, MP 177, or older Comfort Panel projects.
- Click Next.
4.3 Complete the Modify Installation
- Accept the license agreement on the next page.
- Review the license terms for the Migration Tool (it does not require an additional license key — it is a setup-time-only component).
- Click Install. Setup reports the change with the line item "Modifying SIMATIC TIA Portal V16: Migration Tool".
- Wait for the progress bar to reach 100% and for setup to report "Setup has been successfully completed."
- Do not reboot unless prompted; restart TIA Portal and the WinCC flexible Configuration tool, and the migration wizard will now find
WinCCFlexibleMigration.dllin the migration directory.
5. Performing the WinCC flexible to TIA Portal V16 Migration
With the Migration Tool installed, the migration wizard loads correctly and the project conversion proceeds.
5.1 Open the Source Project
- Launch TIA Portal V16.
- From Project > Migrate project, select WinCC flexible project.
- Browse to the
*.hmisource project (for WinCC flexible 2008 SPx) or*.ziparchive. - Click Open. The migration wizard now displays the conversion log instead of the generic error.
5.2 Migration Mapping Table
| WinCC flexible Source | TIA Portal V16 Target | Notes |
|---|---|---|
| OP 77A, OP 73, TP 170A | No direct target — manual re-implementation required | Replaced by KTP400 Basic |
| TP 177A, TP 177B, OP 177B | KTP400 Basic / KTP700 Basic | Screen geometry auto-resized |
| MP 177, MP 277 | KTP900 Basic / TP1200 Comfort | Color depth upgraded |
| MP 377, Comfort Panel 6" | Comfort Panel 6" / 7" | Direct migration supported |
| WinCC flexible Runtime (PC) | WinCC Runtime Advanced (TIA) | Tags, alarms, and scripts migrated |
| VBScript | VBScript | Most constructs pass through unchanged |
| S7-300/400 symbolic addresses | S7-1500 fully-qualified DB tags | PLC program must be migrated first |
5.3 PLC Migration Order
When migrating an integrated WinCC flexible + STEP 7 V5.x project, always migrate the PLC program first. The HMI migration reads the STEP 7 symbol table; if the PLC has not yet been migrated to S7-1500/1200, tags resolve to undefined references and require manual remapping.
- Open the STEP 7 V5.x project in TIA Portal V16 via Project > Migrate project > STEP 7 V5.x project.
- Select the target CPU family (S7-1500 / S7-1200 / ET 200SP).
- Run the conversion; resolve any "unmigratable" warnings before continuing.
- Compile and download the migrated PLC program to validate it.
- Open the HMI migration wizard; tag references now resolve against the migrated STEP 7 program.
6. Post-Migration Verification
After the wizard reports success, perform the following checks before considering the migration complete:
- Compile the TIA Portal project. Watch for warning IDs W0072 (tag not found) and W0111 (HMI connection broken) — these are the most common post-migration warnings and indicate references that the wizard could not auto-resolve.
- Cross-check tag count. Compare the tag list in the migrated TIA Portal project against the original WinCC flexible tag list. Mismatches usually indicate that the source WinCC flexible used multi-instance DB references that did not survive the PLC migration.
- Validate screen count and resolution. Migrated MP 377 screens onto a TP1200 Comfort retain geometry; smaller targets automatically scale, which can break layout-dependent text and graphic positioning.
- Inspect alarm log. Alarms that referenced absolute DB addresses in WinCC flexible become symbolic references after migration. Open each alarm and confirm the tag prefix matches the new STEP 7 program structure.
- Test the runtime simulation. Use Start Runtime in the HMI editor to launch the TIA Portal RT simulator and verify the panel behavior before commissioning.
7. Troubleshooting Matrix
| Symptom | Probable Cause | Resolution |
|---|---|---|
| "An error occured" on migration wizard launch | Migration Tool not installed | Re-run TIA Setup, select Migration Tool in Modify mode |
| "WinCC flexible 2008 SPx not detected" | WinCC flexible installed after TIA V16 | Install or repair WinCC flexible, then re-run TIA Setup / Repair |
| Wizard opens but reports "source project is invalid" |
*.hmi file was edited outside WinCC flexible |
Re-save the project from a clean WinCC flexible installation |
| Wizard converts screens but all tags are red | PLC program not migrated first | Run STEP 7 V5.x migration first, then re-migrate HMI |
| "License missing for Migration Tool" | Corporate license server unreachable | Verify license server connectivity; no separate license key is required for the setup component itself |
| Wizard crashes after 30% with .NET exception | .NET Framework 4.7.2 not installed | Install .NET Framework 4.7.2 and rerun |
| Converted panel shows white screens at runtime | Incorrect HMI device version selected during migration | Re-target the panel device and recompile |
| Migration fails with HRESULT 0x80070005 | Insufficient permissions on %ProgramData%\Siemens\
|
Run TIA Portal as Administrator once to seed ACL |
| Migration succeeds but VBScript fails at runtime | VBScript syntax or API call incompatible | Compare against V16 VBScript reference, refactor per TIA V18 Update 5 Readme |
| "An error occured while starting project" after TIA V18/V19 upgrade | Stale runtime process holding migrated project lock | End all Runtime tasks, restart, retry. Documented in WinCC Unified V18.0 Update 5 Readme |
8. Edge Cases and Known Constraints
8.1 Migrating from WinCC flexible 2007
WinCC flexible 2007 (RT and Engineering) is not a supported source for the TIA Portal V16 migration. Projects must first be opened and re-saved in WinCC flexible 2008 SP2 or later to upgrade the internal project format. The intermediate upgrade step is performed in WinCC flexible without changes to the project content.
8.2 Migrating WinCC (TIA Portal) V13/V14/V15 to V16
If the source project is already a TIA Portal HMI project (originally created in V13/V14/V15 and re-saved in V16), no migration wizard is required — open the project directly in TIA Portal V16 and accept the upgrade prompt. The Migration Tool is not involved in this case, and the "An error occurred" message does not apply.
8.3 Project Size and Memory Limits
The migration wizard loads the entire source project into memory. Practical limits observed in field deployments:
- WinCC flexible projects under 200 screens: migrate in 2–5 minutes.
- 200–1000 screens: 10–30 minutes, requires 8 GB free RAM.
- 1000+ screens: split the project in WinCC flexible first; the wizard is not designed for monolithic very large projects and may fail with an out-of-memory exception that surfaces as the same generic error.
8.4 Coordinated Migration with TIA Portal V17/V18/V19
Projects migrated into TIA Portal V16 are forward-compatible with V17, V18, and V19. The upgrade path is documented in the corresponding readme files:
When upgrading a V16-migrated project to V18 or V19, the upgrade wizard uses the same setup-time Migration Tool component. If the tool was installed for the original V16 migration, it remains available for later upgrades.
8.5 Silent Setup Deployment (Unattended)
For corporate image deployment, the TIA Portal V16 setup supports an unattended mode where the Migration Tool can be preselected in the configuration.xml answer file:
<Product>
<Name>SIMATIC TIA Portal V16</Name>
<Option>
<Id>TIA_Portal_Migration_Tool</Id>
<Selected>true</Selected>
</Option>
</Product>
Deploying the Migration Tool this way prevents the field engineer from ever encountering the "An error occurred" dialog.
9. Related Considerations
9.1 Distinguishing Setup Errors from Runtime Errors
The same "An error occured" text is reused across the WinCC product family. Two distinct contexts exist:
- Setup-time: Migration wizard fails to launch — caused by missing Migration Tool package.
- Runtime-time: WinCC Unified Comfort Panel or PC Runtime reports the same string after a project upgrade — caused by a stale WinCC Unified Runtime process holding the project lock. The fix is to acknowledge the dialog and restart Runtime after a few seconds.
The runtime variant is documented in the WinCC Unified V18.0 Update 5 readme (item 8.2 "Important notes"). For TIA Portal V16 specifically, the runtime variant is rare and applies primarily to panel-side compilations.
9.2 Licensing Impact
Activating the Migration Tool does not consume any license token at runtime — it is a setup-only component. However, opening the migrated project requires a valid TIA Portal V16 license (Floating or Single) for the HMI engineering workbench.
9.3 When to File a Siemens Support Request
If, after completing the steps in section 4, the migration wizard still fails with "An error occurred", capture the following before contacting Siemens Support:
%LOCALAPPDATA%\Siemens\Automation\Portal V16\Log\Migration\MigrationTool.log- Full TIA Setup log from
%ProgramData%\Siemens\Automation\Setup\Logs\ - Output of
reg query "HKLM\SOFTWARE\Siemens\Automation\Portal V16\Components" - Screenshot of the error dialog with the time stamp visible.
- TIA Portal V16 build number from Help > About.
Open a support request via the Siemens Industry Online Support portal at support.industry.siemens.com referencing the order number and the affected TIA Portal version.
9.4 Clean Re-Installation as Last Resort
If the Modify installation still does not register the Migration Tool correctly (rare; typically caused by a corrupted SetupState.xml in %ProgramData%\Siemens\Automation\Setup\), the documented last-resort path is:
- Uninstall TIA Portal V16 through Control Panel > Programs and Features.
- Delete
%ProgramData%\Siemens\Automation\Setup\. - Delete
%LOCALAPPDATA%\Siemens\Automation\Portal V16\. - Reboot.
- Reinstall TIA Portal V16 with the Migration Tool selected at the Products / Packages dialog.
This path is destructive only to the TIA Portal side — WinCC flexible, STEP 7 V5.x, and their projects are preserved.
10. Quick Reference
| Item | Value |
|---|---|
| TIA Portal Version | V16 (Build 16.0.0.0 and later updates) |
| Setup Package Name | TIA_Portal_Migration_Tool |
| Setup Path | Setup > Options > Migration Tool |
| Required Pre-Install | WinCC flexible 2008 SP2+ and STEP 7 V5.4 SP5+ |
| Assembly | WinCCFlexibleMigration.dll |
| Log Path | %LOCALAPPDATA%\Siemens\Automation\Portal V16\Log\Migration\ |
| Fix Time | 5–10 minutes via Modify install |
| Uninstall Required | No (unless SetupState.xml is corrupted) |
| Additional License | None for the Migration Tool component |
Why does TIA Portal V16 say "An error occured" when I try to migrate a WinCC flexible project?
The Migration Tool optional package was not selected during the TIA Portal V16 setup. The migration wizard cannot load WinCCFlexibleMigration.dll and surfaces a generic error. Re-run the TIA Portal V16 setup, choose Modify, expand Options, set Migration Tool to "installed on local hard drive," and complete the setup. No uninstall is required.
Do I need to uninstall TIA Portal V16 to enable the Migration Tool?
No. TIA Portal V16 supports a Modify / Upgrade setup mode that adds or removes individual packages while keeping the rest of the installation intact. Start the setup from the original DVD or ISO, accept the detected installation, navigate to Options > Migration Tool, and click Install. The operation takes 5–10 minutes and does not require a reboot.
Does the Migration Tool require a separate license?
No. The Migration Tool is a setup-time-only component and does not consume a runtime license token. However, opening and editing the migrated project in TIA Portal V16 still requires a valid TIA Portal HMI engineering license (Floating or Single).
Can I migrate WinCC flexible 2007 projects directly into TIA Portal V16?
No. WinCC flexible 2007 is not a supported migration source. Open and re-save the project in WinCC flexible 2008 SP2 (or later) first to upgrade the internal project format, then migrate from WinCC flexible 2008 to TIA Portal V16.
Where do I find migration log files if the error persists after enabling the Migration Tool?
Check %LOCALAPPDATA%\Siemens\Automation\Portal V16\Log\Migration\MigrationTool.log and the setup log in %ProgramData%\Siemens\Automation\Setup\Logs\. If the log shows missing legacy product entries, confirm WinCC flexible 2008 SP2+ and STEP 7 V5.4 SP5+ are installed before TIA Portal V16. If logs do not exist at all, the Migration Tool is still not installed — repeat the Modify setup step.
Does upgrading a V16-migrated project to V18 or V19 require the Migration Tool again?
No, the Migration Tool installed for V16 remains available for subsequent upgrades. TIA Portal V17, V18, and V19 read the same V16 Migration Tool assemblies for cross-version project upgrade. The relevant readme files confirm the upgrade path: V18 Update 5 Readme and V19 Update 5 Readme.