Integration Products | Campaign Creators

QAD HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 17, 2026, 2:11:17 PM
Integration Assessment
Integration Assessment · ERP

QAD × HubSpot

How customers, ship-to addresses, items, sales quotes, sales orders, shipments and invoices in QAD Adaptive ERP, or in the earlier QAD Enterprise and Standard Editions, connect to HubSpot, so sales and marketing work from the full quote-to-cash picture while QAD keeps running manufacturing and finance.

Manufacturing ERPQAD Adaptive ERPQAD Enterprise PlatformQXtend Inbound and OutboundSOAP and XML QDocsMulti-domain
Platform ownerQAD Inc. (QAD | Redzone)
Integration typeCustom, CC-built integration layer
Primary directionTwo-way, QAD owns orders and financials
FeasibilityBuildable, access through QAD
API accessGated API
01 — Summary

Does QAD integrate with HubSpot?

QAD, which now presents itself as QAD | Redzone, builds ERP for manufacturers. QAD Adaptive ERP is its current ERP, built on the QAD Enterprise Platform. Many manufacturers still run the earlier QAD Enterprise Edition or Standard Edition on their own Progress-based servers. Each one holds the customer master, items, sales quotes, sales orders, shipments and receivables. Neither HubSpot nor QAD offers its own app for this connection, so it is a custom build on QAD's integration services.

API access
Open APIOpen with conditionsGated API

Documentation and credentials come only through the vendor, under a license, partner agreement or customer login.

Gated API. Current QAD API and QXtend documentation is published to QAD customers and partners, and integration access is set up on the client's QAD environment by its administrator, or with QAD for a cloud tenant. Some older QXtend guides can be downloaded publicly.

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

QAD sends business events out and accepts validated documents in, so a two-way QAD-to-HubSpot integration is buildable on every current QAD edition.

Campaign Creators assessment

QAD QXtend is QAD's own integration service. QXtend Outbound publishes changes to business objects such as customers and sales orders as XML documents (QDocs), and QXtend Inbound accepts SOAP-wrapped QDocs and enters them through QAD's own maintenance programs, so QAD's validation runs on every write. QAD Adaptive ERP adds the QAD Enterprise Platform, which QAD describes as built on REST APIs and microservices with API management. What sets the pace is access: QAD's technical documentation sits behind customer and partner logins, and QXtend and API access are configured on the client's QAD environment. The other decisions are business ones: which system owns leads and opportunities, and how QAD domains map into one HubSpot portal.

Scorecard
Data richnessHigh
API accessVia QAD
Public docsLimited
Build complexityMod–High

Ratings are CC judgments from QAD's public materials. Service names, QDoc names, field names and limits are confirmed in the client's own QAD documentation and environment during discovery, because they differ by edition and release.

Strength

QAD's own rules run on every write

QXtend Inbound enters data the way a user would, through programs such as Sales Order Maintenance. A won HubSpot deal becomes a QAD order that passed the same checks as one keyed by hand.

Plan for

Domains, editions and two places for leads

Many QAD customers run several domains, and QAD has its own leads and opportunities. The domain map and the owner of pipeline are agreed before any build starts.

Gate

QXtend and API access come first

The client's QAD administrator, or QAD for a cloud tenant, confirms QXtend is in place, creates an integration user and opens network access. Nothing is built until a test QDoc round-trips in a test domain.

02 — API modules

Which QAD APIs does the integration use?

Seven QAD capabilities matter to a HubSpot build. Five carry the integration, one shapes it, and one is a scope decision the client makes up front.

Core

QXtend Outbound (QXO)

Business events · XML QDocs

Publishes changes to QAD business objects to subscribers. Profiles choose which data each subscriber receives.

  • Raised by business events or database triggers
  • Delivered to a web service URL or a polled directory
  • Sales orders, customers, invoice history and more
Write-back

QXtend Inbound (QXI)

SOAP · XML QDocs

Accepts SOAP-wrapped QDocs and enters them field by field through QAD's own maintenance programs.

  • QAD validation runs on every write
  • Each QDoc carries the integration user's credentials
  • A target domain can be named per request
Core

QAD Enterprise Platform APIs

Adaptive ERP · REST

The platform under QAD Adaptive ERP, which QAD describes as built on REST APIs and microservices, with integration and API management among its platform services.

  • Adaptive ERP and Adaptive UX run on it
  • Endpoints listed in the client's QAD documentation
  • Confirm which objects are exposed for the tenant
Core

Customers and addresses

Sold-to · bill-to · ship-to

The customer master with its addresses, terms and credit settings. Orders carry separate sold-to, bill-to and ship-to customers.

  • Customer code is the match key to HubSpot companies
  • Ship-to customers are their own business object
  • Credit limit and credit hold travel with the record
