A TIA Portal upgrade changes more than the file format. It can affect the engineering station, installed option packages, device support, HMI behavior, library references, Openness tools, licensing, and the route back to a known working project. Use this checklist before opening the master project in V21, when planning a brownfield modernization, or when a customer asks what evidence will prove that the migrated project is ready for engineering or site acceptance.
When to use this checklist
Start while the current project can still be opened in its approved engineering environment. The useful starting point is not merely a ZIP file named “backup”; it is an identified baseline with a project version, TIA Portal release and update level, installed products, target devices, responsible owner, checksum, and acceptance status. That context lets another engineer distinguish the project you intended to migrate from an older download, a service laptop copy, or a partially edited commissioning version.
The checklist is suitable for PLC-only projects, integrated PLC/HMI projects, and larger installations with drives, Safety, distributed I/O, third-party device descriptions, libraries, or automation built through TIA Portal Openness. It is not a substitute for the product release notes or the compatibility tool. Each hardware family and option package must still be checked against the official Siemens information for the exact V21 update you will install.
Confirm the supported version path
Siemens states that TIA Portal project versions V14 through V20 can be upgraded directly to V21. Projects from V11 through V13 first need an intermediate upgrade path through V13 SP1 or SP2 and then a version between V14 and V20. STEP 7 V5.x Classic, WinCC flexible, WinCC V7, and integrated classic projects cannot be migrated directly by V21; Siemens directs users to the Migration Tool with V20 or an earlier supported version before the resulting project is upgraded to V21.
Record the source project version and the tool used at every hop. If an intermediate conversion is required, treat it as its own controlled revision: retain the input, output, migration log, compiler result, person who performed the work, and decision to continue. This avoids a common audit gap in which only the final V21 file exists and nobody can reconstruct which conversion introduced a warning or removed an unsupported object.
- Identify the current TIA Portal project version, service pack, update, and edition.
- List STEP 7, WinCC, Startdrive, Safety, PLCSIM, Openness, add-ins, and other installed options that the project actually uses.
- Confirm whether the source is a native TIA Portal project or a Classic/integrated project requiring a separate migration tool.
- Record each intermediate version, responsible engineer, output archive, and compiler or migration report.
- Keep a machine capable of opening the approved source until rollback is no longer required.
Build the compatibility gate before installation
Compatibility is a project-specific decision, not a single “V21 compatible” checkbox. Begin with the engineering workstation: supported Windows edition, free disk space, administrative installation process, corporate endpoint controls, and any parallel TIA versions required for support. Then verify the installed products and license entitlement. A V21 license may cover earlier TIA releases in relevant products, but the exact license type, product bundle, network license service, and customer entitlement must be checked rather than assumed.
Next inspect the project dependencies. Capture CPU, HMI, drive, communication processor, remote I/O, and technology module order numbers with firmware versions. Export a list of GSD, GSDML, EDS, HSP, device packages, global libraries, corporate libraries, faceplates, scripts, certificates, user administration settings, and external source files. For Safety, motion, drives, redundant systems, or protected blocks, name the qualified reviewer and the dedicated validation that applies.
Openness applications and add-ins deserve a separate check. Siemens documents API, enumeration, reference, and add-in configuration changes for V21 and provides a Migration Assistant for compatible development projects. Preserve the source repository and build environment, run the assistant on a branch or copy, review its migration report, rebuild against the V21 assemblies, and test the resulting automation before it is allowed to touch an engineering project.
Prepare a backup and rollback package
A rollback package must answer a practical question: if the migration is rejected, can the authorized team reopen the accepted source, connect with the approved tools, and restore the previous engineering state without guessing? Preserve the archived source project and its checksum, the installed-software inventory, license evidence, library and device-description copies, external sources, certificates handled under the project security procedure, and the latest accepted test or handover reference.
Online uploads are not interchangeable with the original engineering project. Upload only where the device and project permit it, the work is authorized, and the result is understood. Some comments, symbols, libraries, HMI resources, source files, or protected content may not be recoverable from the controller. Document exactly what was uploaded, from which device, at what time, by whom, and whether it is a complete recovery source or only supporting evidence.
- Immutable source archive with SHA-256 checksum and a clear Golden Copy or accepted-baseline designation.
- Engineering-station inventory covering operating system, TIA components, update levels, licenses, and required installers.
- Installed equipment and firmware register, including option packages and third-party device descriptions.
- Libraries, external sources, Openness projects, add-ins, certificates, and protected-access recovery instructions.
- Named rollback owner, decision deadline, recovery test, and acceptance criteria for returning to the source version.
Run a controlled migration and test workflow
Perform the first migration offline on a clone, not on the accepted master. Record the V21 edition and update, open the clone, retain every conversion message, and compile all software and hardware. Do not close warnings simply because the project opens. Classify them by affected device or function, assign an owner, and state whether the warning is accepted, corrected, or blocks the migration. Compare hardware configuration, addresses, device names, network topology, block inventory, HMI objects, alarms, recipes, users, certificates, drive parameters, and Safety signatures where applicable.
- 01
Freeze and identify the approved source; calculate its checksum and record the source environment.
- 02
Create a separate migration revision and open only that copy in the approved V21 test workstation.
- 03
Capture conversion messages, compile hardware and software, and reconcile every new warning or error.
- 04
Run offline comparisons and simulations where meaningful, then execute the approved bench, FAT, or site test plan.
- 05
Test PLC logic, HMI navigation and alarms, communications, drives, motion, Safety, recipes, reports, and restart behavior that are in scope.
- 06
Rehearse the rollback decision and recovery steps before the change window closes.
- 07
Obtain engineering and customer acceptance, then designate the accepted V21 revision without replacing the preserved source.
Testing must be risk based. A clean compiler output does not prove that an HMI faceplate, fieldbus device, drive telegram, motion sequence, Safety function, external script, or commissioning procedure behaves correctly. Define expected results before execution and attach the actual observation, test equipment, configuration, evidence, deviation, and approver. Where a test cannot be performed before site access, mark it explicitly as outstanding rather than presenting the migration as complete.
Evidence checklist for the migration decision
| Checkpoint | Evidence to retain | Acceptance question |
|---|---|---|
| Source baseline | Archive, version, checksum, owner, accepted status | Can the team identify and reopen the exact pre-migration project? |
| Compatibility | Siemens references, hardware/firmware list, options, libraries, licenses | Are all used components supported or covered by an approved exception? |
| Conversion | V21 version/update, messages, intermediate revisions, compiler reports | Is every warning assigned and resolved or consciously accepted? |
| Functional test | Test cases, expected and actual results, attachments, deviations | Have the functions affected by the migration been demonstrated? |
| Rollback | Recovery owner, tools, source archive, rehearsal result, decision point | Can the previous state be restored inside the permitted window? |
| Acceptance | Engineering review, customer/site acceptance, released revision | Is the V21 project clearly distinguished from drafts and rejected attempts? |
Record the migration in AutoNexit
Create or link a lifecycle change for the V21 migration and state the reason, affected systems, owner, planned window, risk, and acceptance route. In Revisions, retain the accepted source separately from each migration attempt; attach checksums, conversion and compiler reports, and identify the final accepted V21 revision only after review. Use Installed software and firmware records for the engineering tools and equipment versions, and link the relevant backup record rather than duplicating unexplained files.
Commissioning evidence should show the test case, expected result, actual result, author, time, attachments, and disposition of any failure. Link open punch items and required retests. When the migration reaches handover, the package should point to the accepted revision, compatible software and firmware inventory, test evidence, unresolved exceptions, backup and recovery information, and the party who accepted the outcome. This creates a connected project record without pretending that AutoNexit performed the migration itself.
Common failure modes and responsibility boundaries
Typical failures include converting the only source copy, missing a third-party device package, assuming an existing license covers every option, rebuilding an Openness tool without testing it, accepting compiler warnings without an owner, treating a successful download as functional acceptance, or discovering after the change window that the old workstation or installer is unavailable. Another frequent error is overwriting the pre-migration revision with the V21 output, which removes the comparison and rollback evidence the team needs most.
If the evidence is incomplete, stop at a visible hold point. State what is missing, who owns it, and which test or approval is blocked. A delayed migration with a recoverable baseline is safer and easier to explain than a nominally finished upgrade whose source, warnings, and acceptance cannot be reconstructed.
Official Siemens sources
Version rules and product claims were checked against the sources below. Fact-checked
TIA Portal V21 migration questions
Can every TIA Portal project be upgraded directly to V21?
No. Siemens states that V14 through V20 projects can be upgraded directly. V11 through V13 require an intermediate path, while Classic STEP 7, WinCC flexible, WinCC V7, and integrated classic projects must use the supported Migration Tool path with V20 or earlier before moving to V21. Confirm the latest rule for the products your project uses.
What should be backed up before V21 opens the project?
Retain the exact archived source with a checksum, the engineering environment and license inventory, device and firmware list, libraries, external sources, third-party descriptions, Openness or add-in code, relevant certificates under controlled handling, previous acceptance evidence, and a tested way to reopen the source. An online upload alone may not reconstruct the complete engineering project.
When is rollback an acceptable result?
Rollback is appropriate when a blocking compatibility issue, unresolved compiler change, failed functional or Safety test, missing license or dependency, or loss of the approved change window prevents acceptance. The project procedure must name who can make that decision, the deadline, and the evidence that the restored source is operationally acceptable.
Does AutoNexit migrate or validate the TIA Portal project?
No. AutoNexit keeps the source and migrated revisions, checksums, installed-software context, test evidence, actions, approvals, and handover links connected. The migration, product compatibility decision, equipment access, functional-safety review, and authorization remain with Siemens documentation and the responsible engineering and site teams.