Converting Siemens ProTool .pdb Files to TIA Portal: Complete Migration Guide

Legacy Siemens HMI projects delivered as ProTool .pdb files appear routinely on service jobs involving S7-300 / S7-400 PLCs paired with OP, TP, MP, and Mobile Panel operator stations. These archives frequently arrive inside .arj containers shipped by an OEM, then need to be migrated through WinCC Flexible 2008 SP2/SP3 and finally into TIA Portal V13, V14, V15, or V16. This reference documents the verified conversion chain, the exact tool versions that handle each transition, the specific defects observed after migration (oversized text, broken tag links, malformed alarms, missing graphics), and the verification steps required before a converted project is downloaded to replacement hardware.

1. ProTool .pdb File Format Overview

ProTool was the Siemens configuration software for OP3, OP7, OP17, OP25, OP27, OP35, OP37, OP170, OP270, OP370, TP27, TP37, TP170, TP270, TP370, MP270, MP370, and Mobile Panel 170/177 HMI panels. The compressed project archive generated by ProTool and ProTool/Lite (the Win95/98 era variant) uses these primary extensions:

On modern Windows 10/11 systems, extracting an .arj requires an ARJ-compatible utility such as 7-Zip (with the ARJ.32.64 codec pack), WinRAR, or the legacy ARJ v2.84a command-line tool. Once extracted, the .pdb can be opened in ProTool/Pro V6.0 SP3 or migrated forward.

2. Migration Path and Tool Compatibility Matrix

There is no direct converter from ProTool to TIA Portal. Every migration must pass through WinCC Flexible 2008, and only specific service-pack levels of WinCC Flexible 2008 can ingest a ProTool .pdb. The supported chain is therefore two-step:

The critical pivot is the WinCC Flex 2008 SP2 -> SP3 jump. SP2 (build 8.2.2.0) shipped with the legacy ProTool importer intact; from SP3 onward the importer was removed because Siemens expected customers to have already migrated. If you only have SP3, the .pdb cannot be ingested; you must obtain SP2 either as an installation image on the legacy DVD or from a Siemens support representative. Siemens support confirms that the ProTool-to-TIA transition cannot skip the WinCC Flexible 2008 SP2 stage.

3. Prerequisites and Tool Versions

Confirm each of the following before attempting migration. Skipping any one results in either a refusal to open the file or a silently corrupted conversion.

1. Extraction utility: 7-Zip 19.00+ or WinRAR 5.x with ARJ support, installed and registered as the handler for .arj.
2. ProTool/Pro V6.0 SP3 (optional, recommended) - opens the original .pdb for read-only inspection and tag export. Without it you cannot validate the source before passing it to WinCC Flex.
3. SIMATIC WinCC Flexible 2008 SP2 - the only WinCC Flexible service pack that can natively import a ProTool .pdb via Project > Migrate ProTool Project. Both 32-bit and 64-bit are available, but WinCC Flexible is 32-bit; on Windows 10 64-bit you must install it in Windows 7 compatibility mode.
4. SIMATIC WinCC Flexible 2008 SP3 or SP5 - used only to re-save the migrated project as a .fwx ready for TIA Portal import. SP5 is the last release (build 8.5.2.0) and is preferred if available.
5. TIA Portal V13, V14, V15.1, V15.2, V16, or V17 - V13 is the lowest version that can import a WinCC Flexible 2008 SP3+ project; V15.1 is the practical minimum for current Comfort Panel firmware compatibility. The WinCC Comfort/Advanced or WinCC Professional ES is required (Basic is not sufficient for migration).
6. Matching panel firmware: A migrated project targeting an OP/TP 170/270/370 must be re-targeted to a KTP400 Comfort, KTP700 Comfort, TP700 Comfort, TP900 Comfort, TP1200 Comfort, or KP700/KP900/KP1200 Comfort (or the Basic series KTP400 Basic - KTP1200 Basic). The original OP/TP hardware is no longer manufactured.
7. STEP 7 / TIA PLC project - the HMI tags point at PLC DB/M/I/Q addresses; ensure the STEP 7 project is available in TIA so the tag references resolve.

4. Step-by-Step Conversion Procedure

4.1 Extract the OEM archive

1. Save the OEM .arj to a local directory, e.g. C:\Migrate\Source\.
2. Right-click the file and select 7-Zip > Extract Here. You should see one or more .pdb files plus any companion .bmp, .wmf, or text library files.
3. Note the panel target written inside the .pdb header (view with ProTool/Pro or any text reader that shows the byte stream - the panel type string is at offset 0x000C in most versions).

4.2 Inspect with ProTool/Pro (optional but recommended)

1. Launch ProTool/Pro V6.0 SP3 and open the extracted .pdb from File > Open.
2. Verify the panel type, number of screens, tag count, alarm count, and recipe count under System > Settings.
3. Export the tag list via Tags > Export to .csv for cross-checking after migration.
4. Close ProTool without saving.

4.3 Migrate ProTool -> WinCC Flexible 2008 SP2

1. Install WinCC Flexible 2008 SP2 (build 8.2.2.0). If SP2 is already installed, skip to step 4.
2. Launch WinCC Flexible 2008 SP2.
3. Select Project > Migrate ProTool Project.
4. Browse to the extracted .pdb file and click Open.
5. The migration wizard displays a report. Pay attention to:
   • Number of tags converted - should equal the source tag count from ProTool inspection.
   • Number of alarms converted - alarm classes Errors, Warnings, System, Diagnosis events are mapped automatically.
   • Picture objects with unsupported references - these will be flagged for manual rework.