Core

Quotes, orders and invoices

Sales quotes · sales orders · shipments · invoice history

Sales quotes and orders with their lines, shipments against the order, and invoice history with open balances.

  • Quote and order status on the HubSpot deal
  • Shipments drive customer updates
  • Invoice history and balances on the company
Shapes data

Domains, entities and sites

Multi-domain structure

QAD separates operations into domains, ties each to financial entities, and runs production and stock at sites. One customer can exist in more than one domain.

  • Domain named on every QXtend exchange
  • Currency carried on customers and documents
  • Maps to HubSpot business units or a property
Scope decision

Leads and opportunities in QAD

QAD sales lead and opportunity management

QAD's sales capabilities include leads and opportunities, from prospect to business partner. The client decides which system owns pipeline.

  • Option A: HubSpot owns leads and deals; QAD starts at the quote or order
  • Option B: QAD keeps opportunities; HubSpot shows status for marketing
  • Recorded in the SOW before build
03 — Framework

How does the QAD HubSpot integration work?

A CC-built integration layer subscribes to QXtend Outbound events, or calls Enterprise Platform APIs where the tenant exposes them, matches each record to HubSpot, and writes in batches. Actions that flow back, such as a new customer or sales order from a won deal, go in as QXtend Inbound QDocs so QAD's own programs validate them.

QAD Adaptive ERP · Enterprise or Standard Edition
Customers & addressessold-to, bill-to, ship-to, credit
Items & pricesitem master, price lists
Quotes, orders & shipmentssales quotes, sales orders, lines
Invoices & ARinvoice history, open balances
CC integration layer
Event receiverQXO QDocs over HTTPS
Domain routerQAD domain → HubSpot business unit or property
Identity matchercustomer code · email · domain
HubSpot writerbatch upserts, associations, replay queue
Write-back servicewon deal → QXI customer or order QDoc
HubSpot
Companies & contactscustomers, ship-tos, buyers
Productsitems and list prices
Deals, quotes & line itemspipeline and QAD quotes
Orders & invoicesbooked orders, shipments, balances
Reports & workflowsreorder, credit hold and quote follow-up
QAD → HubSpot (primary flow)HubSpot → QAD (new customers and sales orders from won deals)
Principle

Each record has one owner

HubSpot owns prospects, contacts and pipeline. QAD owns customer accounts once created, items, prices, orders, shipments and invoices. The SOW lists the owner of every field.

Principle

QAD's rules stay in QAD

Pricing, configuration, credit, tax and allocation are calculated by QAD. HubSpot stores the results and never recalculates them.

Principle

Events in, documents out

Changes reach HubSpot as QAD publishes them. Writes go through QXtend Inbound or a platform API, never directly to the database.

04 — Process

What does QAD HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. Read-only flows go live first, so sales sees QAD data in HubSpot before any write-back is switched on.

1

Discovery & access

Confirm the QAD edition and release, cloud or on-premises hosting, the domains in scope, and the HubSpot hubs and tiers. The client's QAD administrator, or QAD for a cloud tenant, confirms QXtend, creates an integration user and opens network access to a test domain.

Gate to next phaseA test QDoc round-trips between QAD and the integration layer
2

Data ownership

Agree which system owns leads and opportunities, which creates customers and ship-tos, where quotes for configured items are built, and how domains map to HubSpot.

Gate to next phaseSigned field ownership matrix
3

Field inventory

Read the QDoc schemas and API documentation for the client's release, list custom fields in use, and choose the QXtend Outbound profiles that feed HubSpot.

Gate to next phaseApproved field list with QAD and HubSpot names
4

HubSpot data model

Create properties, products, the deal and order pipelines, association labels and property groups in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build inbound flows

Build customers, ship-tos, items, quotes, orders, shipments and invoices into HubSpot with idempotent writes and an error replay queue.

Gate to next phaseAll inbound flows running in sandbox with clean reconciliation
6

Build write-back and backfill

Build the won-deal path into QAD through QXtend Inbound, then load current customers, open quotes, open orders and an agreed invoice history.

Gate to next phaseHubSpot totals reconcile to QAD reports within an agreed tolerance
7

Parallel run & launch

Run two weeks in parallel with workflows paused, then switch on automations and hand over monitoring.

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

What does the QAD HubSpot integration sync?

QAD field and QDoc names differ by edition and release, so the source column describes each field plainly. Exact names come from the client's QDoc schemas and QAD documentation in the field inventory phase.

