Migrating from STEP 7 Classic to TIA Portal: the practical

For Siemens TIA Portal V18+.

S7-300 and S7-400 projects in STEP 7 Classic V5.5 still run plants. Here is the actual path to TIA Portal — what migrates, what breaks, what to leave behind. This page is the working engineer's read — what the menu paths actually are in TIA Portal V18+, what the keystrokes do, and the mistakes that bite once the program is on a real CPU. We program S7-1200 / S7-1500 ourselves, daily; we are not a Siemens sales channel.

What this is and when you need it

S7-300 and S7-400 projects in STEP 7 Classic V5.5 still run plants. Here is the actual path to TIA Portal — what migrates, what breaks, what to leave behind. The walkthrough below is the same sequence we use when teaching this on the simulator. Every step names the exact menu path or keystroke; if a name has changed in your version of TIA Portal V18+, it is called out. The simulator runs the same logic flow without the licence cost — ladder, FBD, and ST in a browser, with a virtual CPU you can download to.

Walkthrough

1. Inventory the source project first

Open the STEP 7 Classic project and run Reference data > Cross-references. Note the OB count, FB count, FC count, total DBs, and which CPUs are in the rack. STEP 7 V5.5 SP4 or higher is required for migration; older projects must be opened and saved in V5.5 SP4 first. Hardware comms cards (CP 343-1, CP 443-1) need their firmware versions noted — TIA Portal expects specific minimums.

2. Run the Migration Tool

TIA Portal > Project > Migrate Project. Browse to the STEP 7 V5.5 .s7p file. The migration tool runs a pre-check, then converts. Output: a TIA Portal project in your selected directory plus a migration log file. Read the log — it lists every block that converted with warnings, every block that failed, and every CPU/HW component swap. Typical clean-conversion rate is 80–90% of blocks.

// Migration log shape (excerpt)
// FB10 Motor_Start: converted, 2 warnings
// FC50 PID_Wrapper: converted, 0 warnings
// SFC14 DPRD_DAT: replaced with DPRD_DAT_LEAN
// DB100: converted (non-optimised access)

3. Triage the warnings

Common warnings: SFC14/SFC15 PROFIBUS reads replaced with optimised equivalents (action: test the new SFC behaviour); standard libraries (DI/DO range checks) replaced with TIA Portal versions that have different parameter signatures (action: rewire FB calls); absolute addressing (M0.0, DB10.DBX0.0) preserved but flagged (action: convert to symbolic over time, not all at once).

4. Test in simulation before hardware

TIA Portal ships with PLCSIM Advanced (S7-1500) or PLCSIM (S7-300/400 and 1200). For a STEP 7 -> TIA Portal migration where the target stays S7-300, use S7-PLCSIM in TIA Portal — load the migrated project, watch for stop-mode errors. Common stop trigger: a timer that worked in V5.5 with implicit BCD now needs explicit IEC timer parameters.

5. Plan the on-site cutover

TIA Portal can download to an S7-300 or S7-400 over the same MPI/PROFIBUS/Ethernet route STEP 7 used. Take a backup of the running CPU (Online > Upload from device) before any download. Schedule cutover during a planned outage — a fresh download from TIA Portal will rewrite all DBs, so retentive memory must be saved and restored or the running state is lost.

Common mistakes

• Assuming the migrated project will run on the first download — testing in PLCSIM first catches at least one timer or comparator subtlety per project
• Ignoring the migration log warnings and only fixing the errors — the warnings are where the runtime surprises hide six months later
• Skipping the source-project save in V5.5 SP4 first — TIA Portal's migrator silently mishandles older formats and the conversion looks clean but isn't
• Cutting over during production hours assuming retentive DBs survive — they do not without an explicit upload-then-restore step

Each of these mistakes shows up in real projects every week. The simulator catches the first three at compile time; the fourth one only surfaces on hardware, which is why we recommend running the cert packs against a real CPU once you have completed the curriculum modules.

How this fits the broader curriculum