6. Save the resulting project as .fwx in a dedicated directory, e.g. C:\Migrate\Step1\.
7. Do not attempt to compile or download yet - panel target still says OP/TP.

4.4 Re-save in WinCC Flexible 2008 SP3 or SP5

1. Open the .fwx from step 3.6 in WinCC Flexible 2008 SP3 (or SP5).
2. Allow SP3 to perform its own minor conversion (project format version bump from 8.2 to 8.3).
3. Re-verify the project compiles in SP3: Project > Compiler > Check Consistency. Resolve any error reported under the Messages window before continuing.
4. Save the project. You now have a TIA-compatible .fwx.

4.5 Migrate WinCC Flexible -> TIA Portal

1. Launch TIA Portal V13 (or later) with WinCC Comfort/Advanced or Professional installed.
2. Open the target TIA project that already contains the STEP 7 PLC configuration.
3. Add a new HMI device under Devices > Add New Device > HMI. Choose the replacement Comfort or Basic panel first to create the target HMI station.
4. Right-click the HMI station and select Migrate WinCC Flexible Project... (available from V13 onward).
5. Browse to the .fwx file from step 4.4.
6. The TIA migration tool maps ProTool/WinCC Flex elements as follows:

   Source object	TIA equivalent	Notes
   Tags (single)	HMI tags, DB-bound	Plc namespace prefix added automatically
   Tags (array)	HMI tag arrays	Indexing preserved
   Discrete alarms	Discrete alarms	Trigger bit mapped to HMI tag
   Analog alarms	Analog alarms	Limit types preserved
   Recipes	Recipes	Data record structure preserved
   Area pointers	Connections / area pointers	Re-verify after migration
   Screens (graphics)	Basic screens	Resolution may change; reposition
   Text lists / graphic lists	Text lists / graphic lists	Default font may swap to Arial 14 pt

7. Compile the migrated HMI station: HMI station > Compile > Software (rebuild all).
8. Resolve any compiler warnings about font substitution, missing graphics, or unresolved tag connections.

4.6 Re-target panel hardware (only if original was OP/TP)

If the ProTool project targeted an OP3, OP7, OP17, OP25, OP27, OP35, OP37, OP170, OP170m, TP170, TP170m, TP270, TP370, MP270, MP370, or Mobile Panel 170/177, you must re-target during the TIA migration:

1. Add a new Comfort panel to the project (TP700 Comfort, TP900 Comfort, TP1200 Comfort, or KP1200 Comfort depending on original screen size).
2. Run Migrate WinCC Flexible Project against the new device, not the old TP/OP target.
3. Manually adjust screen layouts because pixel dimensions differ (a 6" TP177B 320x240 maps to 800x480 on TP700 Comfort 7").

5. Common Conversion Issues and Corrections

6. Verification and Acceptance Test

Before downloading to the new HMI hardware, execute this checklist. Each step has a specific pass criterion.

1. Compile clean. TIA Portal shows zero errors and zero warnings on the HMI station. Warnings are acceptable only if documented and accepted.
2. Tag consistency. Open the HMI tag table and filter Status = Invalid. Result count must be 0.
3. Cross-reference check. For each PLC DB referenced by HMI tags, run PLC > Cross-reference in TIA. Resolve any DB address that the PLC no longer exports.
4. Alarm simulation. In the TIA HMI runtime simulation (Start > Simulation), force each discrete alarm trigger bit via PLCSIM and verify the message text displays correctly.
5. Screen navigation. Click through every screen using only the navigation buttons - verify no "screen not configured" pop-ups.
6. Recipe round-trip. Modify a recipe record, save, reload, verify data is unchanged.
7. Connection test. With PLCSIM running and the HMI runtime simulation, verify status byte returns "Connection established" within 5 seconds.
8. Real-hardware download. After the bench tests pass, transfer the project to the physical Comfort panel via Ethernet, MPI, or USB-Prommer and observe the startup banner for firmware version compatibility (minimum TIA V15.1 -> Comfort Panel FW V14.0.1; TIA V16 -> FW V16.0.x).

7. Troubleshooting Matrix

8. When Not to Migrate: Re-Engineering Considerations

The two-step migration through WinCC Flexible 2008 SP2 and SP3 is justified only when:

• The ProTool project contains undocumented operational logic (hidden screens, custom scripts, OEM-specific tag math) that cannot be recovered from the PLC runtime.
• The replacement panel hardware is identical-or-similar to the original (e.g. TP177B 6" -> TP700 Comfort 7").
• Time-to-archive exceeds the engineering hours available to rebuild.

Re-engineering from scratch is preferred when:

• The PLC project is also being modernized (S7-300 -> S7-1500), which breaks tag addresses anyway.
• The original ProTool project uses only basic screens (start, fault, hand, auto) - rebuild in TIA typically takes 8-16 hours vs. 24-60 hours of migration cleanup.
• The new panel series is dramatically different (e.g. WinCC Unified) where the migration tool does not yet exist.

References for ProTool file handling, including the inability of ProSave to read .pdb and the role of .pdb files embedded inside STEP 7 project folders, are documented on the Siemens support portal: opening a *.pdb file, .pdb vs. .psb conversion options, .pdb files inside STEP 7 projects, and the Siemens Community .pdb discussion. The official ProTool V6.0 SP3 manual and the WinCC Flexible 2008 Migration Manual (entry ID 22756405 on the Siemens support site) remain the authoritative references.