A HubSpot Elite Solutions Partner built to help organizations unify strategy, systems, and execution. We design HubSpot systems that scale.

See how we've solved complex HubSpot challenges across migrations, integrations, CMS, automation, and optimization.

Join a team building smarter HubSpot systems. We value strategic thinkers who move proactively, care about quality, and want to do meaningful work.

Integration

HubSpot <> PLM Integration

Powered by Commercient
Integration Assessment
Integration Assessment · Product Lifecycle Management

PLM: Fusion Manage & Windchill × HubSpot

How a manufacturer running Autodesk Fusion Manage (formerly Fusion 360 Manage) or PTC Windchill can bring its product catalog, engineering change status, launch dates and quality records into HubSpot, and send customer requirements, quote configurations and service issues back to engineering as change requests.

Fusion Manage REST API v3Autodesk Platform Services OAuthWindchill REST Services (OData)ProdMgmt · ChangeMgmt · PartListMgmtWebhooks on both platformsBuilt per PLM
Platform ownerAutodesk · PTC
Integration typeCustom build on PLM REST APIs
Primary directionPLM → HubSpot, change requests back
FeasibilityBuildable, access by site
API accessOpen API
01 — Summary

Does PLM integrate with HubSpot?

Engineering knows what the company makes, what is changing and what is failing in the field. Sales and service work from HubSpot and usually see none of it. Both of the PLM platforms covered here expose that data through REST APIs, so the gap can be closed.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. Fusion Manage and Windchill REST Services are documented publicly. Access uses an Autodesk Platform Services app and a Windchill integration account; on-premises Windchill also needs a network path.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

The PLM system stays the source of product truth, and HubSpot puts that truth in front of sales and service, then sends customer input back to engineering.

Campaign Creators assessment

Autodesk Fusion Manage exposes workspaces, items, BOMs and workflow transitions through its REST API v3, authenticated through Autodesk Platform Services, and can push item events to a webhook. PTC Windchill exposes parts, BOMs, change objects, parts lists and (where Windchill Quality is installed) nonconformance and customer experience records through Windchill REST Services, an OData framework bundled with Windchill, with webhook subscriptions through its Event Management domain. A CC-built integration layer turns released items into HubSpot products, change and launch status into deal and ticket context, and HubSpot customer feedback into PLM change requests.

Scorecard
API & docsGood
Data model fitModerate
Network accessSite-specific
Build complexityMod–High

Ratings are CC judgments from Autodesk's and PTC's public documentation. Workspace and field definitions, installed Windchill domains, licensing and network access are confirmed per site in discovery.

Strength

Both platforms push events

Fusion Manage sends item create, update and clone events through Autodesk Platform Services webhooks. Windchill's Event Management domain posts to a callback URL for change, part and document events, so HubSpot learns about releases without constant polling.

Plan for

Every PLM site is configured differently

Fusion Manage workspaces and fields are defined by each tenant, and Windchill types, attributes and lifecycle states are set per site. Mapping starts from the site's own metadata, never from defaults.

Gate

Access and network path first

Fusion Manage needs an Autodesk Platform Services app with a user active on the tenant. Windchill often runs on-premises, so IT must open a secure path to Windchill REST Services and approve the integration account before any build.

02 — API modules

Which PLM APIs does the integration use?

Seven building blocks shape the integration. Two are the platform APIs, three carry the data HubSpot needs, one carries customer input back to engineering, and one is a scope decision about access.

Integration path

Fusion Manage REST API v3

Autodesk · /api/v3/workspaces/{workspaceId}/items

Workspaces, items and their fields, bills of materials, attachments and workflow transitions for every workspace the tenant uses, from items and BOMs to change orders and quality processes.

  • Read and create items in any workspace
  • Workflow transitions per item through the API
  • Item create, update and clone webhooks (system adsk.flc.production)
Integration path

Windchill REST Services

PTC · /Windchill/servlet/odata/{domain}

