TIA Portal Version Reference: Compatibility, Migration, Licensing, and Field PG Setup

Siemens Totally Integrated Automation Portal (TIA Portal) is the unified engineering framework for SIMATIC S7-1200, S7-1500, S7-300/400, ET 200, SINAMICS, SIMOTION, and SIMATIC HMI families. Because TIA Portal is version-bound, with explicit forward and backward compatibility rules, a working version history is essential before any new Field PG purchase, project hand-over, or migration project. As of mid-2026, TIA Portal V20 Update 6 is the latest released version, with V21 in the qualification cycle. This reference consolidates the official compatibility matrix, migration paths, licensing levels, Windows operating-system support, and Field PG selection criteria for the practicing automation engineer.

1. Current TIA Portal Release Status

The official update inventory is published by Siemens as KB document 109963851 – TIA Portal V20 Updates. The entry should be re-checked at procurement time because Siemens periodically ships cumulative Updates between Service Packs.

2. Licensing Levels and Downward Compatibility

TIA Portal is sold in four discrete licensing tiers. A license purchased at a given tier authorizes the installation of all lower-numbered major versions at the same tier:

A V15 Professional license, for example, permits installation of V13, V14, and V15 Professional. It does not open a V17/V18/V19/V20 project because those are forward-only and require a newer license. Two practical consequences follow:

1. Always archive a project as a service contract begins. Once the project is closed and the original hardware is shipped, only the binary .zap15 / .zap17 / .ap20 archive can be reopened. Without that archive, the project cannot be moved forward to a newer TIA Portal version at all.
2. Forward compatibility is one-way. TIA Portal V15 cannot save a V14 project in V15 native form and V14 cannot open it. A V13 SP1 project cannot be opened in V15 directly; the conversion chain is enforced.

3. Project Version Compatibility and Migration Paths

3.1 Opening Older Projects

A project can be opened in TIA Portal if and only if its source version is greater than or equal to the oldest version the editor supports. The official rule set as of V20 is summarized in the table below.

3.2 V21 Migration Gate

According to the V21 "What's new" documentation, the editor will only upgrade projects and libraries that are V14 SP1 or newer. Any project created in V13 or earlier must first be migrated to at least V14 SP1, and that intermediate V14 SP1 file must be archived, before V21 will accept it.

3.3 Migration Tool Mechanics

The TIA Portal migration tool is not a separate executable. It is invoked from inside the editor: Project → Migrate project → Migrate to current version. The tool performs schema, firmware, and library migrations. Hardware configuration blocks that reference obsolete modules are flagged with a warning and the offending module is replaced by a placeholder pending manual re-selection. Library references that no longer exist are dropped with a warning log entry that can be exported to .csv for audit purposes.

1. Verify that the source backup is restorable on the source version of TIA Portal (open, compile, do not download).
2. Make a copy of the .zapxx archive; never migrate in place.
3. Open the project in the target version. The "Migration" dialog is shown automatically the first time.
4. Review the migration log; resolve hardware substitutions, missing libraries, and CPU firmware compatibility entries.
5. Compile the project. A clean compile on the target version is the migration acceptance criterion.
6. Commit the migrated archive to version control (e.g., TIA Portal project server, SVN, or Git LFS) with a tag such as project_v11_migrated_v20.

4. Operating System Support

Field engineers frequently find that the latest cumulative Windows updates break TIA Portal V13 SP2 – V15 stability. The proven mitigation is to defer Windows 10 feature updates and to use a dedicated engineering image that is patched only with the approved Siemens-compatible update set. A Field PG is the practical solution because Siemens ships a pre-imaged, locked-down Windows installation with TIA Portal and the matching device drivers.

5. Trial Version Limitations

A TIA Portal trial is functionally identical to a fully-licensed installation. The only enforced restriction is the use-time clock: 21 days from first start, after which the editor refuses to start. Trial-mode sessions can perform the following operations without restriction:

• Compile and download to any SIMATIC PLC supported by the trial version
• Online diagnostics, force tables, trace recordings
• PLCSIM simulation
• Project migration
• HMI download to Comfort Panels and WinCC Runtime
• Multiuser server / GIT integration

The trial does not impose a project-size cap, a tag-count limit, or a hardware-list restriction beyond what the license tier (Basic / Professional / Comfort / Advanced / Professional) would normally enforce when the trial is launched. Engineers commissioning or troubleshooting legacy systems with no active license can therefore use a 21-day trial as a stopgap, provided the start date is recorded so that the next trial period can be re-armed on a different physical or virtual machine.

6. Field PG Selection for TIA Portal V20

For a portable engineering platform that must hold the latest TIA Portal, the recommended Siemens product is the Field PG M6 (6th generation). Key selection criteria that the engineer must verify against Siemens Industry Online Support:

