TIA Portal Version Compatibility: A Practical Guide Before You Upgrade

“Can I open this project?” is the first question of every service call that involves someone else’s machine. TIA Portal’s compatibility rules are strict, and knowing them saves hours — or a failed intervention at 2 a.m.

The three rules that matter

1. TIA Portal opens projects from older versions, never newer. A V17 project opens in V18/V19 (it will be upgraded — one way, no return). V19 projects do not open in V18. There is no “save as older version” for projects, only for libraries in limited cases.
2. Upgrading the project does not upgrade the PLC. A V15.1 project upgraded to V18 still compiles for the CPU’s configured firmware. You can keep old firmware in a new Portal — this is the escape hatch that makes upgrades low-risk.
3. CPU firmware sets the feature ceiling, Portal version sets the tooling. New instructions and features are gated by firmware version; the Portal version mostly determines which firmware versions you can configure and which editors you get.

What this means for a machine builder

• Ship the project archive with the machine (.zap17, .zap18, …). The extension tells the service engineer which Portal to bring before leaving the office.
• Pin one Portal version per machine generation, and upgrade deliberately — not because a laptop happened to have a newer install. A mixed fleet where each machine was “upgraded when touched” becomes unmaintainable within a few years.
• Multiple Portal versions coexist happily on one PC. A service laptop with V15.1, V17 and V19 side by side is normal practice; the licenses are backwards-compatible (a V19 license runs older versions).

Upgrade strategy that has never burned us

1. Archive the original project (keep the old .zap forever).
2. Upgrade the project in the office, compile, and diff the compilation output — not on the machine.
3. Keep CPU firmware unchanged on the first visit; only raise firmware when a feature or bugfix demands it, as its own planned step with a back-out path.
4. After site acceptance, archive again and record Portal version + firmware in the machine dossier.

FAQ

Can I downgrade a project? Practically, no. You rebuild: copy blocks through a library or re-generate sources. This is why accidental upgrades are expensive — Portal warns you, take the warning seriously.

Do WinCC (HMI) panels follow the same rules? The one-way project rule is the same, with an extra trap: the panel’s runtime version must match what the project compiles for. Older Basic Panels cap the usable WinCC version regardless of your Portal.

Is there a compatibility matrix? Siemens publishes one in Industry Online Support (search “TIA Portal compatibility”). Bookmark the entry for your exact CPU family instead of trusting memory.

Zone Otomasyon programs and services Siemens TIA Portal systems across S7-1200/1500 generations. Planning a migration from STEP 7 Classic or an old Portal version? Talk to us before you touch the running machine.