PTC Windchill Microsoft Dynamics 365 Integration

We connect PTC Windchill to Microsoft Dynamics 365 Finance & Supply Chain so released parts, BOMs and approved manufacturers reach operations once. We do the Windchill side and the integration design, and we work alongside your Dynamics partner.

Talk to a consultant

Last reviewed by Element Consulting

The problem we solve

You run Windchill for engineering and Dynamics 365 for operations. Both can hold items, BOMs, routings and change, so the first question is which system owns each one. Until that is settled, people re-key released parts into Dynamics and the two copies drift.

There is no connector to buy that answers it for you. Neither Microsoft nor PTC ships a turnkey Windchill to Dynamics 365 integration, so the design is yours to make: who owns what, which state fires a release, and what software sits in the middle.

We are building this now for a multi-site aerospace and defense manufacturer with several business units on one Windchill and one Dynamics. What we learned getting the details agreed is in Windchill and Dynamics 365: who owns what.

On SAP or Oracle instead? See Windchill SAP integration and Windchill Oracle ERP integration.

What we do

  1. 01

    The ownership split, agreed first

    Windchill owns the part master, the engineering BOM, the approved manufacturer list and engineering change. Dynamics 365 owns routings, work centers, inventory, cost, the approved vendor list and purchasing. We get that written down and signed before anyone builds an interface.

  2. 02

    Publishing from Windchill

    We configure PTC's ESI so that only released items, BOMs and manufacturer parts leave Windchill, and so a lifecycle promotion waits on a successful send.

  3. 03

    Middleware selection and mapping

    We help you choose a middleware built for Dynamics 365, then map every field one to one into its standard data entities. Conditional mapping rules save a field and cost far more in logic and testing.

  4. 04

    Numbering and classification that fit Dynamics

    Dynamics 365 caps item and product numbers at 20 characters, and its categories are flatter than a Windchill classification tree. We settle both before migration, along with the characters Dynamics will not accept in manufacturer part numbers.

  5. 05

    Several legal entities on one Windchill

    If your business units are separate legal entities in Dynamics, ESI can send each part to the right one with standard targets and a small extension for entity-specific attributes.

  6. 06

    Reference data coming back

    Inventory on hand, and cost if engineers need it, land on the Windchill part as read-only attributes that only the integration can update. Data coming back never blocks an engineering release.

Where Windchill and Dynamics 365 integrations go wrong

Two change processes

Change runs in both Windchill and Dynamics 365 Engineering Change Management, and the integration ends up refereeing which revision is released.

In-work data sent to ERP

Purchasing asks for unreleased BOMs to start long-lead buys, and the integration turns into a stream of corrections. We give purchasing a view of preliminary data and keep releases going through change.

Routings edited in two places

MPMLink process plans and Dynamics routes hold the same operations and times. One system owns them, decided by where your manufacturing engineers work.

A missing test environment

Windchill, the middleware and Dynamics each need one, with someone named to keep them running. A blocked middleware environment has been one of the top schedule risks on our current program.

Why Element?

Process and people first, technology second. The mapping is the smaller job. The larger one is getting engineering, supply chain and IT to agree on one owner for each fact, and we lead that conversation.

Windchill is what we do. We have worked in PTC Windchill since 2003, across 100+ PLM implementations, with PTC Certified Windchill Implementation Practitioners on the team. We don't resell software or middleware, so the recommendation comes without a license sale attached.

Who does this work. Senior consultants who have run Windchill and ERP integrations end to end. Compare the ERP options in the Windchill ERP integration guide.

Talk to a consultant

About Element Consulting. Element Consulting is an independent PTC partner that has implemented, upgraded, integrated, and rescued PTC Windchill since 2003: 100+ PLM implementations, a senior-only team, headquartered in West Des Moines, Iowa. Managing Partner Eric Horn is a PTC Certified Windchill Implementation Practitioner. The firm works mainly in aerospace and defense, federal and national-security programs, medical devices, and industrial equipment, including ITAR-controlled and government-cloud delivery, and does not resell software.

FAQ

Is there a standard connector between Windchill and Dynamics 365?

No. Neither Microsoft nor PTC ships a turnkey one. PTC's Enterprise Systems Integration (ESI) publishes released data from Windchill, and a middleware product or custom code loads it into Dynamics 365. We recommend middleware for most manufacturers, because a custom integration becomes a maintenance job for years.

Who does what between Element and our Dynamics partner?

We work on the Windchill side and the integration design: the ownership split, ESI publishing, the field mapping and the release trigger. Your Dynamics partner owns the Dynamics configuration. The hard calls get made with both teams in the room.

Should we run engineering change in Dynamics 365 or in Windchill?

If Windchill runs engineering change, don't run it in Dynamics too. Let Windchill manage change and send Dynamics the results: the new item revision, the new BOM and the new lifecycle state.

We're still on Dynamics AX. Should we integrate now or after the move to Dynamics 365?

Design for Dynamics 365. AX integrations are built on older technology that the move retires. If the ERP move is close, design the Windchill side for Dynamics 365 data entities and build the integration once.

Can this run in a government cloud?

Yes, with extra plumbing. On our current program Windchill runs in Azure Government, the integration file drops sit on cloud storage, and the middleware is reached through an API gateway. See Windchill on Azure Government Cloud.

40/40

Migration phases in an AI-verified Windchill 12 to 13.1 upgrade. Zero failures, zero production outage.

Read the case study

80%

Lower cost of poor quality at one manufacturer once manufacturing reviewed the data before release.

100+

PLM implementations since 2003, from new Windchill rollouts to upgrades, ERP integration and rescue.

*Results from specific engagements. Clients are named only with their permission, and your results will depend on your scope and starting point.