Skip to content
SteepGraph

PTC Windchill

Windchill Data Migration and Integration.

We do two things on Windchill. We move product data into it, or out of it, with structures, history and files intact. And we connect it to the systems around it. Both run on frameworks we built and maintain, not on scripts written for your project.

  • 30+ PLM migration programmes
  • 2B+ records migrated
  • ITAR & EAR controlled data
  • ISO 27001 certified
Talk to a Windchill expert

What we do on Windchill

Two Jobs, Done on Frameworks.

We don’t implement or customise Windchill. We take on the two pieces of work where Windchill programmes most often slip: moving the data, and connecting the systems.

  1. 01

    Data Migration

    Product data into Windchill, or out of it, without losing what makes it engineering data.

    You are here if

    • You are moving to Windchill from Pro/INTRALINK, SOLIDWORKS PDM, Vault, SmarTeam or Teamcenter
    • You are leaving Windchill for Aras, 3DEXPERIENCE or Teamcenter
    • You have to prove to engineering, and to an auditor, that nothing was lost
    How the migration worksData Migration Framework

  2. 02

    Integration

    Windchill exchanging parts, BOMs, documents and changes with the systems that act on them.

    You are here if

    • A release in Windchill still reaches ERP by email, spreadsheet or re-keying
    • Your existing interfaces are custom code nobody wants to touch before an upgrade
    • A failed exchange is found by the plant, not by an alert
    How the integration worksIntegration Framework

The migration risk

A Migration Can Load Without Errors and Still Be Wrong.

Windchill data is not rows in a table. It is CAD files linked to each other, parts linked to CAD, revisions and iterations with their history, lifecycle states and access rules. A load can accept every record and still break the links between them.

Migration waveIllustrative

Wave 2 · Released assemblies

Load logComplete · 0 errors

What reconciliation found

  • CAD references312 assemblies with missing components
  • Revision historyLatest iteration only
  • CAD-to-part links1,840 parts with no CAD
  • Lifecycle statesReleased loaded as In Work
  • FilesAll present in vault
Ready for engineeringNo

The load log counts records. Reconciliation checks the engineering.

Data migration, on the framework

Six Stages. The Last One Proves the Rest.

Every run goes through the same six stages, configured for your source and for Windchill’s rules. Problems are found and fixed before the data lands, and the result is reconciled record by record.

  1. Extract

    Is the right data coming out?

    • Parts, CAD and documents
    • Files from the vault
    • API, database, files or custom

  2. Transform

    Did it change as expected?

    • Types and attributes mapped
    • Revision schemes adapted
    • Lifecycle states mapped

  3. Validate

    Will Windchill accept it?

    • Numbering and naming rules
    • Required attributes
    • Duplicates and bad characters

  4. Correct

    Fixed before it lands?

    • Missing and invalid values
    • Broken links rebuilt
    • Revisions renumbered

  5. Load

    In the right order?

    • Parts before structures
    • CAD structures and part links
    • Delta loads for cutover

  6. Reconcile

    Does it match?

    • Record-level counts and deltas
    • Structures and files
    • Every exception, listed

What you decide, not the tool

  • Selective or big bang
  • Full history or latest release
  • Phased or single cutover
  • Windchill as source or target
  • Controlled access for ITAR & EAR data
  • Revision scheme kept or adapted

The screens, the rules and the sources: Data Migration Framework

The integration risk

The Costly Integration Failure Is the Silent One.

A change is released in Windchill. The material or BOM update never reaches ERP, and nobody is told. It surfaces weeks later, when the plant builds the previous revision.

ApproachA change is releasedAn exchange failsA field or rule changesWindchill is upgraded
Point-to-point codeA change is releasedA script pushes it, if it runsAn exchange failsFound by the people downstreamA field or rule changesA developer edits the codeWindchill is upgradedEvery interface retested, often rewritten
On the Integration FrameworkA change is releasedA configured flow, event-driven or scheduledAn exchange failsAlerted, retried and loggedA field or rule changesA mapping edited on screenWindchill is upgradedFlows re-pointed and retested in configuration

Integration, on the framework

Every Exchange Goes Through One Place You Can See.

Windchill connects once, to the framework. Each exchange is a configured flow: picked up, checked, mapped to the other system’s model and delivered, with every run recorded.

Runs as a Docker container, in your environment or hosted by SteepGraph.

The dashboard, the flows and the mappings: Integration Framework

Windchill migration and integration

Tell Us What Has to Move, or What Has to Connect.

Bring the source system, the rough volumes and the systems on the other side. We’ll show you how the frameworks handle it, and say plainly where they don’t.

Talk to a Windchill expert

FAQ

Frequently Asked Questions

No. On Windchill we do data migration and integration, both on our own frameworks. Configuration and customisation of Windchill itself stay with your team or your implementation partner, and we work alongside them.

Pro/INTRALINK, SOLIDWORKS PDM, Autodesk Vault, SmarTeam, Teamcenter, 3DEXPERIENCE / ENOVIA, Oracle PLM, Documentum, and legacy or home-grown systems. Data comes out through an API, the database, files and reports, or custom extraction, whichever the source allows.

Yes. Windchill is a source as well as a target for the Data Migration Framework, with Aras Innovator, 3DEXPERIENCE and Teamcenter among the targets.

No. A migration can be selective, only the products, parts and structures you need, or a complete big-bang move. You also choose between full revision history and latest release only.

Data-quality rules run before and after the load, and every run ends with a reconciliation of source against target: record-level counts and deltas, structures, files, and a list of every exception. You sign off on that report, not on a load log.

That depends on volumes and on the cutover you choose. The framework supports delta and incremental loads, so data can move in phases and the final window only has to carry what changed since the last load.

Yes. We have migrated ITAR and EAR controlled data, with access restricted to authorised personnel on both the source and the target side.

ERP systems including SAP, Oracle, Microsoft Dynamics, Epicor, IFS and Odoo; ALM tools including Jira, Azure DevOps, Polarion and ClickUp; EPLAN for ECAD; and anything reachable over REST, SOAP, a database, a message queue or the file system.

It ships as a Docker container, so it runs in your own environment or hosted by SteepGraph. Flows can be event-driven or scheduled.

It is caught, not lost. The framework records every run, raises an alert on a failure, retries where that is safe, and keeps an audit log, so your team sees the problem before anyone downstream does.

We’d like to use Google Analytics cookies to understand how visitors use this site. No analytics cookies are set unless you accept. Privacy Policy