QAD fieldHubSpot propertyObjectDirectionNotes
Customers & addresses
Customer codeqad_customer_codeCompanyQAD → HSMatch key. Unique within a domain.
Customer namenameCompany↔ BothHubSpot fills blanks only once QAD owns the account.
Bill-to addressaddress, city, state, zip, countryCompanyQAD → HSFrom the customer's address record.
Ship-to customersShip-to (association label)CompanyQAD → HSChild companies or a custom object. Confirm in discovery.
Salespersonhubspot_owner_idCompanyQAD → HSQAD salesperson mapped to a HubSpot owner.
Credit terms, credit limit, credit holdqad_credit_terms, qad_credit_holdCompanyQAD → HSRead only in HubSpot.
Customer currencyqad_currencyCompanyQAD → HSDefault currency for the customer.
Contact name, email, phonefirstname, lastname, email, phoneContact↔ BothEmail is the contact match key. Confirm where QAD stores buyer contacts.
New customer from won dealCustomer (create)CompanyHS → QADQXtend Inbound customer QDoc into the chosen domain.
Items & pricing
Item numberhs_skuProductQAD → HSMatch key for products.
Item descriptionname, descriptionProductQAD → HS
Product lineqad_product_lineProductQAD → HSUsed for reporting and reorder rules.
List pricepriceProductQAD → HSBase price only. Customer price lists stay in QAD.
Item statusqad_item_statusProductQAD → HSInactive items hidden from new HubSpot quotes.
Sales quotes
Sales quote numberqad_quote_numberDeal↔ BothLinks the HubSpot deal to the QAD quote.
Quote status and expirationqad_quote_status, qad_quote_expiresDealQAD → HSDrives deal stage rules.
Quote totalamountDealQAD → HSQAD's calculated value, including configured lines.
Quote linesLine itemsLine itemQAD → HSItem, quantity and price per line.
Sales orders & shipments
Sales order numberqad_order_numberOrderQAD → HSUnique per domain. Associated to company, contact and deal.
Order date and due dateqad_order_date, qad_due_dateOrderQAD → HS
Order total and currencyhs_total_price, hs_currency_codeOrderQAD → HSDocument currency kept as entered.
Order statushs_pipeline_stageOrderQAD → HSMapped to an order pipeline.
Order linesLine itemsLine itemQAD → HSItem, quantity and price per line.
Shipment and ship dateqad_last_ship_dateOrderQAD → HSDrives shipped notices and reorder timing.
Won dealSales order (create)DealHS → QADQXtend Inbound sales order QDoc, only for paths chosen in the SOW.
Invoices & AR
Invoice number and dateInvoice number, invoice dateInvoiceQAD → HSHubSpot invoice object or custom object. Confirm in discovery.
Invoice amount and open balanceqad_invoice_balanceInvoiceQAD → HSBalance due updates as payments post.
Open AR by customerqad_open_arCompanyQAD → HSRollup calculated in the integration layer.
Last invoice dateqad_last_invoice_dateCompanyQAD → HSDrives reorder and win-back workflows.
06 — Auth & API

How are authentication and API limits handled?

QAD access is set up on the client's QAD environment. Values QAD does not publish are marked for confirmation.

TopicQADHubSpot
InterfacesQXtend Outbound (XML QDocs pushed to a web service URL or directory) and QXtend Inbound (SOAP-wrapped XML QDocs). Adaptive ERP adds QAD Enterprise Platform REST APIs. Confirm which interfaces the client's release and hosting support.REST APIs: CRM objects, associations, products, line items, orders, invoices, imports.
AuthenticationQXtend Inbound QDocs carry a QAD user name and password, which can be encoded. Outbound web service subscribers can use socket-level credentials and SSL. Platform API authentication is confirmed with QAD for the tenant.Private app access token or OAuth 2.0 public app, scoped per object.
Access modelSet up by the client's QAD administrator for a dedicated integration user, or with QAD for a cloud tenant. QXtend licensing and setup are confirmed with QAD.Self-serve in the client portal. Custom objects need an Enterprise hub.
DocumentationCurrent guides and API references are in QAD's document library for customers and partners. Some older QXtend guides are public.Public developer documentation.
Multi-domainSource and destination domains are set per QXtend subscriber or request. Entities and sites sit under each domain.One portal. Domains map to business units or a domain property.
Change detectionQXtend Outbound raises QDocs from business events or database triggers, filtered by profile. A query service supports on-demand reads.Writes are immediate; batch endpoints handle volume.
Rate limitsNot published. Confirm with QAD.Per-10-second burst and daily limits by subscription tier.
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

Documentation and access sit with QADHigh

QAD's technical guides and API references need a customer or partner login, and QXtend is configured on the client's environment. Make access a client-owned dependency in the SOW, with a date.

