Luc Boucher - PLM Expert - PLM MigrationWe are today facing of a lot of PLM migrations in large industries to a new release or even a core product for the whole PLM scope of the company. Migrating from one release to another on the same product seems to be natural and without complexity regarding migration framework offered by PLM vendors.
All of us who have ever managed a PLM migration project know how it is always difficult to manage technical issues during migration coming from migration tools itself, data, architecture
Customers are usually saying : I do not need more functionality or rework them, I just need to be up to date regarding support or compliant with integrated tool. These are today major reasons to migrate a PLM system today.
So, industrial companies assume that they will reduce migration cost because their migration is becoming « only » a technical migration. This is not true! I have never seen a PLM migration without a large design specification, if it is not the case, design is postpone to the next migration and most of the time AM cost is becoming higher or huge.
Re-Design is mandatory for all major releases because of new design models, new user interfaces or even to be compliant with new functionality. It is like saying : I’m buying the new smartphone but I will only use it as a cell phone so I just need my contacts with customized attributes and no data network..
For instance, if you are considering a migration from Windchill 9 to 10, you could think that every UI will be automated generated by the product so you should « only » migrate data,services etc…
The reality is quite different. Windchill 10 now gives us incredible capabilities regarding UI compare to older releases. In order to be compliant with OOTB capabilities and customization done on the older release it is mandatory to redesign UI with end users. And I don’t speak about change management…


This kind of migration is the opportunity to be more COTS but also involved a mandatory re-engineering. This activity is very important regarding maintenance costs  and the ability to use up-to-date and new capabilities of the product. So do not speak about technical PLM migration for major release please… 😉

I’m just sharing my PLM point of view… what is yours?

Eve - Luc Boucher - PLM Expert