HubSpot + DELMIAWorks integration

DELMIAWorks is the manufacturing ERP Dassault Systèmes sells to small and mid-sized manufacturers, the product once called IQMS, which Dassault acquired in 2019. It keeps ERP and MES in one shared database, so the order, the production run, the quality record and the shipment sit together. Its customers are mostly discrete manufacturers, in plastics, automotive, aerospace, medical devices and industrial equipment, and it carries a CRM module of its own that logs calls, quotes and meetings against that same database.

Marketing and sales teams at these companies often run HubSpot for forms, email nurture, web analytics and the pipeline. That leaves the account’s operational truth in DELMIAWorks: what the customer has on order, what shipped, which invoice is overdue and which return is still open. A seller preparing for a call asks customer service, who has the answer on screen.

Two facts shape this project more than any field does. Dassault keeps the DELMIAWorks knowledge base and user community behind customer logins, so the interface details are read with your credentials during discovery. And DELMIAWorks can run on your own servers, on Dassault’s hosted and managed service in AWS, or in a data centre of your choosing, and each of those changes who can schedule what.

Six records do the work, and together they answer the questions sellers bring to customer service. Customers become HubSpot companies and contacts become contacts. Sales orders, shipments and invoices land as custom objects on the company, and open returns become tickets, so service sees them beside the conversation.

Nothing flows back in a first build. DELMIAWorks’ own CRM, quoting and EDI modules already maintain customers and take orders inside the ERP, and a second writer would compete with them. Orders that arrive by EDI never passed through a HubSpot deal, which is why orders live on the company rather than on deals: the company shows the whole order book, not only the orders sales touched.

Keys are the numbers DELMIAWorks issues, carried in the export and held in custom HubSpot properties: customer, order, shipment, invoice and RMA numbers. Names are for people to read. Contacts match on email, with the customer number breaking the tie when two contacts share an address.

The pattern is an SFTP extract, transform and load, because it is the one shape that works in every DELMIAWorks deployment before anyone has read the licensed documentation. Your DELMIAWorks administrator, or Dassault’s implementation team, schedules an export that writes one file per object and a manifest of row counts to an SFTP drop. If the documentation shows a better interface for your release, it can replace the file later without changing the HubSpot side.

Our load service collects each file, hashes it so a repeat is skipped, checks its columns against the agreed contract and quarantines rows that fail, with a reason. It then batch upserts on the DELMIAWorks numbers and runs a separate association pass: contacts, orders and tickets to companies, shipments and invoices to orders. Rows loaded are reconciled against the manifest on every run, and a replay endpoint reloads any file on request.

The deciding fact is that DELMIAWorks’ interfaces are documented only to licensed customers. Any route, packaged or built, starts with somebody reading that documentation under your login and confirming what an export or an interface can carry.

A custom integration fed by a scheduled export is the route we recommend. It works on premises, on the hosted service and in a third-party data centre, and it keeps the keys, the delete signal and the reconciliation under our control. The marketplace app from Commercient is a third-party alternative for a standard mapping, with its runtime and roadmap outside your team. An iPaaS has no public DELMIAWorks interface to call, so it faces the same discovery and then bills per task.

1. Scope. We establish the deployment, the release and who can schedule an export, and we read the relevant documentation under your login.
2. Architect. We write the file contract: objects, columns, keys, the delete signal, the schedule and the manifest, plus the SFTP route.
3. Build. The load service is written against sample exports, into a HubSpot sandbox with a portal allowlist from the first commit.
4. Validate. We reconcile each file against its manifest, then compare open orders and invoice totals with DELMIAWorks reports.
5. Operate. We watch every run, replay any file on request, and re-check the contract whenever DELMIAWorks is upgraded.