Two places can own pipelineHigh

QAD has its own leads and opportunities. Without one owner, reps update both and reports disagree. The SOW names the owner, and the other system shows status only.

Two places can create customersHigh

QAD and HubSpot can both add accounts. The won-deal handoff through QXtend Inbound is the usual single creation path.

Multiple domainsMedium

One customer can exist in several domains with different codes and currencies. The match rule and the HubSpot company structure are agreed before the build.

Edition and release differencesMedium

Enterprise Edition, Standard Edition and Adaptive ERP expose different QDocs and APIs. Budget a short field inventory against the client's own release rather than relying on standard lists.

Upgrade testingLow

QAD releases updates to Adaptive ERP and to QXtend. Include a regression check of the integration in the client's upgrade routine.

Opportunities in HubSpot

The full account on one HubSpot recordHigh value

Open quotes, open orders, shipments, invoice balance and credit hold sit beside every email and meeting, so reps walk into calls prepared.

Won deals become QAD orders without rekeyingHigh value

A won deal creates the QAD customer and sales order through QAD's own validation, so order entry starts from clean data.

Aftermarket and service-parts reorder campaignsHigh value

Last order date and order history by product line drive HubSpot sequences that prompt customers to reorder spares and consumables.

Quote follow-up from QAD quotesMedium value

Quotes near expiration enter HubSpot workflows, so no quote expires without a follow-up.

Credit hold visibility for salesMedium value

Reps see a credit hold before they promise a delivery, and a workflow alerts the account owner.

Revenue reporting by product line and domainMedium value

Orders and invoices in HubSpot let leaders compare pipeline, bookings and billed revenue in one dashboard.

Quote-to-cash

HubSpot runs the deal. QAD runs the order.

The integration follows the path a sale already takes in a manufacturing business. Each step has one system in charge, and the other system sees the result.

  1. Prospect and deal in HubSpot; the company becomes a QAD customer in the right domain when the deal is won.
  2. Quote in QAD for configured items, or in HubSpot for standard items, with the result on the deal.
  3. Sales order booked and shipped in QAD, shown on the HubSpot company and deal as an order.
  4. Invoices, balances and credit status flow back to HubSpot, so sales sees what was billed and paid.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the qad_ prefix in a QAD property group. Rollups are calculated in the integration layer so HubSpot and QAD reports agree.

Internal nameLabelObjectTypeSource / logic
qad_customer_codeQAD Customer CodeCompanySingle-line textCustomer code; unique within a domain
qad_domainQAD DomainCompanyDropdownDomain the customer belongs to
qad_credit_termsCredit TermsCompanySingle-line textCustomer credit terms
qad_credit_holdCredit HoldCompanySingle checkboxCustomer credit hold flag
qad_currencyQAD CurrencyCompanyDropdownCustomer default currency
qad_open_arOpen ARCompanyNumber (currency)Sum of open invoice balances
qad_open_order_valueOpen Order ValueCompanyNumber (currency)Sum of open sales order lines
qad_last_invoice_dateLast Invoice DateCompanyDateMost recent invoice
qad_quote_numberQAD Quote NumberDealSingle-line textSales quote number
qad_quote_statusQAD Quote StatusDealDropdownSales quote status
qad_order_numberQAD Order NumberOrderSingle-line textSales order number; unique per domain
qad_product_lineProduct LineProductDropdownItem product line
09 — Scope builder

Interactive scope builder

Choose the QAD objects 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
QAD × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

QAD HubSpot integration FAQ

Does QAD integrate with HubSpot?

Yes, through a custom integration. Neither HubSpot nor QAD offers its own app for this connection, so Campaign Creators builds on QAD QXtend, QAD's own integration service, and on the QAD Enterprise Platform APIs in QAD Adaptive ERP.

What data syncs between QAD and HubSpot?

QAD customers, ship-to addresses and items sync to HubSpot companies and products, along with sales quotes, sales orders, shipments and invoices. Won HubSpot deals are sent back to QAD through QXtend Inbound, so QAD's own validation runs on every order.

Which QAD editions does the integration support?

QAD Adaptive ERP and the earlier QAD Enterprise and Standard Editions, in the cloud or on the client's own servers. The edition and release decide which services are available, so they are confirmed in the first phase.

What does setting up the QAD HubSpot integration involve?

Seven phases, each closed by a client sign-off: discovery and access, data ownership, field inventory, the HubSpot data model, inbound flows, write-back and backfill, and a parallel run before launch. Read-only flows go live first, so sales sees QAD data before any write-back is switched on.

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

Timeline and cost depend on the QAD edition and hosting, the domains in scope, custom fields and the history to load. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.