Success Path
End to end high-level guidance to a successful transition

Prepare to Go-Live

Prepare your user ends and support team for what is to come.


Note:  This is not meant to be an all-inclusive, fully detailed guide to transition Windchill to your private Azure cloud.  PTC has many options for additional Windchill-specific help, which are the Support team, your PTC Customer Success Manager, Success Management, or any of our well-qualified partner service providers.  For further questions about Azure, please contact your Microsoft representative.

Update support documentation

Document how your system is now designed and supported. This documentation is crucial for supporting and using the system. We have recommended you took account of the items in your system. Now you will compile the various documentation pieces your team has created throughout this project.

Application documentation should include:

  • Customizations: Note which customizations were removed and how to use the system without them
  • New Features: If you opted to upgrade your Windchill, your end users might benefit from new features. Let them know what they are and point them to appropriate training

Document how to use the application and how to get support in case of issues. This is the only documentation your end-users should need. Application documentation should be consistently updated: when you make a change to the application, update the documentation to reflect that change.

Communicate change to end users

In a perfect world, this transition will have minimal effect on your end-users, but it is essential to let them know they may experience a change in experience to minimize the number of support requests.

Promote to production

After you have performed all the necessary testing in the test/QA environment, you’re ready to promote the code to production. This step “publishes” your application—deploying it to your users. Ensure you have a backup in place before promoting to production. If you have followed a thorough DevOps process, your work should already be backed up.

To promote to production, the developer/architect will import data and entities to the production server. If an issue arises, do not make changes to the application in the production environment. First, adjust and test them in the development environment. Second, promote the code to the test/QA environment and test thoroughly. Third, promote the code to production.   The same practices you have applies with respect to user downtime for on-premises Windchill upgrades can be applied here.

Once the technical team has successfully deployed the application, notify project team members and stakeholders. The application is now collecting real data, communicating with your assets, and is available for use.

Did you find this helpful?


Product Documentation

Find step-by-step instructions and information about moving Windchill to Azure cloud in the Help Centers.

Ask the Community

Visit the PTC Windchill Community to get product assistance, share ideas, and browse information about using Windchill.

Technical Support

Log a case with eSupport using your Service Contract Number. Don’t have it? Ask the Community.

Contact Us

Have a question? Submit your contact information and we’ll reach out within 1 business day. You’re never obligated to purchase or commit.