Opening TIA Portal V11 Project Files in TIA Portal V13

Engineers upgrading from STEP 7 / TIA Portal V11 to V13 frequently encounter an apparent roadblock: the .ap11 project file cannot be selected through the migration wizard, and Windows cannot associate the file with TIA V13 because V13 expects a different file extension and project signature. The correct workflow is to use the Project > Open command from inside TIA Portal V13 and let the application detect that an upgrade conversion is required. The dedicated Migration tool is for converting legacy STEP 7 V5.x or WinCC flexible projects, not for upgrading between TIA Portal versions.

This reference documents the supported upgrade path, explains the project file structure across TIA Portal generations, and provides a field-tested procedure for opening, converting, verifying, and saving TIA V11 projects in TIA V13 (and higher). It also covers the common failure modes (unknown file association, library references, HMI compile errors) and the controls to apply so the upgrade is deterministic and reversible.

1. Background: TIA Portal Project File Format Evolution

Each major release of TIA Portal introduces a new project database schema. Siemens encodes the target version into both the file extension and the internal binary signature, so a project written by an older release cannot be opened directly by a newer release without conversion. The file extension mapping is:

2. The Migration Tool vs. The Open Command

Two different conversion paths exist in TIA Portal, and choosing the wrong one is the most common cause of the error described in the source case.

2.1 Migration Tool (Project > Migrate project)

The Migration command is reserved for legacy environments:

• STEP 7 V5.4 / V5.5 (.s7p, .mcp) to TIA Portal
• WinCC flexible 2008 / WinCC (TIA Portal predecessor) to WinCC (TIA Portal)
• PROFINET configuration files from older COM versions

Selecting Project > Migrate project in TIA V13 and pointing at an .ap11 file will fail with "The selected project was not created by a supported source system."

2.2 Open Command (Project > Open)

The native Open command handles version upgrades within the TIA Portal product line. When TIA V13 reads an .ap11 signature it triggers the version upgrade wizard. This is the only correct path for TIA-to-TIA upgrades. See the official procedure in TIA Portal Help - Opening Projects.

3. Prerequisites

1. TIA Portal V13 (or higher) installed with administrator rights. The target TIA Portal version must be the most recent version that will ever read the converted project. TIA Portal does not support downgrade - a V13 project cannot be reopened in V11.
2. Source project folder intact on a local NTFS drive (avoid network shares during the initial upgrade to eliminate latency and ACL-related errors).
3. Original .ap11 shortcut file present, or knowledge of the source folder name.
4. Read/write access to the project folder. TIA creates a new *.ap13 shortcut and a converted project tree.
5. Optional but recommended: a backup of the entire project folder (e.g. KP300_Basic_Demo_v11_backup.zip) before any conversion is attempted.
6. For HMI panels (e.g. the KP300 Basic referenced in the source): ensure the panel HSP (Hardware Support Package) is installed in TIA V13. If the original device firmware is not recognized, the upgrade will complete but the HMI station will show as "unknown device".

4. Step-by-Step Procedure: Open a V11 Project in TIA V13

1. Launch TIA Portal V13 as a user with administrator privileges (right-click > Run as administrator if User Account Control is enforced).
2. From the Portal view or Project view, select Project > Open (keyboard shortcut Ctrl + O).
3. In the Open project dialog, click Browse to navigate to the source folder. TIA V13 displays all recognized project shortcuts (.ap11 through .ap13) plus recently used projects.
4. Select the .ap11 project shortcut (for example KP300_Basic_Demo.ap11) and click Open.
5. TIA V13 detects the older project signature and displays a version conversion prompt: "The selected project was created with an older version of TIA Portal. The project will be converted to the current version. This action cannot be undone."
6. Click Convert. The conversion time depends on project size: a 1 MB project typically completes in 5 to 15 seconds, while multi-MB projects with hundreds of devices can take several minutes.
7. When conversion completes, the project opens in the project tree. TIA V13 creates a sibling .ap13 shortcut pointing to the same logical project database. The original .ap11 file is not deleted; it remains on disk for archival.
8. Select Project > Save as and choose a new folder if you want a side-by-side copy of the V11 original and the V13 upgrade.

5. Why Double-Clicking the .ap11 File Fails

When only TIA V13 is installed, the Windows registry contains no association for the .ap11 extension. Double-clicking the shortcut produces the dialog:

"Windows cannot open this file type. To open this file, Windows needs to know which program you want to use to open it."

This is purely a shell-association problem, not a project corruption problem. Two workarounds exist:

1. Open from within TIA Portal using the procedure in Section 4 (recommended).
2. Associate the file extension manually in Windows: right-click the .ap11 file > Open with > Choose another app > Look for another app on this PC > navigate to C:\Program Files\Siemens\Automation\Portal V13\Bin\Siemens.Automation.Portal.exe. After clicking Always use this app, Windows will pass the file directly to TIA V13, which then runs the same internal conversion.