OData domains bundled with Windchill: ProdMgmt for parts and BOMs, ChangeMgmt for problem reports, change requests, change notices and variances, PartListMgmt for parts lists, and Event Management for webhook subscriptions.

  • Standard OData query options ($filter, $select, $expand)
  • Each domain publishes its own metadata (EDM)
  • Write calls carry a CSRF_NONCE header
Core

Product catalog from items & BOMs

Released items · Windchill parts

Released sellable items become HubSpot products, with number, description, revision and lifecycle state. The BOM stays in PLM; HubSpot receives the top-level sellable configuration and selected attributes.

  • Only released, sellable items enter the catalog
  • Revision and lifecycle state on every product
  • Obsolete items archived in HubSpot
Core

Engineering change & launch status

ECR / ECO · Fusion Manage change orders · Windchill change notices

Open change requests and change orders that affect a product, with their workflow state and need date, plus launch milestones from Fusion Manage product introduction projects where used.

  • Sales sees pending changes before quoting
  • Launch date and phase on the product record
  • Service sees changes that fix a known issue
Enrichment

Quality & customer complaints

Fusion Manage NCR / CAPA · Windchill NC and CEM

Nonconformance and corrective action records, and in Windchill Quality the customer experience records that capture customer-reported issues, linked to the customer and product in HubSpot.

  • Windchill quality domains require the Quality products
  • Open quality issues on the company and ticket
  • Restricted fields stay in PLM
Write-back

HubSpot → PLM change requests

Tickets · quote lines · feedback

Customer requirements, non-standard quote line configurations and product-related service tickets create a change request in PLM, with the customer, product and evidence attached, and the PLM status returns to HubSpot.

  • Fusion Manage: new item in the change request workspace
  • Windchill: change request in ChangeMgmt (write support confirmed per site)
  • Engineering stays in its own workflow
Scope decision

On-premises Windchill & licensing

Network path · integration user · seats

Windchill is often hosted inside the client network, and both platforms tie API access to a named or licensed user. The client decides how the integration reaches Windchill and which account it uses.

  • Secure inbound path or an agent inside the network
  • Integration user licensing confirmed with Autodesk or PTC
  • Webhook callbacks must be reachable from the PLM side
03 — Framework

How does the PLM HubSpot integration work?

A CC-built integration layer sits between the PLM platform and HubSpot. It receives PLM webhooks, reads full records through the REST APIs, applies the release and visibility rules, and writes to HubSpot in batches. HubSpot changes that need engineering go back as PLM change requests.

PLM platform
Items & BOMsFusion Manage items · Windchill parts
Change objectschange requests, change orders, change notices
Launch & lifecycleNPI projects, lifecycle states
Quality recordsNCR, CAPA, NC, customer experiences
CC integration layer
Authenticated clientAPS OAuth · Windchill site authentication
Event receiverwebhooks plus scheduled reconciliation
Release filterreleased, sellable items only
Identity resolveritem number · revision · customer
HubSpot writerbatch upserts, error replay
HubSpot
Productscatalog from released items
Deals, Line items & Quotespricing stays in HubSpot
Ticketsservice issues and quality links
Custom objectsEngineering change, quality issue
Lists, workflows & reportslaunch, change and quality views
PLM → HubSpot (catalog, change and launch status, quality)HubSpot → PLM (change requests from customer input, status follow-up)
Principle

PLM owns the product definition

Item numbers, revisions, BOMs and lifecycle states are set in PLM. HubSpot stores what sales and service need and never edits engineering data.

Principle

HubSpot owns the customer

Customers, deals, quotes and tickets live in HubSpot. PLM receives only the customer context a change request needs.

Principle

Release is the gate

Only released items reach the HubSpot catalog. Work-in-progress designs and restricted attributes stay inside PLM.

04 — Process

What does PLM HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. The first PLM site is delivered end to end before a second site or platform is added.

1

Discovery & ownership

Confirm which PLM platform and sites are in scope, which workspaces or Windchill types matter, and which system owns each record. Agree what counts as a released, sellable item.