Other commercial-grade laptops (Lenovo ThinkPad T-series, Dell Latitude, HP EliteBook) can run TIA Portal V20 if the platform is on the Siemens compatibility list for the corresponding update. Always cross-check the SIMATIC IPC compatibility KB before procurement; non-Field-PG machines frequently fail the S7-1500 firmware download tool because of signed-driver restrictions on the Ethernet adapter.

6.1 Image and License Setup Procedure

1. Order the Field PG with the latest SIMATIC TIA Portal pre-installation. Siemens provides a recovery image that includes Windows and the matching TIA Portal version.
2. Activate the license through the Automation License Manager using the License Key sent with the order, or transfer a floating license from the company license server.
3. Run Windows Update, but only until the most recent cumulative update tested by Siemens is installed. Document the date.
4. Install the latest TIA Portal V20 Update from KB 109963851.
5. Run the TIA Portal Administrator to register the editor and connect to the company project server, if applicable.
6. Verify the installation by opening an empty project, dropping a CPU onto the device configuration, and downloading to PLCSIM. A successful download is the acceptance criterion.

7. Practical Field-Use Considerations

7.1 Hardware Compatibility Lock

TIA Portal refuses to download a project whose CPU firmware is older than the editor's minimum. The compatibility list is part of the device support package (HSP) that ships with each Update. When the field engineer's TIA Portal is newer than the firmware in the panel (e.g., V20 against a V14 SP1 firmware CPU), the fix is to add the matching HSP or to install the older TIA Portal side-by-side. A V15 license authorises side-by-side installation of V11, V13 SP2, V14, V14 SP1, and V15 without buying an additional license — the older versions are simply installed with the same license key.

7.2 Backup Discipline

The single most common reason an old TIA Portal project cannot be recovered is the absence of the project archive. The .zap15 / .zap17 / .ap20 file produced by Project → Archive is the only durable, version-bound copy. Database files left in the user's working folder are not portable: if the source editor is no longer installed, they cannot be re-attached. Adopt a working rule: any TIA Portal project that is sent to a customer, archived to a vault, or shipped to a sister company is archived and version-tagged before transmission.

7.3 Multiuser Engineering

From V14 SP1 onward, TIA Portal supports a server-based multiuser mode in which multiple engineers check out / check in objects in a shared project. From V17 SP1, the multiuser server can be replaced with a Git-based workflow, but the TIA Portal multiuser server is still required for the SIMATIC PCS 7 use case. A Field PG that is to be used for multiuser engineering must be a member of the company VPN and have a stable connection to the multiuser server because the editor performs periodic lock-refresh transactions.

8. Migration from TIA Portal V15 and Earlier

Engineers running long-life V15 installations frequently need a direct path to V20. The shortest chain for a V15 project is V15 → V15.1 → V16 → V17 → V18 → V19 → V20. The chain is mandatory; skipping versions results in a "Project cannot be migrated because intermediate format is missing" error. The full chain is therefore:

1. Archive the V15 project.
2. Open the project in TIA Portal V15.1; if a V15.1 license is not available, install V15 side-by-side and open the V15 archive in V15 first. Then perform a "Save as new version" inside the editor (or use the migration tool of the V15.1 install).
3. Repeat for V16, V17, V18, V19, V20.
4. At each step, archive the intermediate version, and run a full project compile to catch hardware substitution or library-missing issues early.

Migration cost in engineering hours is non-trivial. A medium S7-1500 project (≈ 300 FB instances, 80 HMI screens) typically requires 8–16 hours of mechanical fix-up work. PCS 7 projects with many CFC/SFC charts are heavier and benefit from a V14 SP1 → V20 jump to skip intermediates; PCS 7 V9.x projects are the boundary case where intermediate V17 or V18 must be used as a stepping-stone.

9. Troubleshooting Common Upgrade Issues

10. Summary: Recommended Approach for a New Field PG

1. Order a Field PG M6 with the SIMATIC IPC TIA Portal pre-installation (latest available image).
2. Install the latest TIA Portal V20 Update (Update 6 as of 06/2026) from the Siemens Industry Online Support entry referenced above.
3. Activate the license via Automation License Manager.
4. Verify the build by downloading a small test project to PLCSIM and to a physical S7-1500 CPU.
5. For any project older than V14 SP1, install the matching older TIA Portal version side-by-side (no extra license required under the V15+ licensing rule), and migrate through the official chain to V20.
6. For a V21 upgrade, ensure that the source project is at least V14 SP1; otherwise the V21 "What's new" rule will refuse the upgrade and the project will have to be migrated stepwise to V14 SP1 first.
7. Document the as-built configuration: editor version, Update level, license key, OS build, and last verified compile. This record is essential for the next project hand-over and for the next engineer who picks up the same Field PG.