Integration
SYSPRO 6 and HubSpot
SYSPRO 6 to HubSpot, and changes in HubSpot back to SYSPRO 6. Both directions are separate sync products, configured independently, and this page shows what the shipped catalogue sets up for this pair.
- Phase 1 · forward sync
- Phase 2 · write-back
In plain wordsRecords from SYSPRO 6 are pushed into HubSpot, and changes made in HubSpot are carried back to SYSPRO 6. Each direction is its own sync with its own configuration.
This page documents what the shipped catalogue sets up. For the commercial overview of the same pair — editions, licensing and how to buy it — Commercient publishes SYSPRO 6 to HubSpot integration on commercient.com .
Phase 1 — SYSPRO 6 to HubSpot
Phase 2 — HubSpot back to SYSPRO 6
What you getChanges made in HubSpot to companies (customer accounts), Customer, products, deals (orders, invoices, quotes, opportunities), Quote, Sales Invoice, Sales order, Supplier, Purchase Order, Sales Order, contacts are carried back to SYSPRO 6.
| Process | What it delivers | Source → destination | Templates | Operations |
|---|---|---|---|---|
| Create New Customer | HubSpot companies to Syspro Customer | companies → Customer | 2 | create / update |
| Create New Product | HubSpot products to Syspro Product | products → Product | 1 | create |
| Create New Quote | HubSpot deals to Syspro Quote | deals → Quote | 1 | create |
| Create New Sales Invoice | HubSpot deals to Syspro Sales Invoice | deals → Sales Invoice | 1 | create |
| Create New Sales Order | HubSpot deals to Syspro Sales order | deals → Sales order | 1 | create |
| Create New Supplier | HubSpot companies to Syspro Supplier | companies → Supplier | 1 | create |
| Create or Update Purchase Order | HubSpot deals to Syspro Purchase Order | deals → Purchase Order | 1 | create |
| Delete Customer | HubSpot companies to Syspro Delete Customer | companies → Customer | 1 | delete |
| Delete Product | HubSpot products to Syspro Delete Product | products → Product | 1 | delete |
| Delete Purchase Order | HubSpot deals to Syspro Delete Purchase Order | deals → Purchase Order | 1 | delete |
| Delete Quote | HubSpot deals to Syspro Delete Quote | deals → Quote | 1 | delete |
| Delete Sales Order | HubSpot deals to Syspro Delete Sales Order | deals → Sales Order | 1 | delete |
| Delete Supplier | HubSpot companies to Syspro Delete Supplier | companies → Supplier | 1 | delete |
| (unnamed) | HubSpot contacts to Syspro Contact | contacts → Contact | 1 | create |
| (unnamed) | HubSpot Update companies to Syspro Update Customer | companies → Customer | 1 | update |
| (unnamed) | HubSpot Update deals to Syspro Update Sales Order | deals → Sales Order | 1 | update |
| Update Product | HubSpot Update products to Syspro Update Product | products → Product | 1 | update |
| Update Supplier | HubSpot Update companies to Syspro Update Supplier | companies → Supplier | 1 | update |
Objects moved
- companies
- Customer
- products
- Product
- deals
- Quote
- Sales Invoice
- Sales order
- Supplier
- Purchase Order
- Sales Order
- contacts
- Contact
Setting up SYSPRO 6 and HubSpot from the CLI
One wizard stands the tenant up, and it is the same five steps for every pair: register, capture the server IP, connect the CRM, declare the ERP connector, then import and enable the sync processes. What changes between pairs is the CRM’s connection mode and the ERP’s connector type.
1. Register the tenant
Registration creates the account, emails a verification link, and — once the Data Lake is seeded — prints a once-only bootstrap API key valid for seven days. The three consent flags are the registrant’s own decision, and the server refuses start without all three.
# which instance types sign-up accepts - run this first and use SYSPRO 6's code below
$ dlake register erps
# the three consent flags are the registrant’s decision - ask before passing them
$ dlake register start --generate-password \
$ --email <email> --company "<Company Name>" --phone <tel> \
$ --instance-type <code from dlake register erps> \
$ --consent-crm-backup --consent-erp-backup --consent-phone
# after the human clicks the verification link: watch for the seed and catch the key
$ dlake register status --watch
# the bootstrap key expires in 7 days - mint a durable one while it is still valid
$ dlake admin create_api_key --keyName "<tenant>-setup" --expirationDays 90
2. Connect HubSpot and declare SYSPRO 6
Steps 3 to 5 of the wizard are admin-plane tools, they are safe to re-run, and the server enforces their order — attempt the CRM step before the server IP is captured and it answers 409 naming the step you skipped.
# the authoritative answer to where a registration got to - first call when resuming
$ dlake admin registration_state
# step 3: record the server IP (a prerequisite for the CRM step)
$ dlake admin registration_capture_server_ip --ipAddress <ip>
# step 4: the catalog lists every CRM with its authMode and the fields it needs
$ dlake admin registration_crm_catalog
$ dlake admin registration_crm_select --crmName HubSpot
# HubSpot registers the platform's callback, not the CLI's - always the website leg
$ dlake registration oauth --crm HubSpot --no-browser
# this provider’s flow ends in a PIN, emailed by the complete call itself; the verb reads it hidden (or --pin-stdin)
$ dlake registration pin --crm HubSpot
$ dlake admin registration_crm_finalize
# step 5: the catalog lists the connector types and the fields each one needs
$ dlake admin registration_connector_catalog
$ dlake admin registration_connector_submit \
$ --connectorType <type from the catalog> --erpName <SYSPRO 6 code> --fields @fields.json
$ dlake admin registration_connector_provision
$ dlake admin registration_provisioning_status
3. Review and enable the Phase 1 processes
The shipped templates listed above are what crmpro_apply_template imports. Every one of them imports its process inactive, so an imported process does nothing until an operator activates it — read the process and its field mapping first, because an object with no mapped fields pushes nothing and records no error.
# the default-template catalog, and the mapping each template carries
$ dlake admin crmpro_templates --profile <tenant>
# what exists on the tenant now, and the master sync flag
$ dlake admin crmpro_list_processes --profile <tenant>
$ dlake admin crmpro_sync_status --profile <tenant>
# read a process and its field mapping BEFORE activating it
$ dlake admin crmpro_get_process --profile <tenant> --recordId <id>
$ dlake admin crmpro_field_mapping --profile <tenant> --recordId <id>
# turn the forward sync on
$ dlake admin crmpro_set_sync_enabled --profile <tenant> --enabled true
Processes run in a fixed order, and that order is a dependency order: a process that depends on another’s records sees them only once that process has run, so a parent flows on one run and its children on the next. The full order for this pair is on the Phase 1 page.
The wizard in full, including resuming a setup days later: Setting up an integration with dlake · Registering a new Data Lake · CRMPro (forward sync).
0Source on GitHub
This page is generated from the skill pages in the dlake CLI repository. Those pages are the authority; if they disagree with anything here, they are right.
Phase 1 source
dlake-crmpro-hubspot/erps/syspro-6.md
Phase 2 source
dlake-txdownloaderpro-hubspot/erps/syspro-6.md
Phase 1, in full
The complete upstream page for SYSPRO 6 into HubSpot, on this site.
Read the full pagePhase 2, in full
The complete upstream page for HubSpot back into SYSPRO 6, on this site.
Read the full pageSYSPRO 6 and HubSpot: common questions
Which way does data move between SYSPRO 6 and HubSpot?
Both ways, as two separate syncs. Phase 1 is CRMPro, the forward sync that pushes SYSPRO 6 records into HubSpot. Phase 2 is TxDownloaderPro, the write-back that carries changes made in HubSpot back to SYSPRO 6. They are configured independently, and a tenant can run either on its own.
What do Phase 1 and Phase 2 mean?
They are the two sync products the on-premises agent can run. Phase 1 is CommercientCRMPro, product 11, the forward sync from the source system into the CRM. Phase 2 is CommercientTxDownloaderPro, product 22, the write-back in the other direction. Registering a product says what to run; the Phase 1 and Phase 2 configuration says what it runs on.
Is there a ready-made template set for SYSPRO 6 to HubSpot?
Not a Standard one. The catalogue ships no Standard template for this pair, but it carries 9 community templates. A community template is authored in a tenant rather than shipped with the product and imports the same way as any other, so its names, notes, field mapping and SQL are tenant content. Read them with dlake admin crmpro_templates against the tenant that holds them.
Does the forward sync delete anything in the CRM?
Each template group carries its own insert, update and delete flags, and the integration page lists what each group does. Read a process with dlake admin crmpro_get_process before activating it.
What does the write-back from HubSpot create in SYSPRO 6?
The default set ships 18 processes for this pair: Create New Customer, Create New Product, Create New Quote, Create New Sales Invoice, Create New Sales Order, Create New Supplier, Create or Update Purchase Order, Delete Customer and 10 more. Each one takes a saved query against HubSpot, an inbound mapping document, and writes the result into SYSPRO 6.
Which objects does the write-back move?
companies, Customer, products, Product, deals, Quote, Sales Invoice, Sales order and 5 more. Those are the kinds of HubSpot record the shipped processes carry back to SYSPRO 6.
View moreShow less
What does "Phase 2 ready" mean?
It means the tenant has at least one TxDownloaderPro process. Creating a process with txdownloaderpro_create_process is what flips a customer to Phase 2 ready; registering the product alone does not, because registering says what to run and the configuration says what it runs on.
How do I see the write-back processes and whether they are failing?
dlake admin txdownloaderpro_list_processes returns every Phase 2 process with its 30-day unresolved-error count, which is the same grid the portal shows. txdownloaderpro_get_process returns one process in its edit shape, including the query and both mapping documents.
How do I stop the two directions looping?
dlake admin txdownloaderpro_circular_sync_check takes a process id and names the CRM objects that also have an active Phase 1 configuration. Those are the objects where a write-back can be picked up again by the forward sync, so check it before activating a process on this pair.
Can an AI agent set this up?
Yes, over the admin control plane or the CLI — the same tools either way. The crmpro_* and txdownloaderpro_* tools cover listing, reading, creating and updating processes. They need a full-scope key that belongs to a user holding the Admin role, and every write is audited.
Where is the authoritative source for this pair?
The skill pages in the dlake CLI repository, which is where this page is generated from. The forward sync page is linked at the foot of the integration page, and the same text is readable in the terminal with dlake skills show.
Related
Every ERP and CRM integration · CRMPro (forward sync) · TxDownloaderPro (writeback sync) · AI agents & MCP · HubSpot integrations on commercient.com