Gate to next phaseSigned ownership table and release rule
2

Access & network

Fusion Manage: register an Autodesk Platform Services app and confirm the integration user is active on the tenant. Windchill: agree the network path, the integration account and the authentication method with IT.

Gate to next phaseAuthenticated test call to each platform
3

Metadata & field dictionary

Read Fusion Manage workspace and field definitions, or the Windchill domain metadata, for every object in scope, including lifecycle states and change workflow states.

Gate to next phaseSigned field dictionary with state values
4

HubSpot data model

Create product properties, Engineering Change and Quality Issue custom objects, association labels and the ticket pipeline for PLM-related service, in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build

Build the integration layer: webhook receiver, scheduled reconciliation, release filter, HubSpot writer and the change request write-back, with idempotent writes and an error replay queue.

Gate to next phaseCatalog, change status and write-back working in sandbox
6

Backfill

Load released items as products and open change and quality records, then switch to webhooks and reconciliation.

Gate to next phaseHubSpot product count matches the released item count
7

Workflows, parallel run & launch

Build launch, change-alert and service automations with notifications paused, run two weeks in parallel, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the PLM HubSpot integration sync?

Fusion Manage field IDs are defined per workspace by each tenant, and Windchill attributes come from each domain's metadata. Where a name is site-specific the row describes the field and the note says to confirm it in discovery.

PLM fieldHubSpot propertyObjectDirectionNotes
Item master & product catalog
FM: item number (workspace field) · WC: Part Numberhs_skuProductPLM → HSPrimary match key with revision. Confirm the Fusion Manage field ID in discovery.
FM: item title · WC: Part NamenameProductPLM → HS
FM: description field · WC: description attributedescriptionProductPLM → HSConfirm field names in discovery.
FM: revision · WC: Versionplm_revisionProductPLM → HSLatest released revision.
FM: lifecycle state · WC: part lifecycle stateplm_lifecycle_stateProductPLM → HSState values read from the site's lifecycle definitions.
WC: Viewplm_viewProductPLM → HSDesign, manufacturing or service view; confirm which view feeds the catalog.
FM: workspace and item ID · WC: part IDplm_item_idProductPLM → HSUnique. Used for links back to PLM.
Product family or classificationplm_product_familyProductPLM → HSFM workspace field or WC classification node. Confirm in discovery.
BOM-derived catalog
FM: item BOM · WC: part structure (PartUse)plm_bom_summaryProductPLM → HSTop-level components only, as text. Full BOM stays in PLM.
WC: PartUse.Quantityplm_bom_summaryProductPLM → HSQuantity per component in the summary.
Sellable option or variantplm_option_codesProductPLM → HSWC ProdPlatformMgmt or FM option fields where used. Confirm in discovery.
WC: parts list (PartListMgmt)plm_service_partsProductPLM → HSService parts available for the product, for service teams.
Engineering change & launch
FM: change request / change order item · WC: ChangeRequest, ChangeNoticeEngineering ChangeCustom objectPLM → HSOne record per open change that affects a product in the catalog.
FM / WC change numberplm_change_numberEngineering ChangePLM → HSUnique.
FM: workflow state · WC: change stateplm_change_stateEngineering ChangePLM → HSWorkflow state values confirmed in discovery.
WC: AffectedObjects · FM: affected itemsProduct associationsEngineering ChangePLM → HSLinks the change to the products it touches.
Need date or target release dateplm_change_need_dateEngineering ChangePLM → HSField names confirmed in discovery.
FM: NPI project phase and launch milestoneplm_launch_date, plm_launch_phaseProductPLM → HSWhere the tenant runs product introduction projects.
Quality & customer complaints
FM: NCR / CAPA item · WC: Nonconformance, CAPAQuality IssueCustom objectPLM → HSOpen records linked to a product in the catalog.
WC: CustomerExperienceQuality IssueCustom object↔ BothCustomer-reported issues where Windchill Quality is installed.
Quality record number and stateplm_quality_number, plm_quality_stateQuality IssuePLM → HSField names confirmed in discovery.
Related product and customerAssociationsQuality IssuePLM → HSProduct and HubSpot company associations.
HubSpot → PLM change requests
Ticket (product issue)FM change request item · WC ChangeRequestTicketHS → PLMCreated when a ticket is escalated to engineering. Ticket ID stored on the PLM record.
Customer requirement or feedbackChange request descriptionTicketHS → PLMCustomer, product and evidence included; no contact details beyond what engineering needs.
Quote line with a non-standard configurationChange request for engineering reviewLine itemHS → PLMTriggered by a HubSpot quote approval rule.
PLM change request number and stateplm_change_request_number, plm_change_stateTicketPLM → HSStatus returns to the ticket so service can update the customer.
06 — Auth & API

