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.
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.
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.
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.
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.
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.
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.
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.
QXtend Outbound (QXO)
Business events · XML QDocsPublishes 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
QXtend Inbound (QXI)
SOAP · XML QDocsAccepts 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
QAD Enterprise Platform APIs
Adaptive ERP · RESTThe 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
Customers and addresses
Sold-to · bill-to · ship-toThe 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
Quotes, orders and invoices
Sales quotes · sales orders · shipments · invoice historySales 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
Domains, entities and sites
Multi-domain structureQAD 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
Leads and opportunities in QAD
QAD sales lead and opportunity managementQAD'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
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.
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.
QAD's rules stay in QAD
Pricing, configuration, credit, tax and allocation are calculated by QAD. HubSpot stores the results and never recalculates them.
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.
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.
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.
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.
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.
HubSpot data model
Create properties, products, the deal and order pipelines, association labels and property groups in a HubSpot sandbox.
Build inbound flows
Build customers, ship-tos, items, quotes, orders, shipments and invoices into HubSpot with idempotent writes and an error replay queue.
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.
Parallel run & launch
Run two weeks in parallel with workflows paused, then switch on automations and hand over monitoring.
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 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers & addresses | ||||
| Customer code | qad_customer_code | Company | QAD → HS | Match key. Unique within a domain. |
| Customer name | name | Company | ↔ Both | HubSpot fills blanks only once QAD owns the account. |
| Bill-to address | address, city, state, zip, country | Company | QAD → HS | From the customer's address record. |
| Ship-to customers | Ship-to (association label) | Company | QAD → HS | Child companies or a custom object. Confirm in discovery. |
| Salesperson | hubspot_owner_id | Company | QAD → HS | QAD salesperson mapped to a HubSpot owner. |
| Credit terms, credit limit, credit hold | qad_credit_terms, qad_credit_hold | Company | QAD → HS | Read only in HubSpot. |
| Customer currency | qad_currency | Company | QAD → HS | Default currency for the customer. |
| Contact name, email, phone | firstname, lastname, email, phone | Contact | ↔ Both | Email is the contact match key. Confirm where QAD stores buyer contacts. |
| New customer from won deal | Customer (create) | Company | HS → QAD | QXtend Inbound customer QDoc into the chosen domain. |
| Items & pricing | ||||
| Item number | hs_sku | Product | QAD → HS | Match key for products. |
| Item description | name, description | Product | QAD → HS | |
| Product line | qad_product_line | Product | QAD → HS | Used for reporting and reorder rules. |
| List price | price | Product | QAD → HS | Base price only. Customer price lists stay in QAD. |
| Item status | qad_item_status | Product | QAD → HS | Inactive items hidden from new HubSpot quotes. |
| Sales quotes | ||||
| Sales quote number | qad_quote_number | Deal | ↔ Both | Links the HubSpot deal to the QAD quote. |
| Quote status and expiration | qad_quote_status, qad_quote_expires | Deal | QAD → HS | Drives deal stage rules. |
| Quote total | amount | Deal | QAD → HS | QAD's calculated value, including configured lines. |
| Quote lines | Line items | Line item | QAD → HS | Item, quantity and price per line. |
| Sales orders & shipments | ||||
| Sales order number | qad_order_number | Order | QAD → HS | Unique per domain. Associated to company, contact and deal. |
| Order date and due date | qad_order_date, qad_due_date | Order | QAD → HS | |
| Order total and currency | hs_total_price, hs_currency_code | Order | QAD → HS | Document currency kept as entered. |
| Order status | hs_pipeline_stage | Order | QAD → HS | Mapped to an order pipeline. |
| Order lines | Line items | Line item | QAD → HS | Item, quantity and price per line. |
| Shipment and ship date | qad_last_ship_date | Order | QAD → HS | Drives shipped notices and reorder timing. |
| Won deal | Sales order (create) | Deal | HS → QAD | QXtend Inbound sales order QDoc, only for paths chosen in the SOW. |
| Invoices & AR | ||||
| Invoice number and date | Invoice number, invoice date | Invoice | QAD → HS | HubSpot invoice object or custom object. Confirm in discovery. |
| Invoice amount and open balance | qad_invoice_balance | Invoice | QAD → HS | Balance due updates as payments post. |
| Open AR by customer | qad_open_ar | Company | QAD → HS | Rollup calculated in the integration layer. |
| Last invoice date | qad_last_invoice_date | Company | QAD → HS | Drives reorder and win-back workflows. |
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.
| Topic | QAD | HubSpot |
|---|---|---|
| Interfaces | QXtend 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. |
| Authentication | QXtend 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 model | Set 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. |
| Documentation | Current guides and API references are in QAD's document library for customers and partners. Some older QXtend guides are public. | Public developer documentation. |
| Multi-domain | Source 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 detection | QXtend 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 limits | Not published. Confirm with QAD. | Per-10-second burst and daily limits by subscription tier. |
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
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.
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.
QAD and HubSpot can both add accounts. The won-deal handoff through QXtend Inbound is the usual single creation path.
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.
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.
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
Open quotes, open orders, shipments, invoice balance and credit hold sit beside every email and meeting, so reps walk into calls prepared.
A won deal creates the QAD customer and sales order through QAD's own validation, so order entry starts from clean data.
Last order date and order history by product line drive HubSpot sequences that prompt customers to reorder spares and consumables.
Quotes near expiration enter HubSpot workflows, so no quote expires without a follow-up.
Reps see a credit hold before they promise a delivery, and a workflow alerts the account owner.
Orders and invoices in HubSpot let leaders compare pipeline, bookings and billed revenue in one dashboard.
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.
- Prospect and deal in HubSpot; the company becomes a QAD customer in the right domain when the deal is won.
- Quote in QAD for configured items, or in HubSpot for standard items, with the result on the deal.
- Sales order booked and shipped in QAD, shown on the HubSpot company and deal as an order.
- Invoices, balances and credit status flow back to HubSpot, so sales sees what was billed and paid.
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 name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| qad_customer_code | QAD Customer Code | Company | Single-line text | Customer code; unique within a domain |
| qad_domain | QAD Domain | Company | Dropdown | Domain the customer belongs to |
| qad_credit_terms | Credit Terms | Company | Single-line text | Customer credit terms |
| qad_credit_hold | Credit Hold | Company | Single checkbox | Customer credit hold flag |
| qad_currency | QAD Currency | Company | Dropdown | Customer default currency |
| qad_open_ar | Open AR | Company | Number (currency) | Sum of open invoice balances |
| qad_open_order_value | Open Order Value | Company | Number (currency) | Sum of open sales order lines |
| qad_last_invoice_date | Last Invoice Date | Company | Date | Most recent invoice |
| qad_quote_number | QAD Quote Number | Deal | Single-line text | Sales quote number |
| qad_quote_status | QAD Quote Status | Deal | Dropdown | Sales quote status |
| qad_order_number | QAD Order Number | Order | Single-line text | Sales order number; unique per domain |
| qad_product_line | Product Line | Product | Dropdown | Item product line |
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
Sources & verification
Based on public documentation. QDoc names, API endpoints, field names and limits are confirmed in the client's own QAD documentation and environment during discovery.
- QAD | Redzone: Adaptive ERP, Connected Workforce and Champion AI
- QAD Adaptive ERP: sales (leads, opportunities, quotes, orders, pricing)
- QAD Enterprise Platform
- Introducing the QAD Enterprise Platform (white paper)
- QAD QXtend User Guide: QXtend Outbound and QXtend Inbound
- HubSpot: orders API
- HubSpot Knowledge Base: create custom objects
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.
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.
.png?width=1920&height=553&name=cc-logo-color%20(2024).png)