Migrating from STEP 7 Classic to TIA Portal: the practical path is one of the building blocks. The full Siemens curriculum on the simulator covers: programming-language fundamentals (ladder, FBD, ST), tag and variable scope, HMI tag binding, comms setup (Profinet / EtherNet/IP / Modbus depending on the platform), and the brownfield troubleshooting pathway. Each is its own module with worked examples and a portfolio piece. The cert packs at the Pro tier align to the ISA CCST exam content outline. Reference: isa.org.

For the platform-pick decision — when Siemens is the right call versus a different brand — see the brand hub. For region-specific context on where Siemens dominates the SA install base, see the relevant city pages under /brands/siemens/training-in-* and the sector pages under /industries.

Where this sits in a working week

A technician who has finished this module typically spends the next three to four working days running the same logic flow on hardware. The simulator's value is the dry run — getting the keystrokes and the IDE conventions into muscle memory before you sit down with a live CPU. The first time you build this on hardware, expect the IO mapping and the addressing conventions to slow you down for a session or two; the simulator's project tree mirrors the same shape so the transition is short.

The full Siemens curriculum runs roughly 60 to 100 hours of focused practice. That breaks into bit logic and timers in the first 20 hours, FBs and structured data in the next 20, comms and HMI in the next 20, and a portfolio piece in the last block. Pace yourself — three or four hours per session, four sessions a week, and you finish in eight weeks. Most of our learners report that the bottleneck is not understanding the IDE, it is building reflex around the conventions: where Siemens expects you to put state, how it scopes variables, what naming patterns the OEMs in the sector use.

Vendor reference

Siemens's own documentation is the canonical reference once you are working on real hardware: Siemens Industry Online Support. The simulator covers the basics; the vendor docs cover everything specific to a hardware revision, a firmware update, or a CPU-specific quirk. Bookmark both. The IEC 61131-3 standard that governs all the Siemens programming languages is at iec.ch.

What we don't claim

This site is not SAQA-registered, not MerSETA-accredited, and not an NQF-registered qualification provider. Our completion certificates are course-level only — they describe what you covered, not an NQF Level X qualification. The CCST cert from ISA is the portable industry credential we recommend; we are not an ISA cert delivery partner either, but our cert packs are CCST-aligned. The walkthrough above is brand-specific because Siemens's tooling has its own conventions; do not assume the same menu paths exist in another brand's IDE.

How to start

You can be running migrating from step 7 classic to tia portal: the practical path in the simulator in 5 minutes. Free tier covers the basics, no card, no install. Once you are 20 minutes in you will know whether the platform fits how you learn. The full Siemens curriculum is the Basic tier (USD 12 / month). The cert packs and portfolio export sit in the Pro tier (USD 29 / month). For institutional buyers — TVET colleges, private training providers, in-house engineering training departments — the bulk-licence option is the Teams tier, USD 199 per seat per year, minimum 5 seats. The training-centres page has the institutional pitch and the contact form.

Honest expectations on the local job market

Petrochem, mining, FMCG, automotive, and water-utility sectors all carry Siemens install bases somewhere in their stack. Knowing the IDE conventions on this page does not get you a job by itself; it gets you past the first technical screen. The portfolio piece — a working program you built yourself, with a wiring track, a tag list, an HMI screen, and a short README explaining the design choices — is what lands the second interview. The simulator's portfolio export bundles all of that into a single folder you can hand a hiring engineer. Recruiters in this space skim the README first; if your design choices are coherent, they read the code.

Load-shedding has reshaped what gets built first in Siemens programs across SA. Power-recovery patterns — controlled shutdown on UPS hold, state recovery from retentive memory, sequenced restart of motor groups — now belong in the same module as the basics. Migrating from STEP 7 Classic to TIA Portal: the practical path fits into that shape: every line of code you write needs to consider what state the controller is in when it powers up after a 2.5-hour cut, not just what state it is in when running. The simulator's restart-from-cut mode lets you exercise this without bricking real hardware.