Start with what is actually running in the machine
The starting point is the operating control system, not just the S7-300 designation. We check the CPU and modules, software versions, drawings, networks, HMI and changes made during the machine's service life. We compare the available project with the online program to the extent supported by the tools and access protection. An upload from the controller alone does not replace a complete project with symbols, sources and the configuration of other devices.
Before machine and control system modernisation, we internally secure the material needed for the work and record settings, recipes and values needed for commissioning. We agree which functions to retain and what to change. A platform replacement is not combined with unagreed changes to the process.
STEP 7 Classic, TIA Portal and the new CPU family
Moving a project into TIA Portal, upgrading a TIA project version and migrating the program to S7-1500 are separate operations. A TIA project can still contain an S7-300.
TIA Portal V21 does not support direct migration of STEP 7 Classic projects. One route specified by Siemens uses Migration Tool V20 to prepare a migration file, followed by migration in TIA Portal V20. Only then is the resulting TIA project upgraded to V21, checking device and optional package compatibility.
The workstation preparing the migration file needs the software required to process the source project, with the necessary licences, packages and updates. Installing V21 alone is not sufficient.
Migrating the program to S7-1500 is a further operation within TIA. It requires a consistent, compiled reference program. We review the log and make the necessary corrections; the target hardware is configured separately. The converter does not automatically transfer the old CPU's hardware configuration.
Select the CPU and I/O for the process
Selection covers memory, response times, communication load, technology functions and capacity for expansion. We do not select a CPU solely from the old controller's order number. We also check firmware and hardware support in the target TIA version.
Central S7-300 modules cannot simply be moved into an S7-1500 system. For the I/O, we prepare a new configuration, terminal and address mapping, and check signal types, power supplies and cabinet space. Existing distributed stations may remain after compatibility of the complete configuration has been confirmed: interface, modules, parameters and communication. Retaining PROFIBUS or PROFINET alone does not establish that compatibility.
Special blocks, diagnostics and safety functions
In the PLC program, we check SFCs/SFBs, machine manufacturer libraries, control loops, motion functions, interrupts and STL code using indirect addressing. Blocks tied to the old platform may need replacement or redesign. Protected blocks need an authorised migration route that is actually available: an unprotected version or a library intended for the new CPU. We do not assume the converter can migrate an encrypted block.
Diagnostics require a separate review. S7-1500 has integrated system diagnostics; older implementations based on system status lists and Report System Errors cannot be carried over unchanged. We also check what operators and maintenance staff will see after migration.
The F-program, F-I/O configuration and safety functions require a separate assessment and the appropriate validation and acceptance process. An ordinary machine sequence test cannot replace this work.
DB access must match the communication interface
We identify references to fixed addresses, such as DB10.DBW4, both in the PLC and in external systems. An optimised DB has no fixed offsets available for absolute addressing. We therefore analyse the dependencies before enabling optimisation.
If a communication partner requires absolute access, a dedicated standard-access DB with an agreed data layout may be appropriate. We verify the DB number, offsets, data types and read/write ranges. Where PUT/GET is needed, we assess it together with CPU permissions and access protection; it is not enabled automatically as a connection fix. We also check pointers, local data and value retention after a restart.
HMI and SCADA are part of the migration
For HMI and SCADA, we check the panel or runtime, engineering version, communication driver and tag addressing. Retaining an older panel must be based on confirmed compatibility with the new CPU. Changing the IP address alone is not sufficient.
Testing covers tag reads and writes, commands, alarms, recipes and reconnection after a fault. We also verify drive telegrams and data exchange with other PLCs and reporting systems. For CP/CM modules, we check the required communication instructions and connection parameters as well as the physical interface.
Plan the shutdown and any rollback before dismantling
Before shutdown, we prepare the program, hardware, wire identification and work sequence. The shutdown window covers installation, I/O checks, communication checks and process trials, with time allowed for fault correction.
We agree a decision point for stopping commissioning. Rollback is practical only if the necessary old equipment, internal backups for restoring the controls and the means of reversing electrical and mechanical changes have been retained. A program archive alone does not return a machine to service. Once an agreed stage has been passed, rollback may require a different procedure.
Test machine behaviour, not just successful compilation
We check signals, scaling, drive directions, sequences, interlocks and diagnostics. Trials cover communication loss, STOP/RUN, loss and restoration of power, and a controlled restart under conditions agreed with the plant. Testing away from the machine reduces risk but does not replace checking the installation and process.
After the work, we discuss results, changes and operating recommendations. Before contacting ETOPA, prepare device designations, available material, a process description and the permitted shutdown window. The older platform is covered separately in our guide to modernising SIMATIC S5 to S7-1500.
Siemens documentation
The route to V21 is described in the migration options overview; preparation of the intermediate file is covered by Migration Tool V20. The separate S7-1500 program migration procedure defines the requirements and scope of conversion. Siemens also explains standard and optimised block access and acceptance of changes in a Safety system.