What are the requirements for migrating a STEP 7 V5.x project to STEP 7 Professional (TIA Portal)?
The software components listed below must be installed on the computer on which you wish to perform the migration:
- STEP 7 Professional (TIA Portal) V11 or higher
- STEP 7 V5.4+SP5 or higher with associated license (US)
- All STEP 7 options packages which will be used in the projects to be migrated
The entire STEP 7 V5.x project (S7 program, hardware and network configuration) must be consistent. Perform the relevant function for consistency checking in each case to check and ensure consistency.More information about consistency checking is available in Entry ID: 5416540 and in the relevant help menu of STEP 7 V5.x.
In the SIMATIC Manager of STEP 7 V5.x you can also store the STEP 7 program just in a program folder (without CPU). After migration a non-specific CPU is created in STEP 7 (TIA Portal) for the consistent program.
Compilation in the block consistency check causes the tags in the instance DBs for the technology blocks (PID function blocks, for example) to be reset to their default values. This applies also to the data blocks in which recipes were configured.
Before you migrate the project to the TIA Portal we recommend the following:
- Save the instance data blocks beforehand and after compilation in the block consistency check copy them back into the block folder.
- Or re-establish the consistency of the blocks without compilation in the block consistency check. Create a new instance DB and copy the data from the old (inconsistent) DB into the new (consistent) DB.
Projects from earlier versions of STEP 7
If you want to migrate projects from earlier versions of STEP 7 (V5.3, for example) to STEP 7 Professional (TIA Portal), you must first re-compile these projects in STEP 7 V5.4+SP5 (or higher).
During migration only the software is migrated by default and in the target project an unspecified device is created for each of the devices in the source project. Hardware and network configurations and connections are not migrated.
If you also want to migrate the hardware components from your STEP 7 V5.x project, then in the "Migrate project" dialog you must enable the "Include hardware configuration" option.
NoteIf you include the hardware configuration in the migration, all the hardware components in your STEP 7 V5.x project must be in the hardware catalog of the TIA Portal. The modules that could be ordered and were not discontinued by 1.10.2007 are supported by the TIA Portal and are stored in the hardware catalog of STEP 7 (TIA Portal). If your project contains hardware components that are not in the hardware catalog of STEP 7 (TIA Portal) and that cannot be replaced with GSDML files, migration is aborted.
You can migrate projects with protected blocks to the TIA Portal and then download them to the CPU. Here, blocks from STEP 7 V5.5 encrypted with S7 Block Privacy are marked as not supported. Note the following restrictions in this case:
- The block protection from STEP 7 V5.x (KNOW_HOW_PROTECT or encryption with S7 Block Privacy) is not supported in the TIA Portal. A modified block protection is available in STEP 7 Professional.
- You cannot open or edit these blocks.
- The block protection from STEP 7 V5.x can no longer be removed in the TIA Portal.
Before migrating the project, you should remove the block protection from your blocks in STEP 7 V5.x. After migration you can protect your blocks again with the protection mechanism of STEP 7 Professional (TIA Portal) in this menu: "Edit > Know-How Protection".
Before migration you must use S7 Distributed Safety V5.4 SP5 to compile projects with safety programs which you have created with S7 Distributed Safety. Then you can continue using those projects in STEP 7 Safety Advanced. The following software tools must be installed on the computer to which you are migrating:
- STEP 7 Safety Advanced
- S7 Distributed Safety V5.4 SP5
- F Configuration Pack V5.4 SP5 to V5.5 SP11.
After migration you receive a complete project with a safety program which has retained the program structure of S7 Distributed Safety and the F overall signature. F blocks from the F library S7 Distributed Safety (V1) are converted into instructions which STEP 7 Safety Advanced provides.
When the migrated project is compiled with STEP 7 Safety Advanced, the program structure (1: with F‑CALL) is transferred to the new program structure of STEP 7 Safety Advanced (2: with Main Safety block). With this the F overall signature changes and the safety program might have to be re-approved.
The table below shows the components/software tools which can or cannot be migrated to STEP 7 Professional (TIA Portal).
Migratable Non-migratable LAD S7-HiGraph
(Blocks are migrated but identified as not supported.)
FBD iMap STL FMS connections S7-GRAPH and S7-SCL
The blocks must be consistent and re-compiled after migration in the TIA Portal. Then you must reload the project. It is only possible to have an Online View of the blocks after compiling and downloading.
Libraries created with STEP 7 V5.x.
Copy the blocks into a STEP 7 V5.x project. After migration you can create a library for the blocks in the TIA Portal.
The blocks (FB44, DB44, …) are migrated but are identified as not supported. You can download the blocks but not edit them. The message texts and address monitoring instances are no longer available in the TIA Portal project.
You can only migrate single projects.
You can migrate the S7-SCL blocks with or without the associated "STEP 7 V5.x - SCL source". However a complete migration is only executed if the associated sources are available in the source folder of the source project.
Source project After migration SCL blocks with source Editable SCL blocks Know-how-protected SCL blocks with source Editable SCL blocks. The know-how protection is removed during the migration and can be enabled again with STEP 7 (TIA Portal). SCL blocks without source Know-how-protected blocks* Know-how-protected SCL blocks without source Know-how-protected blocks*
*The block protection cannot be removed and the SCL blocks cannot be edited in STEP 7 (TIA Portal).
Refer also to the information in the STEP 7 (TIA Portal) Online Help under "Migration of SCL programs".
Further information about migratable instructions is available in Entry ID: 59784005. You cannot transfer a series of instructions and you have to enter them manually after migration.
The SFM blocks (FB49, DB49, FB50 and FC49) are not migrated. After migration:
- The system diagnostics is enabled in the CPU Properties.
- You must compile the hardware configuration in STEP 7 (TIA Portal) in order to create the new SFM blocks including new alarms and test lists.
Then you have to download the project into the CPU.
PLC messages are migrated with all the parameters and including all message classes. The message types and message instances are also migrated and stored under the PLC messages in the TIA Portal. The requirement is that option "Always assign CPU-oriented unique message numbers" must be enabled in the source project. You can enable this setting afterwards in the STEP 7 V5.x project. Proceed as follows before the migration:
- In the SIMATIC Manager of your STEP 7 V5.x project you mark your station ("SIMATIC 300", for example).
- In the menu bar you select the "Options > Customize..." dialog.
- Select the "Message numbers" tab and enable the setting "Always assign CPU-oriented unique message numbers".
- Then save your project with the "File > Save as..." function and the "With reorganization (slow)" option.
Messages are migrated only with this setting as shown in Fig. 3.
The TIA Portal Readiness Check Tool delivers an easy way of checking whether the TIA Portal supports the hardware in the projects. The tool can be used for:
- STEP 7 V5.4
- STEP 7 V5.5
- WinCC V7
- WinCC flexible 2008
Further information is available in Entry ID: 60162195.
If your project includes configurations from option packages that are not compatible with your current version of STEP 7 or which are not installed on your computer, you cannot migrate the project to STEP 7 (TIA Portal). If you open the project in STEP 7 V5.x, you get the message indicating that options packages are missing.
In case these configurations are still obligatory, you must install the missing options packages. Note here the hardware requirements for installing with the current version of STEP 7. For example, you need version V4.2.1 (or higher) for SIMOTION SCOUT with STEP 7 V5.5+SP2 in Windows 7 (32-bit). More information about compatibility is available in Entry ID: 18734363. After installing the missing options packages you must recompile your project.
If you no longer need the configurations of the missing options packages, you must reorganize the project in STEP 7 V5.x. For this, in the SIMATIC Manager you open the dialog "File > Save as..." and enable the option "With reorganization (slow)". Change the project name or the path and acknowledge with OK. After saving and reorganizing you can migrate the newly created project to STEP 7 (TIA Portal).
With this option the project is checked and reorganized in addition during the saving procedure. Under certain circumstances this method also reduces the project's memory requirement. All the elements of the missing options packages are removed from the project. More information is available in the Online Help of STEP 7 V5.5 under "Save project as".
Programming recommendations and information about migration to S7-1500 in STEP 7 (TIA Portal) V12 and higher are available in
Further information is available in the STEP 7 (TIA Portal) Online Help under "General information about the migration of program blocks".
The screens in this FAQ response were created with STEP 7 V5.5 and with STEP 7 (TIA Portal) V13.
- You have a technical question / problem: Ask the Technical Support
- You want to discuss in our forum and exchange experiences with other users
- You want to create CAx data for one or more products
- You would like to send us feedback on this Entry