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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Item numbers, revisions, BOMs and lifecycle states are set in PLM. HubSpot stores what sales and service need and never edits engineering data.
Customers, deals, quotes and tickets live in HubSpot. PLM receives only the customer context a change request needs.
Only released items reach the HubSpot catalog. Work-in-progress designs and restricted attributes stay inside PLM.
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.
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.
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.
Read Fusion Manage workspace and field definitions, or the Windchill domain metadata, for every object in scope, including lifecycle states and change workflow states.
Create product properties, Engineering Change and Quality Issue custom objects, association labels and the ticket pipeline for PLM-related service, in a HubSpot sandbox.
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.
Load released items as products and open change and quality records, then switch to webhooks and reconciliation.
Build launch, change-alert and service automations with notifications paused, run two weeks in parallel, then switch on.
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 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Item master & product catalog | ||||
| FM: item number (workspace field) · WC: Part Number | hs_sku | Product | PLM → HS | Primary match key with revision. Confirm the Fusion Manage field ID in discovery. |
| FM: item title · WC: Part Name | name | Product | PLM → HS | |
| FM: description field · WC: description attribute | description | Product | PLM → HS | Confirm field names in discovery. |
| FM: revision · WC: Version | plm_revision | Product | PLM → HS | Latest released revision. |
| FM: lifecycle state · WC: part lifecycle state | plm_lifecycle_state | Product | PLM → HS | State values read from the site's lifecycle definitions. |
| WC: View | plm_view | Product | PLM → HS | Design, manufacturing or service view; confirm which view feeds the catalog. |
| FM: workspace and item ID · WC: part ID | plm_item_id | Product | PLM → HS | Unique. Used for links back to PLM. |
| Product family or classification | plm_product_family | Product | PLM → HS | FM workspace field or WC classification node. Confirm in discovery. |
| BOM-derived catalog | ||||
| FM: item BOM · WC: part structure (PartUse) | plm_bom_summary | Product | PLM → HS | Top-level components only, as text. Full BOM stays in PLM. |
| WC: PartUse.Quantity | plm_bom_summary | Product | PLM → HS | Quantity per component in the summary. |
| Sellable option or variant | plm_option_codes | Product | PLM → HS | WC ProdPlatformMgmt or FM option fields where used. Confirm in discovery. |
| WC: parts list (PartListMgmt) | plm_service_parts | Product | PLM → HS | Service parts available for the product, for service teams. |
| Engineering change & launch | ||||
| FM: change request / change order item · WC: ChangeRequest, ChangeNotice | Engineering Change | Custom object | PLM → HS | One record per open change that affects a product in the catalog. |
| FM / WC change number | plm_change_number | Engineering Change | PLM → HS | Unique. |
| FM: workflow state · WC: change state | plm_change_state | Engineering Change | PLM → HS | Workflow state values confirmed in discovery. |
| WC: AffectedObjects · FM: affected items | Product associations | Engineering Change | PLM → HS | Links the change to the products it touches. |
| Need date or target release date | plm_change_need_date | Engineering Change | PLM → HS | Field names confirmed in discovery. |
| FM: NPI project phase and launch milestone | plm_launch_date, plm_launch_phase | Product | PLM → HS | Where the tenant runs product introduction projects. |
| Quality & customer complaints | ||||
| FM: NCR / CAPA item · WC: Nonconformance, CAPA | Quality Issue | Custom object | PLM → HS | Open records linked to a product in the catalog. |
| WC: CustomerExperience | Quality Issue | Custom object | ↔ Both | Customer-reported issues where Windchill Quality is installed. |
| Quality record number and state | plm_quality_number, plm_quality_state | Quality Issue | PLM → HS | Field names confirmed in discovery. |
| Related product and customer | Associations | Quality Issue | PLM → HS | Product and HubSpot company associations. |
| HubSpot → PLM change requests | ||||
| Ticket (product issue) | FM change request item · WC ChangeRequest | Ticket | HS → PLM | Created when a ticket is escalated to engineering. Ticket ID stored on the PLM record. |
| Customer requirement or feedback | Change request description | Ticket | HS → PLM | Customer, product and evidence included; no contact details beyond what engineering needs. |
| Quote line with a non-standard configuration | Change request for engineering review | Line item | HS → PLM | Triggered by a HubSpot quote approval rule. |
| PLM change request number and state | plm_change_request_number, plm_change_state | Ticket | PLM → HS | Status returns to the ticket so service can update the customer. |
Values the vendors publish are stated; anything site-specific is marked for confirmation.
| Topic | PLM | HubSpot |
|---|---|---|
| Access model | Fusion 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. |
| Interfaces | Fusion 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. |
| Authentication | Fusion 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 detection | Fusion 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. |
| Network | Fusion 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 limits | Not published. Confirm with Autodesk and PTC. | Per-10-second burst and daily limits by subscription tier. |
| Licensing | API 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. |
Severity reflects impact on the SOW, not technical difficulty alone.
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.
Fusion Manage workspaces and Windchill types are configured per site. Budget a metadata spike per site to build the field dictionary before mapping.
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.
PLM holds many more items than sales sells. Agree the release rule (state, item type, flag) so only sellable items reach the HubSpot catalog.
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 records can name suppliers and failure details. The client approves which quality fields HubSpot may hold.
HubSpot products come from released PLM items, with the current revision and lifecycle state, so quotes never use obsolete parts.
Deals that include a product with an open change order are flagged, so sellers set the right expectations on lead time and specification.
Escalated tickets and customer requirements arrive in PLM as change requests with the customer context attached, and their status comes back to HubSpot.
Launch dates and phases on the product record drive HubSpot launch campaigns and sales enablement at the right time.
Service agents see open quality issues for the customer's product on the ticket, and can link a complaint to an existing record.
Revenue by product, change volume by customer segment, and complaint trends meet in HubSpot dashboards.
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.
All custom properties use the plm_ prefix in a PLM property group. Values come from PLM; HubSpot does not edit them.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| plm_item_id | PLM Item ID | Product | Single-line text | FM workspace and item ID, or WC part ID; unique |
| plm_revision | Revision | Product | Single-line text | Latest released revision |
| plm_lifecycle_state | Lifecycle State | Product | Dropdown | Site lifecycle state values |
| plm_product_family | Product Family | Product | Dropdown | Workspace field or classification node |
| plm_bom_summary | BOM Summary | Product | Multi-line text | Top-level components and quantities |
| plm_launch_date | Launch Date | Product | Date picker | NPI launch milestone |
| plm_launch_phase | Launch Phase | Product | Dropdown | NPI project phase |
| plm_open_changes | Open Engineering Changes | Product | Number | Count of open changes affecting the item |
| plm_change_number | Change Number | Engineering Change | Single-line text | FM or WC change number; unique |
| plm_change_state | Change State | Engineering Change | Dropdown | Workflow or lifecycle state |
| plm_quality_number | Quality Record Number | Quality Issue | Single-line text | NCR, CAPA, NC or customer experience number; unique |
| plm_change_request_number | PLM Change Request | Ticket | Single-line text | Change request created from the ticket |
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.
Based on public documentation from Autodesk, PTC and HubSpot. Each item marked for confirmation is verified with the client's PLM administrator during discovery.
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.
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.
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.
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.
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.