S7-200 to S7-1200 Migration Tool: TIA Portal V11 Conversion

David Krause12 min read
S7-1200SiemensTutorial / How-to
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview

The legacy S7-200 family (CPU 212 through CPU 226, plus the later S7-200 SMART series) is still installed in thousands of small machines running STEP 7-Micro/WIN V4.x project files. When these machines require a modern replacement controller, the engineering question is no longer if you migrate, but how you get the existing Micro/WIN logic onto an S7-1200 in the shortest possible time without introducing logic errors.

Siemens published a dedicated S7-200 to S7-1200 Conversion Tool that performs the bulk of the translation automatically. The tool is hosted inside TIA Portal and reads a compiled Micro/WIN program (.mwp) exported through STEP 7-Micro/WIN. The tool is not distributed as a standalone executable and is not bundled with every TIA Portal release. It shipped with TIA Portal V10.5 and TIA Portal V11 (including V11 SP2). In TIA V12 and later the conversion menu entry was removed, so projects originating in those newer releases cannot directly accept Micro/WIN source. The supported two-stage path is:

  1. Convert Micro/WIN V4.x project → TIA Portal V10.5/V11 (S7-1200 image)
  2. Open that TIA V10.5/V11 project in TIA V13/V14/V15/V16/V17 and let the standard TIA migration handle the version upgrade

The converter handles the heavy lifting (tag map creation, I/O address mapping, ladder → FBD/ST translation) but it does not produce a 1:1 equivalent program. Expect manual cleanup, retag, instruction replacement, and library rework after the automated pass. For small programs (under ~200 networks) many engineers find that a manual rewrite is faster than cleanup. For programs above ~500 networks the tool saves real engineering hours.

Prerequisites

Before launching the conversion tool, confirm every component below is installed. The tool will refuse to start if any prerequisite is missing.

Component Required Version Notes
STEP 7-Micro/WIN V4.0 SP9 (build 4.0.9.25) or later V4.x service pack Must be installed before TIA Portal so the program can export the project file format the converter reads
TIA Portal V10.5 or V11 (Basic or Professional) Conversion Tool is integrated; do not attempt with V13+
TIA Migration Tool plug-in Matches the TIA V10.5/V11 build Adds the File > Migrate project entry
S7-200 to S7-1200 Conversion Tool V1.x for the chosen TIA version Downloaded separately from the Siemens Industry Online Support entry
Operating system Windows 7 SP1 / Windows 10 (per TIA V11 matrix) TIA V11 does not officially support Windows 11; use a Windows 10 21H2 VM if needed
Administrator rights Local admin required for install Both Micro/WIN and TIA must run in the same user context
Important: Micro/WIN and TIA Portal must be installed on the same machine. The converter spawns Micro/WIN in headless mode to read the project; a network install of Micro/WIN on a different PC will not work.

TIA Portal Version Compatibility Matrix

TIA Portal Version Conversion Tool Available? Conversion Path
V10.5 Yes (built-in) Direct Micro/WIN → TIA V10.5
V11 / V11 SP1 / V11 SP2 Yes (plug-in) Direct Micro/WIN → TIA V11
V12 / V12 SP1 Removed Convert to V11 first, then standard TIA upgrade to V12
V13 / V13 SP1 / V13 SP2 Removed Convert to V11 first, then upgrade to V13
V14 / V15 / V15.1 Removed Convert to V11 first, then chain-upgrade to target version
V16 / V17 / V18 Removed Convert to V11 first, then chain-upgrade to target version

The two-stage approach (V11 → V13 → V14 → V15 → V16 → V17) is the only supportable path once the source project was created in V10.5 or V11. Each TIA version upgrade is handled by the built-in Project > Migrate command and requires no additional plug-in.

Download the Conversion Tool

The official Siemens conversion tool is distributed as a self-extracting installer through the Siemens Industry Online Support. The entry number to search is 39878.

  1. Open Siemens Industry Online Support.
  2. Enter entry ID 39878 in the search box and navigate to the S7-200 to S7-1200 Conversion Tool download.
  3. Select the build that matches your installed TIA Portal version (separate installers exist for V10.5 and V11).
  4. Save the .exe to a local path with administrator rights.
  5. Verify the file checksum against the value published on the Siemens support page before running it.