How are authentication and API limits handled?

Values the vendors publish are stated; anything site-specific is marked for confirmation.

TopicPLMHubSpot
Access modelFusion Manage: an Autodesk Platform Services app; calls run as a user who is active on the tenant. Windchill: an integration account on the Windchill site, with access to the contexts in scope.Private app access token or OAuth public app, scoped per object. Custom objects need an Enterprise subscription.
InterfacesFusion Manage REST API v3 (JSON). Windchill REST Services: OData domains under /Windchill/servlet/odata/, with metadata per domain.REST APIs: CRM objects, products, line items, quotes, tickets, associations.
AuthenticationFusion Manage: OAuth through Autodesk Platform Services, 2-legged or 3-legged. Windchill: the site's configured authentication, or OAuth where the site has set up an authorization server; write calls need a CSRF nonce.Bearer token on every call.
Change detectionFusion Manage: Autodesk Platform Services webhooks for item create, update and clone, scoped to a workspace. Windchill: EventSubscription with a CallbackURL, for entities in the supported domains.Webhooks for HubSpot-side changes.
NetworkFusion Manage is cloud-hosted. Windchill is often on-premises: the integration needs a secure path in, or an agent inside the network, and callbacks need a reachable endpoint.Cloud-hosted; outbound calls from the integration layer only.
Rate limitsNot published. Confirm with Autodesk and PTC.Per-10-second burst and daily limits by subscription tier.
LicensingAPI access runs as a licensed user on both platforms. Windchill Quality domains need the Quality products installed. Confirm with Autodesk or PTC.Products, quotes and custom objects depend on the HubSpot subscription.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Network access to on-premises WindchillHigh

An on-premises Windchill server is not reachable from the internet by default. IT must approve a secure path or an agent before the build. Make this a client-owned dependency in the SOW, with a date.

Site-specific data modelsHigh

Fusion Manage workspaces and Windchill types are configured per site. Budget a metadata spike per site to build the field dictionary before mapping.

Integration user and licensingMedium

Both platforms run API calls as a licensed user, and webhooks act with that user's permissions. Confirm the account and seat with Autodesk or PTC.

What counts as sellableMedium

PLM holds many more items than sales sells. Agree the release rule (state, item type, flag) so only sellable items reach the HubSpot catalog.

Write-back acceptanceMedium

Engineering decides which customer input becomes a change request. Agree the trigger, the required fields and who triages in PLM before switching on write-back.

Quality data sensitivityLow

Quality records can name suppliers and failure details. The client approves which quality fields HubSpot may hold.

Opportunities in HubSpot

A catalog sales can trustHigh value

HubSpot products come from released PLM items, with the current revision and lifecycle state, so quotes never use obsolete parts.

Change alerts before the quoteHigh value

Deals that include a product with an open change order are flagged, so sellers set the right expectations on lead time and specification.

Customer input reaches engineeringHigh value

Escalated tickets and customer requirements arrive in PLM as change requests with the customer context attached, and their status comes back to HubSpot.

Launch-ready campaignsMedium value

Launch dates and phases on the product record drive HubSpot launch campaigns and sales enablement at the right time.

Quality context for serviceMedium value

Service agents see open quality issues for the customer's product on the ticket, and can link a complaint to an existing record.

