
A Production Windchill Upgrade: 40 Phases, Zero Failures, Zero Outage
40 of 40 migration phases, zero failures, zero production outage.
Read customer storyChoosing a partner
We move manufacturers from on-premise PTC Windchill to Windchill+, PTC's SaaS edition. The work starts with deciding what to leave behind, and it ends with a cutover that has been rehearsed until it is routine.
Talk to a consultantLast reviewed by Element Consulting

Windchill+ is on a lot of roadmaps. PTC's documentation explains how the conversion works, and it is good documentation. It does not tell you which of your customizations to drop, how much history to bring, or who owns the change for the people using the system.
An on-premise system that has run for ten or fifteen years carries customizations built for workflows that no longer exist, part numbering kept in Excel, and a change process people route around. Lift all of it into Windchill+ and you have the same problems with a better SLA.
Windchill+ limits how much you can customize, on purpose. So the first phase is an inventory, with one question asked of every customization: does this earn its keep? The longer version is in the Windchill+ migration guide nobody writes.
We inventory every customization and convention and sort each one: keep, rebuild as configuration, or retire. It is a workshop with the people who use the system.
Systems that have run for years carry settings left over from old versions. We find out what your environment is, as opposed to what the documentation says it is, before a rehearsal finds it for us.
The workflows you will run in Windchill+ are designed before the migration: part numbering, BOM structure and change control included.
What comes across, what is archived and what is left behind, decided object type by object type.
We rehearse the full migration until nothing new breaks, then once more. Automation makes repeated runs cheaper, which is why we can run more of them.
Champions, communication and training with a named owner who is not on the cutover's critical path. IT's job changes too, from running servers to managing a vendor.
By cutover weekend the team has watched the same steps finish clean more than once.
You want PTC to run the servers and the upgrades, and you can live inside its limits on customization.
You depend on customizations Windchill+ will not carry, or your hosting rules keep the system in your own data center.
Controlled data has to sit in a government cloud you control. You keep the Windchill you have and move it.
We do all three and will say which fits. See Windchill upgrades and Windchill on Azure Government Cloud.
We rehearse. On our most recent production Windchill upgrade, all 40 migration phases completed with zero failures and zero production outage, because the rehearsals had already found what would have gone wrong. We hold a Windchill+ move to the same standard. Read the case study.
Process and people first, technology second. A Windchill+ move changes how people work even when the screens look the same. We staff organizational change management on the project, with its own owner.
Independent of the license. We are an independent PTC partner and we don't resell software, so we can tell you when staying on-premise is the better answer.
Talk to a consultantAbout Element Consulting. Element Consulting is an independent PTC partner that has implemented, upgraded, integrated, and rescued PTC Windchill since 2003: 100+ PLM implementations, a senior-only team, headquartered in West Des Moines, Iowa. Managing Partner Eric Horn is a PTC Certified Windchill Implementation Practitioner. The firm works mainly in aerospace and defense, federal and national-security programs, medical devices, and industrial equipment, including ITAR-controlled and government-cloud delivery, and does not resell software.
Yes. It is the same Windchill PLM platform, delivered as SaaS and maintained by PTC, where on-premise Windchill is installed and run on your own infrastructure.
Not all of them. Windchill+ limits customization by design. Each customization is rebuilt as configuration, replaced by a process, or retired. We make that list with the people who use the system before anyone commits to a cutover date.
It depends on how much you have customized, your hosting and compliance rules, and who you want running the servers. We do both and will tell you which fits. See Windchill upgrades.
No, and it is a decision to make on purpose. For each kind of object you choose between full history and a baseline, and between migrating and archiving. Bring everything and you pay to move the mess. Bring too little and engineering loses history it relies on.
It depends on your compliance rules. If your controlled data has to sit in a government cloud you control, or you need to keep your customizations, the alternative is running the Windchill you have in your own Azure Government tenant. See Windchill on Azure Government Cloud.
Element Consulting plans and runs Windchill+ moves for manufacturers: the customization review, the drift audit, data scoping, rehearsed migration and change management. PTC's Windchill+ Success Path directs customers to select an implementation partner for this work.
40/40
Migration phases in an AI-verified Windchill 12 to 13.1 upgrade. Zero failures, zero production outage.
Read the case study80%
Lower cost of poor quality at one manufacturer once manufacturing reviewed the data before release.
100+
PLM implementations since 2003, from new Windchill rollouts to upgrades, ERP integration and rescue.
*Results from specific engagements. Clients are named only with their permission, and your results will depend on your scope and starting point.
The earlier the conversation about what to leave behind happens, the cheaper the move is.