The installer registers an entry under File > Migrate project > S7-200 project inside TIA Portal V10.5/V11. There is no start-menu icon because the tool is invoked exclusively from inside the TIA Portal shell.

Step-by-Step Conversion Procedure

1. Prepare the Micro/WIN Source

  1. Open the program in STEP 7-Micro/WIN V4.0 SP9.
  2. Compile the project (PLC > Compile or Ctrl + F9). Compilation must complete with zero errors. Warnings are acceptable but record them — they often become conversion warnings.
  3. Make a working copy (File > Save As) before any modification. The original must remain untouched in case the conversion fails.
  4. Close Micro/WIN. The converter launches its own Micro/WIN host; running Micro/WIN simultaneously will lock the project file.

2. Launch TIA Portal V10.5 or V11

  1. Start TIA Portal in administrator mode.
  2. Create a new project (Project > New) and add an S7-1200 CPU that matches the target hardware (CPU 1211C, 1212C, 1214C, 1215C, or 1217C DC/DC/DC or DC/DC/RLY variants).
  3. Configure the device configuration to mirror the I/O count of the S7-200 source. The converter does not resize the S7-1200; if the source uses more digital or analog points than the chosen CPU supports, address-mapped tags will be clipped.

3. Invoke the Conversion

  1. From the TIA Portal menu, select File > Migrate project > S7-200 project.
  2. In the dialog, browse to the saved Micro/WIN .mwp file.
  3. The tool launches an embedded Micro/WIN instance to read the source. A progress bar reports each conversion phase.
  4. When the wizard finishes, the converted blocks appear in the project tree under Program blocks. A conversion log file is written to %TEMP%\S7-200-to-S7-1200-Conversion\<timestamp>.log.

4. Review the Conversion Log

Open the log and capture every entry marked [WARNING] or [ERROR]. Categories that commonly appear:

Log Code Meaning Recommended Action
W0010 Unused symbol pruned None — informational only
W0023 S7-200-specific timer (TONR/TON/TOF) replaced with IEC_TIMER Review time base; S7-200 uses 100 ms, S7-1200 IEC timers use 1 ms
W0102 Subroutine call inserted as FB instance Verify instance DB was created and renamed
E0201 Counter type CTU/CTD/CTUD missing in target Manual rewrite required using IEC_CTU/CTD/CTUD
E0305 Unsupported instruction (e.g. HSC, PTO/PWM, NETR/NETW) Replace with S7-1200 native high-speed counter or PID instructions
E0410 Memory address out of range (e.g. source used VD50000) Move data into supported range (MB0..MB32767, DB1..DB32767)

5. Address Mapping Verification

The converter applies the default I/O mapping shown below. Verify every address manually because the converter does not validate against the selected CPU.

S7-200 Address Space S7-1200 Equivalent Conversion Behaviour
I0.0 .. I0.7 / I1.0 .. I1.7 %I0.0 .. %I0.7 / %I1.0 .. %I1.7 Direct 1:1
Q0.0 .. Q0.7 / Q1.0 .. Q1.7 %Q0.0 .. %Q0.7 / %Q1.0 .. %Q1.7 Direct 1:1
AIW0 .. AIW62 %IW64 .. %IW126 Offset shift to avoid conflict with on-board I/O
AQW0 .. AQW62 %QW64 .. %QW126 Offset shift
V0 .. V8191 (data block) Global DB, byte-addressed Renamed tags; verify symbol names retained
M0.0 .. M31.7 %M0.0 .. %M31.7 Direct 1:1
SM0.0 .. SM299.7 (special memory) System constants / tags Partial — see special handling section

Instruction Coverage and Limitations

The conversion tool covers the standard Micro/WIN ladder and FBD instruction set but does not translate every block. The following table summarises the conversion behaviour for the most common instructions.

