STEP 7 Classic to TIA Portal: What Changes for the Programmer

You have programmed in SIMATIC Manager for 10 or 20 years. You know STEP 7 Classic inside out. Now you open TIA Portal for the first time, and everything is in a different place. This guide is not a TIA Portal tutorial — it is a map of the 15 things that will confuse, frustrate, or delight you most as an experienced STEP 7 programmer.

1. One Window Instead of Five#

STEP 7 Classic: SIMATIC Manager, HW Config, Symbol Editor, LAD/STL/FBD Editor, and WinCC flexible — five separate applications.

TIA Portal: Everything in one window. Project tree on the left, editor in the center, properties and catalog on the right. It takes 1–2 days to stop looking for the "other application."

2. Tags Are Created Inline#

STEP 7 Classic: Create symbols in the separate Symbol Editor before using them. If the symbol does not exist, you type the absolute address.

TIA Portal: Create tags directly while programming. Type a name in the code, TIA Portal asks if you want to create it. Tags are managed in "PLC tags" in the project tree — no separate application.

Impact: Faster workflow, but be disciplined — it is easy to create duplicate or inconsistently named tags.

3. Data Blocks: Optimized Access Is the Default#

STEP 7 Classic: All DBs use standard (absolute) access. DBW0, DBW2, DBD4 — every variable has a byte address. Adding a variable shifts all subsequent addresses.

TIA Portal (S7-1500): Optimized access is the default. Variables are accessed by name only — no byte addresses. Adding or removing a variable does not affect anything else.

The catch: If you migrate a STEP 7 Classic project, the migrated DBs are set to "Standard" for compatibility. You must manually switch to "Optimized" per DB and convert all absolute references to symbolic.

What breaks: PUT/GET communication, OPC DA (classic), and any external system that accesses DB data by absolute byte address. These need reconfiguration when switching to optimized DBs.

4. Compilation Is Automatic#

STEP 7 Classic: You compile each block individually. If you forget to compile a block, the online version does not match your offline edit. This causes mysterious behavior.

TIA Portal: Compilation happens automatically before every download. TIA Portal compiles the entire program and identifies all changed blocks. You cannot accidentally download an uncompiled block.

5. Download Identifies Changes Automatically#

STEP 7 Classic: You select which blocks to download. If you modified 5 blocks but only download 3, the remaining 2 are out of sync.

TIA Portal: Download shows all changed blocks. You confirm the list and download everything at once. Much harder to leave the PLC in an inconsistent state.

6. Online/Offline Comparison Is Built In#

STEP 7 Classic: Comparing online (PLC) vs. offline (PC) requires manual effort. Many programmers never do it — leading to the situation where nobody knows which version is current.

TIA Portal: Visual comparison is built in. Right-click a block → "Compare offline/online." Differences are highlighted line by line.

7. STL/AWL Is Second-Class on S7-1500#

STEP 7 Classic: AWL is a first-class language. Many experienced programmers prefer it for its compactness.

TIA Portal (S7-1500): STL/AWL runs in emulation mode on S7-1500. It is 10–30% slower than native SCL or LAD/FBD. Main OBs on S7-1200 cannot use STL at all. Siemens clearly positions SCL as the replacement.

What to do: Keep existing AWL code for initial migration (it works in emulation). Plan to convert performance-critical blocks to SCL over time.

8. Cross-References Are Better — But Moved#

STEP 7 Classic: Ctrl+Alt+Q opens cross-references. Every STEP 7 programmer's muscle memory.

TIA Portal: Cross-references are in the Inspector window (bottom panel) under the "Cross-reference" tab. Select any variable and see all usage locations. The information is richer (shows block, network, and line), but the keyboard shortcut is different.

9. Watch Tables Are More Powerful#

STEP 7 Classic: VAT (Variable Table) with limited formatting options.

TIA Portal: Watch tables support comment lines for structuring, multiple display formats per variable, and triggering on specific conditions. More powerful but takes time to learn.

10. Firmware Must Match the Project#

STEP 7 Classic: Relatively forgiving about firmware versions. A program compiled for one firmware usually works on another.

TIA Portal (S7-1500): The project specifies a firmware version. The CPU firmware must be equal to or newer than the project version. Uploading a program requires the exact TIA Portal version it was created with. Keep VMs with matching TIA Portal versions.

11. PLCSIM Is Integrated#

STEP 7 Classic: S7-PLCSIM is a separate installation and application.

TIA Portal: PLCSIM is integrated. Click "Start simulation" and a virtual PLC starts. PLCSIM Advanced (separate license) adds advanced features like API access.

12. Trace Function (S7-1500 Only)#

STEP 7 Classic: No trace recording available.

TIA Portal: Record variable values over time — like an oscilloscope for PLC variables. Invaluable for debugging timing issues, intermittent faults, and understanding process behavior. This alone is worth the migration for many programmers.

13. Project Versioning Is Version-Locked#

STEP 7 Classic: Projects are reasonably backward-compatible between V5.x versions.

TIA Portal: A V16 project cannot be opened in V15 — only upward migration. This means your entire team must use the same version. Plan for this before starting a multi-engineer project.

14. Resource Requirements Are Higher#

STEP 7 Classic: Runs comfortably on a 10-year-old laptop.

TIA Portal: Minimum 8 GB RAM, recommended 16 GB+. SSD is almost mandatory — HDD performance is painful. A powerful workstation makes a noticeable difference. Budget for new hardware when planning the migration.

15. It Gets Better After 2 Weeks#

The first week in TIA Portal is frustrating. Everything is in a different place. The second week, you start appreciating the integrated environment. By week three, going back to STEP 7 Classic feels like going back to the 1990s. This is the consistent experience reported by thousands of engineers who have made the transition.

How PLCcheck Pro Helps the Transition#

PLCcheck Pro bridges the knowledge gap:

• Analyzes your STEP 7 Classic program before migration
• Documents every block so the TIA Portal team understands the code
• Identifies AWL blocks that should be prioritized for SCL conversion
• Generates a migration complexity report

Analyze your STEP 7 program before switching →

Frequently Asked Questions#

How long does it take to become productive in TIA Portal?

2–4 weeks for an experienced STEP 7 Classic programmer. The concepts are identical — it is the workflow and UI that change. The Siemens Programming Guideline (Document 81318674) is an excellent reference for TIA Portal best practices.

Can I keep using STEP 7 Classic for S7-300/400?

Yes. STEP 7 V5.7 is still supported and available. For maintaining existing S7-300/400 systems without migration, STEP 7 Classic remains the right tool. Only new S7-1200/1500 projects require TIA Portal.

What is the biggest gotcha?

The firmware version lock. If you create a project in TIA Portal V17 and your colleague has V16, they cannot open it. And if your PLC has firmware V2.0 but your project targets V2.8, you must update the firmware before downloading. Plan for this.

---

Maintained by PLCcheck.ai. Last update: March 2026. Not affiliated with Siemens AG.