Skip to main content
B
BG_95467164-Participant
4-Participant
June 12, 2026
Question

Thingworx Platform 7.4 Upgrade

  • June 12, 2026
  • 2 replies
  • 14 views
I am using ThingWorx Platform Release 7.4 and DatecodeSP1 We currently have a business-critical ThingWorx 7.4 application running in our environment. As per our internal requirements, we are planning to upgrade the platform to the latest available version, ThingWorx 10.1. Could you please assist us with the recommended approach and way forward for this upgrade? We would appreciate it if you could provide: The recommended upgrade path from ThingWorx 7.4 to 10.1. Any prerequisites, compatibility considerations, and key risks involved. Detailed documentation or implementation guides for the upgrade process. Best practices to minimize downtime and ensure a successful migration. Additionally, we would like to understand the level of support that PTC provides during this upgrade activity Here are the errors that I faced We currently have a business-critical ThingWorx 7.4 application running in our environment. As per our internal requirements, we are planning to upgrade the platform to the latest available version, ThingWorx 10.1. Could you please assist us with the recommended approach and way forward for this upgrade? We would appreciate it if you could provide: The recommended upgrade path from ThingWorx 7.4 to 10.1. Any prerequisites, compatibility considerations, and key risks involved. Detailed documentation or implementation guides for the upgrade process. Best practices to minimize downtime and ensure a successful migration. Additionally, we would like to understand the level of support that PTC provides during this upgrade activity

2 replies

D
dlemoult5-Regular Member
5-Regular Member
June 12, 2026

Dear customer, kindly reformulate the same ask in a Support Ticket using the PTC eSupport portal (eSupport | PTC) and someone will contact you to provide you guidance. Kind regards

S
slangleyCommunity Manager
Support
June 12, 2026

Hi ​@BG_9546716 

Kudos for planning your upgrade!  As you know, you are jumping many releases to get to the latest version (note that 10.2 is planned for release soon).  There is often a lot of trial and error involved to lock down all the steps, and it’s often necessary to do some interim upgrades.  That will be a problem for you since many of the releases you would need to jump to are no longer available for download. 

 

Opening a case is the right approach, but I’ll provide some high level information.

 

Generally, when you’re not jumping this many releases, it is recommended to create a clone of your production environment (remember to turn off any feeds to avoid impacting your production data).  The cloned environment, with all it’s data, etc. would be used for testing the upgrade.   That allows you to assess the time actually needed for upgrading Prod.  It’s recommended to use a VM so you can take snapshots along the way that allow you to quickly revert if a step fails.  If you were upgrading from 9.2, it might be necessary to first install 9.4 before jumping to a higher version.  The ThingWorx Help Center has some guidance around this, but every situation is different and requires due diligence to work through the steps that will be needed for Prod.  Keep in mind too, that as you upgrade, it may be necessary to upgrade the database, Apache Tomcat, and java and any extensions that you are currently running.  Refer to the Release Advisor to determine compatible versions for each release.

 

Since you’re starting from such an old release, you may have to export all the data and try the import approach into a newer version. But you may run into issues with extensions.  You’ll need to validate the extensions you have installed in your current system and download/install the compatible version for the release you’re migrating to.  Some extensions that were available then, have been removed due to security reasons, etc., so if you are using any of those, it may drive the need to make some unexpected changes.  If you have any custom extensions, those will likely require update.

 

This is fairly high level but should provide some insight around the process.  Once you’ve opened a case, the engineer will be able to provide more detailed guidance for moving forward.

 

Regards.

 

--Sharon

 

Terms & ConditionsAccessibility statement