IMDTouchKnowledge BaseShop main store

How-to

How to migrate a WinCC flexible project to TIA Portal

HMI and touchscreens Published 7 min read

Short answer

One TIA Portal installation replaces both STEP 7 Classic and WinCC flexible, but the two project types move differently: the STEP 7 V5.x project is imported, and the WinCC flexible 2008 project is migrated through an intermediate release because the newest TIA Portal versions no longer offer that migration. Verify the exact S7-300 CPU and panel against the device lists and license STEP 7 and WinCC Comfort separately.

On this page
  1. One shell, two licensed components
  2. Check the panel and the device catalog
  3. Import the STEP 7 V5.x project
  4. Migrate the WinCC flexible 2008 project
  5. Sort the licenses
  6. The migration sequence, in order
  7. Verify, then decide
  8. Questions asked

One TIA Portal installation replaces both of the packages you use today, but it does not merge them into one license, and your two project types move through two different functions. The STEP 7 Professional V5.5 project is imported into TIA Portal, not opened. The WinCC flexible 2008 project is migrated, and the newest TIA Portal releases no longer offer that migration, so the route to a current version runs through an intermediate release. Before you spend anything, confirm three things: your exact S7-300 CPU is supported for import, your exact panel appears in the target release's HMI device catalog, and you know which licenses the work needs. The upgrade itself is worth it, because the panel cannot be programmed any other way, and the checks below decide the rest.

One shell, two licensed components #

TIA Portal is a single engineering shell, and STEP 7 and WinCC sit inside it as separately licensed components. STEP 7 in TIA Portal takes over the S7-300 and S7-400 work you do in V5.5, and it is the only environment for the S7-1200 and S7-1500 CPU families; the S7-1200 documentation states that STEP 7 configures and programs that CPU, including serving projects to earlier V4.x devices. The WinCC side splits by hardware: the WinCC Basic functions included with STEP 7 program Basic Panels, while Comfort Panels require a WinCC Comfort engineering license. So one TIA Portal version does replace both of your current packages, but the panel you are buying forces the WinCC Comfort purchase no matter how you handle the STEP 7 question.

Check the panel and the device catalog #

Read the exact panel designation, then read the engineering release its own documentation names. For the first Comfort generation that requirement was printed as WinCC Comfort V11 SP2. A later TIA Portal release also programs that panel on one condition: the panel must be listed in that release's HMI device catalog. Check the supported-device entry for the exact designation before you install anything, because support is decided per model, not per panel family. If the model is missing from the list in your release, the fix is a service pack, a newer release or a different panel, and the same check-and-fix sequence is described in when an HMI model is missing from the programming software. If the mapping between software packages and panel families is unclear, which HMI software works with which HMI panel hardware lays it out.

Import the STEP 7 V5.x project #

TIA Portal has an import function for STEP 7 Classic projects; there is no path that simply opens a V5.5 project. Work on a copy and keep the V5.5 original untouched as the rollback.

Check the CPU first. Some older S7-300 CPUs are not supported for import, so a general statement that TIA Portal supports S7-300 settles nothing. The exact CPU designation does. A CPU 317-2 DP moved from STEP 7 V5.5 to TIA Portal V17 in one documented migration, which shows the check is passable; your CPU's entry in the release's supported-device list is the decision.

Run the import against the copy, then treat the result as a draft. Compare the converted hardware configuration, blocks, symbols and connection settings with the source project, and clear every diagnostic the import reports. With STL and networking in the program, a clean import log proves the project entered, not that it behaves identically; compile and test supply that proof.

Migrate the WinCC flexible 2008 project #

Siemens' WinCC Migration Guide documents the procedure for moving a STEP 7 V5.x and WinCC flexible 2008 project into WinCC (TIA Portal), and it is the reference to follow step by step.

One documented fact decides the route: the TIA Portal V20 release documentation states that migrating WinCC flexible projects is no longer supported. A 2008 project therefore cannot enter the newest releases directly. Migrate in an intermediate release that still offers the function, save the converted project, then open it in your target release and accept the project upgrade, following any intermediate steps the portal names.

Then choose combined or standalone. If the S7-300 stays on its classic program, migrate the HMI project on its own and configure the S7-300 connection inside the HMI project; the controller never changes. If both projects move together, the guide's combined procedure covers it in one pass.

Either way, read the migration log as a work list: screens, tag connections and flagged project features need review and manual correction. Compile after the corrections and do not transfer until the compile is clean.

Sort the licenses #

Two entitlements are in play. The Comfort Panel needs a WinCC Comfort engineering license in the release you install. The PLC work needs STEP 7, and the COMBO license is the practical answer there: it covers classic STEP 7 and TIA Portal STEP 7 in one license, so V5.5 keeps working on the same PC while you build in TIA. In one documented licensing example, the upgrade to TIA Portal STEP 7 Professional carried order number 6ES7822-1AA23-0YE5.

