Creo and Windchill Data: Export, History and AI Value

What are Creo and Windchill data worth to AI developers?

Mercor names PTC Creo on its hardware engineering listing and publishes what a company earns: "$45k–$1.3M", which "Depends on assembly count and completeness" (Mercor). That is a buyer program's published range for companies with 20 to 2,000 employees, not the price of a completed sale.

A Creo shop that ran Windchill for years usually holds more than the models. The database records who changed what, at which revision, under which change notice, and which configuration was released. That record of engineering decisions is scarce: it is not on the public web, and only companies that build products accumulate it.

This page is general information, not legal advice; read the PTC agreement your company signed, and have counsel check customer contracts before any data is shared.

Put your counts into the CAD archive value calculator for a rough band, or request a valuation from Origin once you know what the database holds.

What a Windchill database holds, and what it does not

Windchill keeps history as versions. "A version identifier such as A.1 is composed of a revision A and an iteration 1. A new revision is created whenever an object is revised. A new iteration is created when an object is checked out and checked back in." (PTC).

Change records sit beside the designs. PTC's change process runs from problem reports through change requests to change notices, and the second change administrator "is responsible for creating the implementation plan captured in the change notice" (PTC). A change notice tied to the parts it revised is close to a labeled example: the problem, the decision and the new geometry.

Usually missing: measured test data, supplier quality records and field returns. If they live in a quality system, a lab folder or ERP, list them separately; linked outcomes add to what a buyer will pay.

Creo model tree, Model Player and family tables: the design history inside the files

Each Creo file carries its own build history. "The Model Tree is a list of items in the model, in a hierarchical structure, that reflects, relations between the items or their order of regeneration", and in it "Each feature is represented by a node" (PTC). With the Model Player, "you can go backward or forward through the feature creation history in the model in order to observe how the model was created" (PTC).

Family tables multiply that value. PTC describes them as "collections of parts (or assemblies or features) that are essentially similar, but deviate slightly in one or two aspects, such as size or detail features", built from a generic and its instances (PTC). A table of fifty fastener sizes is a small dataset of controlled variation; a table of product variants is a larger one. Count instances separately from generics so a buyer sees both.

How to count Creo assemblies, parts and iterations in Windchill

Start with a search, but widen it. By default, "Windchill only searches against the latest iteration of every revision based on the criteria. Non-latest iterations are ignored." (PTC). A first count from the search box therefore understates your history; use the advanced search options that include all versions.

For repeatable numbers, ask your administrator for report templates. In Windchill, "A report is the output of a predefined search and is used for generating statistics and metrics against business information" (PTC).

How to export, archive or back up Windchill data with its history

Windchill has three built-in routes out, and none is a full history export on its own.

• Export and import. "Windchill export enables you to place all the data stored in high-level objects in the local database into JAR files", but "The data that is exported (stored) and then imported (extracted) does not include information required for change control." (PTC). For a CAD document seed, "No parts or links between parts and CAD documents are exported" unless you pick the combined product structure option.
• Packages. Windchill packages exist so you can share data "with people that work outside of your Windchill installation", for example on physical media (PTC). They suit a defined sample for a buyer's evaluation, not the whole history.
• Archive jobs. Through Purge Management, "if the archive functionality is installed at your site" you can "create an archive of the data to restore at a later time" (PTC). Without that option, a purge is permanent.

Purging is the step that loses value. "Only earlier iterations can be purged", and Windchill blocks purges of "Objects that are included in a family table" and "Iterations that are referenced from a change object" (PTC). If your site runs scheduled purges, the older iterations may already be gone; check before quoting depth.

For a complete copy, back up both halves. PTC says "the Windchill database should be backed up on a regular basis" and "Content files stored in an external file vault must be backed up using standard operating system tools and procedures." (PTC). A buyer-ready set is then exported from a restored copy after the exclusions below.

What a STEP export loses from Creo files

STEP carries solids, surfaces and some annotations, not the model tree. When Creo reads a STEP file, an exported solid comes back as a solid and surface-only data comes back as quilts (PTC). Rebuilding features takes a separate tool: "Feature Recognition is a process that semiautomatically identifies features imported from any Boundary Representation model (IGES, STEP, etc)." (PTC).

So a folder of STEP files shows what your products look like, while the Creo files show how your engineers built them. The Mercor listing names its target as "Full multi-part assemblies in native CAD with feature trees" (Mercor). Offer STEP only as a viewing copy next to the native set.

Who owns Creo and Windchill data, and what PTC's terms say

On-premises Windchill runs on your servers and your database, so the designs and records in it are your company's, subject to customer and supplier contracts. The SaaS offering is different, because PTC's agreement governs how data leaves its service.

PTC's Master Software as a Service Agreement (May 2026) says that "without the prior written consent of PTC", "the Customer is expressly prohibited from accessing or using (directly or indirectly, including via an application created by Customer or a third party) the application program interface of the Services to extract data from the Service for the purpose of training, fine-tuning, or creating an artificial intelligence (AI) model" (PTC, read 12 November 2026). Read that before anyone scripts an extraction from Windchill+.

The same agreement offers a standard exit: "the Customer can request up to two data exports", and "export and snapshot of Data (e.g., for Customer's long-term retention needs) are not offered as part of the standard PTC offering" (PTC). Ask PTC in writing how to obtain a complete export for a data license. Contract ownership of client designs is covered in who owns CAD files made for a client.

What to take out of a Windchill export first

Filter by product, context and library before exporting, not after.

• Customer-owned products: contexts or libraries that hold work done to a customer's design or under a contract that assigned the design.
• Supplier and catalog models: purchased-part libraries, supplier-provided Creo or STEP models and standard-part catalogs.
• Export-controlled data: defense articles, dual-use items and anything carrying an export classification. Work through the ITAR and EAR checklist first.
• Personal and customer names in change objects, comments and drawing title blocks; see de-identifying company data.

What AI companies pay for Creo and Windchill data

There is no published sale of a Windchill database to an AI company, and no published price for one. The evidence is one buyer program's published range.

A Windchill site with released product structures, intact iterations and linked change notices is the strong case. Creo files kept on a shared drive without Windchill still qualify, with less history. Compare with SolidWorks PDM vaults and Siemens NX and Teamcenter, or read the general CAD and engineering data guide.

Does your company hold records like these? See what your data is worth.

Origin Data Partners works with companies that own data and helps get it bought. We are independent of the services on this page, and a buyer may pay us when a deal closes (how Origin is paid). See what your data is worth.