Micro/WIN Instruction S7-1200 Equivalent Auto-Converted?
Normally Open / Normally Closed contacts Direct mapping Yes
Coil output (—( )—) Direct mapping Yes
Set / Reset coil (S/R) Direct mapping Yes
TON / TOF / TONR IEC_TIMER (TP / TON / TOF) Yes, but verify time base
CTU / CTD / CTUD IEC_Counter (CTU / CTD / CTUD) Yes
MOV_W / MOV_DW / MOV_R MOVE (LAD) or assignment (ST) Yes
ADD_I / ADD_R / SUB_I / MUL_I / DIV_I ADD / SUB / MUL / DIV Yes
BCD conversion No native equivalent No — manual rewrite
NETR / NETW (PPI networking) No native equivalent No — manual rewrite using PUT/GET or TSEND_C
HSC (high-speed counter modes 0..12) S7-1200 HSC channel Partial — hardware config only, mode must be re-selected
PTO / PWM PTO/PWM output on S7-1200 Partial — control block rewrite required
PID PID_Compact V2 Partial — auto-tuned values not transferred
USS protocol No native equivalent No — manual rewrite using USS library block
Modbus RTU master (MBUS_CTRL/MBUS_MSG) MODBUS_MASTER No — manual rewrite
Freeport (XMT / RCV) Point-to-Point configuration No — manual rewrite using Send_P2P / Receive_P2P
Data table pointer operations Indirect addressing with PEEK/POKE No — manual rewrite
Critical: Programs using PPI networking (NETR/NETW), USS drive protocol, or Freeport serial communications require a full manual rewrite. The conversion tool leaves these blocks as uncompiled stubs and the project will not build.

Manual Cleanup After Conversion

Even a successful automated conversion always needs the following manual cleanup pass before download. Plan 2 to 4 hours per 100 networks for the cleanup phase.

  1. Time-base audit: Search every IEC_TIMER block and confirm the PT input reflects the original time base (S7-200 TON uses 100 ms; S7-1200 IEC_TIMER uses 1 ms). Multiply S7-200 values by 100 to preserve timing.
  2. Special memory replacement: Common S7-200 specials have no S7-1200 equivalent. SM0.0 (always-on) → TRUE constant; SM0.1 (first-scan) → rising edge of "FirstScan" tag from system clock; SM0.5 (1 Hz clock) → CLK_1HZ from System and clock memory settings.
  3. Symbol table restore: The converter imports V-memory symbols as a global DB but renames the DB. Re-apply meaningful names from the original Micro/WIN symbol table.
  4. Subroutine call review: Each SBR (subroutine) becomes an FB with its own instance DB. Verify the instance DB was created; missing instances will compile but crash at runtime when the FB is called.
  5. Interrupt routine rewrite: INT_0, INT_1, INT_2 map to hardware interrupt OBs in S7-1200. Event priorities (edge direction, HSC channel, delay) must be reconfigured under Device configuration > Properties > Inputs/interrupts.
  6. Retag scan: Open every block in cross-reference and verify address references resolved to the intended tag. Pay special attention to V-memory offsets that may have collided with on-board I/O mapping.

Alternative Migration Strategies

When the official conversion tool is unavailable, or when the source program relies heavily on unsupported instructions, use one of the following strategies.

Strategy A — Direct Manual Rewrite

For programs under 200 networks with mostly standard contacts, coils, timers, counters, and math, manual rewrite is usually faster than conversion + cleanup. Estimated effort: 4 to 8 hours per 100 networks for an experienced STEP 7 engineer.

Strategy B — S7-200 SMART as Bridge

S7-200 SMART CPUs (SR20, SR30, SR40, SR60, ST20, ST30, ST40, ST60) are programmed with STEP 7-Micro/WIN SMART. Many sites already have installed SMART hardware, allowing a code-move without changing source format. Note that Micro/WIN SMART is not compatible with the S7-200 to S7-1200 Conversion Tool — they are different product lines.

Strategy C — Two-Stage via V11