Worked example: one engineering PC, both jobs. Held as three separate entitlements, classic STEP 7 Professional, TIA Portal STEP 7 and WinCC Comfort would cost three licenses. The COMBO STEP 7 license counts as classic and TIA in one, so the same PC needs 3 − 1 = 2 purchases: the COMBO upgrade plus WinCC Comfort. You can also prove both device checks before spending anything, because the manufacturer offers TIA Portal as an evaluation download with a time-limited trial license, which is enough to run the import, the migration and both compiles.

The migration sequence, in order #

  1. Archive both source projects. Everything after this step runs on copies.
  2. Write down the exact CPU designation and the exact panel designation. Those two strings decide every support check that follows.
  3. Install the target TIA Portal release with STEP 7 and WinCC Comfort licensed, or start with the evaluation download and its trial license.
  4. Check the CPU and the panel against that release's supported-device lists. If either is absent, stop and change the release or the hardware; a project change cannot fix an unsupported device.
  5. Import the STEP 7 project copy if the PLC is moving, and clear the import diagnostics. Skip this step if the S7-300 stays classic, and configure the controller connection in the HMI project instead.
  6. Migrate the WinCC flexible 2008 project, combined or standalone, in a release that still offers the migration, then upgrade the project to the target release.
  7. Work through the migration log, correct screens and connections, and compile both projects. Resolve every error and judge every warning that touches hardware, communications or screens.
  8. Test before any production transfer. Testing HMI simulation against a live PLC shows the bench setup, and validating HMI variables during a software migration covers the tag checks.

One safety gate belongs here: a project transfer overwrites the panel's runtime project and resets retained variable values, so take the cutover in planned downtime, not over a running line.

Verify, then decide #

Keep the untouched V5.5 and flexible 2008 sources until the converted projects have passed commissioning on the machine: screens show the right values, operator commands act on the right addresses, and a full shift runs without an unexplained fault. Then the decision, case by case:

  • CPU not importable and the PLC stays V5.5: hold a COMBO license, migrate only the HMI project, and connect the new panel to the classic controller. The panel upgrade succeeds without touching the program.
  • CPU importable: import, verify against the source, and run both projects in one TIA Portal environment; retire the classic installation once commissioning passes.
  • Target release rejects the flexible project: migrate in the intermediate release that accepts it, save, and step the project up to the target.
  • Panel missing from the device catalog: change the release or the panel before buying. The project cannot be the fix.
  • All checks pass: make the purchase, run the sequence, and V5.5 and WinCC flexible 2008 leave the bench for good.

Questions asked

Do I have to convert the PLC project if only the panel is being replaced?

No. The HMI project migrates on its own and the S7-300 connection is configured inside the migrated HMI project, so the controller keeps running its untouched STEP 7 V5.5 program. The only PLC-side requirement is that the connection in the HMI project matches the CPU's rack, slot and network address. This is the standard route when the CPU is not importable or the line cannot take a controller project change.

Why does the WinCC flexible migration fail in the latest TIA Portal release?

Because the function was removed. The TIA Portal V20 documentation states that migrating WinCC flexible projects is not supported, so a 2008 project cannot enter the newest releases directly. Migrate in an intermediate release that still offers it, save the converted project, then open it in the target release and accept the upgrade. Both versions can sit on the same engineering PC.

How do I prove my S7-300 CPU is supported before buying anything?

Two checks. First, read the exact CPU designation from the hardware configuration in STEP 7 V5.5 or from the order number printed on the module, not just the words S7-300. Second, look that designation up in the supported-device list of the TIA Portal release you plan to install. The evaluation download with its trial license then lets you run the actual import and read the diagnostics before any purchase.

What happens to Multi Panel projects in this migration?

They follow the same path. Multi Panels and Touch panels were both configured in WinCC flexible 2008, so their projects take the same intermediate-release route into TIA Portal. Check the old panel itself against the device catalog as well: a legacy panel that has no entry there cannot be the transfer target, so the migrated project is re-targeted to the new panel and the screens are re-checked on it.

Keep reading

  • Troubleshooting

    E-Designer to Exter Project Conversion and Transfer Path

    E-Designer cannot download to an Exter T150: the terminal accepts applications only from Information Designer. Convert the .mpa project through the maker's conversion service or a licensed Information Designer seat, verify the target, driver and objects, then export a .Dat project transfer file to USB or CF card that the T150 loads automatically. Replace the terminal with current hardware only when the terminal itself is the failing part.

    HMI and touchscreens

  • Troubleshooting

    Fixing an HMI Project That Fails After a Git Clone

    The clone is broken because a referenced bitmap .PLK was never committed, not because of an ignore rule. Read the HMI Output tab for the exact filename, prove the file is untracked with git check-ignore followed by git ls-files, then restore and commit it and re-test from a clean clone. Track the .tgt and .def files for the HMI BIOS version as well.

    HMI and touchscreens

  • How-to

    How to Recover an HMI Program When the Source File Is Lost

    If an editable backup was stored on the HMI at download time, upload it and open it as a project. If the terminal holds only the compiled runtime, no upload can recreate the source: document every screen and tag behavior from the running unit, rebuild against the controller project, and convert the runtime only where the vendor documents a path.

    HMI and touchscreens

What the TiSTAR DEU does when you migrate to WinCC