One reporting layerMedium value

Revenue by product, change volume by customer segment, and complaint trends meet in HubSpot dashboards.

Rollout order

Start with the catalog, then add change and quality.

Every later step depends on HubSpot products matching PLM items, so the catalog goes first. Each step after it uses the same identity rules and data model.

  1. Catalog: released, sellable items become HubSpot products with revision and lifecycle state.
  2. Change and launch status: open change orders and launch milestones appear on products and flag affected deals.
  3. Quality: nonconformance, corrective action and customer complaint records link to products, companies and tickets.
  4. Write-back: escalated tickets, customer requirements and non-standard quote lines open PLM change requests.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the plm_ prefix in a PLM property group. Values come from PLM; HubSpot does not edit them.

Internal nameLabelObjectTypeSource / logic
plm_item_idPLM Item IDProductSingle-line textFM workspace and item ID, or WC part ID; unique
plm_revisionRevisionProductSingle-line textLatest released revision
plm_lifecycle_stateLifecycle StateProductDropdownSite lifecycle state values
plm_product_familyProduct FamilyProductDropdownWorkspace field or classification node
plm_bom_summaryBOM SummaryProductMulti-line textTop-level components and quantities
plm_launch_dateLaunch DateProductDate pickerNPI launch milestone
plm_launch_phaseLaunch PhaseProductDropdownNPI project phase
plm_open_changesOpen Engineering ChangesProductNumberCount of open changes affecting the item
plm_change_numberChange NumberEngineering ChangeSingle-line textFM or WC change number; unique
plm_change_stateChange StateEngineering ChangeDropdownWorkflow or lifecycle state
plm_quality_numberQuality Record NumberQuality IssueSingle-line textNCR, CAPA, NC or customer experience number; unique
plm_change_request_numberPLM Change RequestTicketSingle-line textChange request created from the ticket
09 — Scope builder

Interactive scope builder

Choose the modules and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
PLM × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

PLM HubSpot integration FAQ

Does PLM integrate with HubSpot?

Yes, through an open API: Autodesk Fusion Manage and PTC Windchill both publish REST documentation publicly. Fusion Manage access runs through an Autodesk Platform Services app with no vendor approval needed; Windchill needs an integration account and, where the system runs on-premises, a network path IT must open. Campaign Creators builds a custom integration layer on Fusion Manage REST API v3 and Windchill REST Services (OData) once access is in place.

What data syncs between PLM and HubSpot?

Released, sellable items sync into HubSpot products with revision and lifecycle state. Open engineering change requests, change orders and launch milestones sync as context on products and deals. Quality and customer-complaint records (NCR, CAPA, and in Windchill Quality, customer experience records) link to products and tickets. HubSpot sends customer requirements, non-standard quote lines and escalated tickets back to PLM as change requests, with status returning to the ticket.

Which system owns which data?

PLM owns the product definition: item numbers, revisions, BOMs and lifecycle states are set there and HubSpot never edits them. HubSpot owns the customer: deals, quotes, quote lines and tickets live in HubSpot, and PLM receives only the customer context a change request needs. Release is the gate — only released items reach the HubSpot catalog; work-in-progress designs and restricted attributes stay inside PLM.

What does setting up the PLM HubSpot integration involve?

Seven phases, each closed by a client sign-off: confirming scope and which system owns each record, securing API and network access (an Autodesk Platform Services app, and for Windchill an integration account plus any on-premises network path), building the field dictionary from the site's own workspace or domain metadata, the HubSpot data model with Engineering Change and Quality Issue custom objects, the build, a backfill of released items and open records, and a two-week parallel run before workflows go live.

How long does the integration take and what does it cost?

Timeline and cost depend on which PLM platform is in scope, how many sites or workspaces are involved, whether Windchill is on-premises, and how much site-specific metadata needs mapping before the build starts. Campaign Creators confirms these in discovery and provides a fixed scope before work begins.

Ready to Get More From HubSpot?

Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.