The only Siemens-supported automated path is V11 conversion followed by TIA chain-upgrade. Install TIA V11 in a virtual machine, perform the conversion, then export the project and open it in the target TIA version. TIA's internal migration handles V11 → V13 → V14 → V15 → V16 → V17 with no manual work beyond re-confirming the hardware catalog.

Strategy D — LOGO! 8 as Replacement

For very small machines where the S7-200 was used as a smart relay, consider the LOGO! 8 (6ED1052-x*x*8) as a drop-in functional replacement. Programs port to LOGO! Soft Comfort V8 with minimal effort. The runtime and I/O count match many entry-level S7-200 applications.

Verification Checklist

Run the following checks before downloading the converted project to the S7-1200 CPU.

  1. Compile clean: Project must build with zero errors and zero warnings. Address every warning as if it were an error.
  2. Cross-reference review: Open Tools > Cross-reference and verify every address has a unique owner; duplicate ownership is the most common runtime fault after migration.
  3. Offline simulation: Use the S7-PLCSIM instance that ships with TIA Portal to execute the program against the simulator. Drive every input and confirm the corresponding output transitions correctly.
  4. Hardware configuration match: Open Device configuration and confirm the slot layout matches the real S7-1200 build. Signal modules, communication modules, and onboard I/O counts must match the physical hardware.
  5. Watchdog and OB1 cycle time: The S7-200 ran a single scan loop; the S7-1200 uses OB1 with a configurable maximum cycle time. Set the OB1 watchdog to 150 ms for typical machinery, 500 ms for process applications.
  6. Retain setup: Mark every tag that must survive a power cycle as Retain in the global DB. The S7-200 retained V-memory automatically; the S7-1200 must be configured explicitly.
  7. First-scan logic: Replace every SM0.1 reference with a proper first-cycle handler using "FirstScan" from the system clock tag or a rising-edge flag on the OB1 start.
  8. Analog scaling: Verify scaling blocks for AIW/AQW channels. The S7-200 default integer range (0..32000) differs from the S7-1200 default (0..27648). Insert scaling math where required.
  9. Communication blocks: Re-test any PPI, Modbus, USS, or Freeport communication against the live device. The automated converter cannot validate these blocks.
  10. Download & dry-run: Load the program to the S7-1200 in STOP mode, switch to RUN, and walk every I/O point before reconnecting to the process. Use the watch table to force outputs in a controlled sequence.

Frequently Asked Questions

Which TIA Portal versions include the S7-200 to S7-1200 Conversion Tool?

Only TIA Portal V10.5 and V11 (Basic or Professional) include the conversion entry under File > Migrate project > S7-200 project. TIA V12 and later removed the entry; projects created in V10.5 or V11 must be chain-upgraded through TIA's standard migration wizard to reach V13+.

Does the conversion tool work with STEP 7-Micro/WIN SMART projects?

No. The conversion tool reads only legacy Micro/WIN V4.x .mwp files compiled on STEP 7-Micro/WIN V4.0 SP9. Micro/WIN SMART is a separate product line that targets the S7-200 SMART CPU family. There is no automated bridge from SMART to S7-1200 — manual rewrite is required.

What happens to PPI networking (NETR/NETW) instructions during conversion?

They are dropped. The S7-1200 has no native PPI slave capability. Rewrite the communication using S7 communication PUT/GET blocks (single partner) or open IE communication TSEND_C/TRCV_C blocks (multiple partners) over PROFINET.

Will the converted program preserve the original symbol table and comments?

Partially. Tag names from the Micro/WIN symbol table are carried into a global DB, but the DB itself is renamed and the original V-memory offsets are not preserved as symbols. Network titles and rung comments are not transferred; only symbol and block comments survive, and only when the source Micro/WIN project contained them. Re-apply the original naming scheme manually.

Is it faster to convert or to rewrite a small S7-200 program?

For programs under ~200 networks containing mostly contacts, coils, timers, and counters, manual rewrite is typically faster than conversion plus cleanup. The conversion tool saves real time only on programs above ~500 networks or when the team has no STEP 7 TIA Portal experience. Always budget a minimum of 2 hours of cleanup per 100 converted networks, regardless of source size.

Back to blog