• STEP 7 Professional (TIA Portal) V11 or higher
• STEP 7 V5.4+SP5 or higher with the associated license
• STEP 7 options packages used in the project to be migrated

Note
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. We recommend the following as a remedy:

• Save the instance data blocks beforehand and copy them back into the block folder after compilation in the block consistency check or
• Restore the consistency of the blocks without compilation in the block consistency check. Generate a new instance DB and copy all the data from the old (inconsistent) DB into the new (consistent) DB.

Then you can migrate the project in the TIA Portal with your configured values.

Fig. 01

Note
As from STEP 7 Professional V12 the "Exclude hardware configuration" option in the "Migrate Project" dialog is disabled by default. If you want to migrate the hardware configuration, you must enable this option. If your project contains hardware components that do not fulfill these requirements, migration is aborted. In this case you must

• replace the non-migratable modules from STEP 7 V5.x with modules that are still being actively marketed
• or install the missing GSD files in the TIA Portal.

• 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.

Recommendation
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".

• The check sum and the overall signature of the F program are not changed by the migration. The migrated projected does not have to be approved again and can be downloaded into the F CPU without renewed compilation (1).
• If, however, you edit or recompile the migrated F program with STEP 7 Safety V11, then the program structures are changed to STEP 7 Safety Advanced V11 (2). In this way the F program receives a new overall signature and a new check sum. This means that the F program has to be approved anew.

Fig. 02

Note
You cannot migrate a Distributed Safety Project to STEP 7 (TIA Portal) V12, because the Safety Option is not yet available.

S7-SCL blocks can be migrated with or without the associated "STEP 7 V5.x - SCL source".

• S7-SCL source block available in the STEP 7 V5.x project (recommended)
  In order for you to be able to edit your S7-SCL blocks as required in STEP 7 Professional (TIA Portal), the S7-SCL sources must be stored in the source folder of the V5.x project before migration. These S7-SCL sources from STEP 7 V5.x are migrated to STEP 7 (TIA Portal) as S7-SCL blocks. The actual sources are not transferred, because no more work is done with block sources in STEP 7 (TIA Portal). In STEP 7 (TIA Portal), an SCL block is always created here in unprotected form (even if there is "KNOW-HOW-PROTECT" in the V5.x source).
• No S7-SCL source available for SCL block in the STEP 7 V5.x project.
  S7-SCL blocks for which the associated source file is missing in STEP 7 V5.x are migrated to STEP 7 (TIA Portal) as protected blocks. Restrictions for editing these blocks apply in the same way as for the protected blocks in Point 5.

The S7-GRAPH and S7-SCL blocks must be consistent and have to be recompiled after migration to STEP 7 (TIA Portal). Then you have to download the project into the CPU. It is only possible to have an Online View of the blocks after compiling and downloading.

Note
Please also observe the information given in Entry ID: 59784005. A number of instructions cannot be transferred and these have to be entered manually after migration.

• Process diagnostics S7-PDIAG
  S7-PDIAG blocks (FB44, DB44, …) are migrated but are marked as not supported. These blocks can be downloaded, but cannot be edited. The message texts and address monitoring instances are not longer available in the STEP 7 (TIA Portal) project.
• H systems
• Multiprojects (only separate projects can be migrated)

The components and software tools below are no longer supported in the TIA Portal.

• S7-HiGraph
  These blocks are migrated but are marked as not supported.
• iMap
• FMS connections
• Libraries created with STEP 7 V5.x. To remedy this we recommend copying the blocks from the library into a project. After migration you can copy the blocks into a TIA Portal library.

1. In the SIMATIC Manager of your STEP 7 V5.x project you mark your station ("SIMATIC 300", for example).
2. In the menu bar you select the "Options > Customize..." dialog.
3. Select the "Message numbers" tab and enable the setting "Always assign CPU-oriented unique message numbers".
4. 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. 03.

Fig. 03

• All parameters of the called block must be assigned in the call statement.
• None of the parameters of the called block is allowed to be deleted and inserted and parameterized at another point in the S7-SCL source.

• STEP 7 V5.4
• STEP 7 V5.5
• WinCC V7
• WinCC flexible 2008

More information is available in Entry ID: 60162195.

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 activate 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).

Fig. 04

Note
With this option the project is checked and reorganized in addition during the saving procedure. Under certain circumstances this method 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".

• Entry ID: 67858106 (Migration to S7-1500)
• Entry ID: 67582299 (Recommendations for programming for migration to S7-1500)