6. What Changes During the V11 → V13 Conversion

The TIA Portal upgrade process is more than a file format change. The following are restructured or recompiled:

7. Handling Common Conversion Errors

7.1 "The project cannot be opened because it was created with a newer version of TIA Portal"

This error means you are attempting the opposite direction (e.g. opening a V13 project in V11). TIA Portal never supports downgrade. Install the matching or newer TIA version.

7.2 "The selected project is not a TIA Portal project"

Caused by selecting the project folder instead of the .ap11 shortcut. TIA Portal expects the shortcut file as the entry point. Inside the folder, additional files such as System\PEData.db, IM\HMI, and CrossReferences define the project; the shortcut is a pointer to the folder's metadata.

7.3 "The project file is write-protected"

Either the project resides on a read-only share, or the user lacks NTFS modify rights. Copy the folder locally and clear the read-only attribute with attrib -R "C:\Projects\KP300_Basic_Demo" /S /D.

7.4 "A referenced library cannot be found"

Open Options > Global libraries > Manage libraries, re-add the missing .al11 file, and repeat the conversion. Library references are stored by absolute path; if the source PC had the library in D:\Libs\ and the new PC does not, the reference is broken.

7.5 HMI compile errors after conversion

KP300 Basic, KTP400, TP177B and other Comfort/Entry panels require V13-compatible WinCC images. The V11 image remains on the panel; V13's HMI loader will detect the runtime mismatch and refuse to load the project until either the panel firmware is upgraded separately with ProSave, or the V13 project is re-targeted to a V11-compatible image using the Type dropdown in the HMI device properties.

8. Verification Checklist

1. Project opens without errors - the project tree expands cleanly. The TIA Portal output window shows no red entries.
2. Devices resolve correctly - all PLCs, HMIs, and distributed I/O show green check marks in the project tree. Any yellow triangle indicates a missing HSP; install the matching HSP from Siemens Industry Online Support and recompile.
3. Program blocks compile - right-click the PLC > Compile > Software (rebuild all blocks). Compilation must finish with zero errors.
4. HMI compilation succeeds - right-click the HMI > Compile > Software (rebuild all). Warnings are tolerated; errors must be cleared.
5. Cross-references rebuild - Project > Cross-reference information > Display. The cross-reference matrix should be repopulated.
6. PLCSIM (optional) - download the compiled blocks to a PLCSIM V13 instance to confirm runtime behavior. Compare with the V11 baseline.
7. Save the upgraded project - Project > Save. The new .ap13 shortcut is created.

9. Multi-User and TIA Multiuser Server Considerations

If the V11 project was checked in to a TIA Multiuser Server, the upgrade path is different:

1. Open the V11 project locally (working copy) in TIA V13 and run the conversion as described above.
2. Run Project > Multiuser > Disconnect from server project if the server is on a V11-compatible TIA Multiuser Server.
3. Configure the server connection against a TIA V13 (or newer) Multiuser Server.
4. Use Multiuser > Check in to publish the V13 project to the new server. Historical revisions created in V11 cannot be preserved; the V13 check-in establishes a new version history.

10. Migrating a Global Library (al11) Used by the V11 Project

Many engineering departments distribute standardized FB/FC blocks through Global libraries. If the V11 project references a library that has not been opened in V13, the HMI/PLC compile may fail. The library migration is a separate process:

1. In TIA V13, choose Libraries > Open global library.
2. Navigate to the .al11 file.
3. TIA V13 prompts to upgrade the library to .al13 format. Confirm.
4. Re-add the upgraded library to the master project via Options > Global libraries > Manage libraries > Browse > select the new .al13.
5. Recompile the project.

11. Practical Notes from the Field

• Project name and folder name must match. If the source folder was renamed (for example KP300_Basic_Demo_old) but the shortcut still references KP300_Basic_Demo, TIA reports "Project not found". Either rename the folder or right-click the shortcut > Edit and adjust the ProjectFilePath line.
• Always perform the upgrade on a local SSD. Converting large projects over a network share can exceed the default file-system timeout and corrupt intermediate files.
• If a V11 SP1 project needs to be opened in V13 SP2 and V14 simultaneously, keep the V11 SP1 master unchanged and create two upgrade copies: one in V13, one in V14. There is no path back to V11 from either copy.
• The TIA Portal Portal view hides the Open command in some compact installations. Switch to the Project view using the link in the lower-left of the start screen for full menu access.
• When TIA V13 is installed alongside V11 on the same PC, the file associations for .ap11 are owned by V11. Double-clicking then correctly launches V11. To force a V13 conversion, use Open with > Siemens TIA Portal V13.

12. Summary Procedure (Quick Reference)

FAQ