Integration
Sage 100 2016 and HubSpot
Sage 100 2016 to HubSpot. 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
- No Phase 2 for this pair
In plain wordsRecords from Sage 100 2016 are pushed into HubSpot. There is no shipped write-back in the other direction for this pair.
Phase 1 — Sage 100 2016 to HubSpot
What you getRecords from Sage 100 2016 become companies (customer accounts), products, deals (orders, invoices, quotes, opportunities), line item in HubSpot. New records are created and existing ones updated.
| Group | Business outcome | Objects | Source tables and views |
|---|---|---|---|
| create customer | ERP customers data becomes company in HubSpot. New records are created and existing ones updated; none are deleted. | company | customers |
| create item | The templates push products to HubSpot. New records are created and existing ones updated; none are deleted. | products | items |
| create order | The templates push deal to HubSpot. New records are created and existing ones updated; none are deleted. | deal | sales order history headers |
| create order detail | The templates push line item to HubSpot. New records are created and existing ones updated; none are deleted. | line item | sales order history lines, items |
| create invoice | The templates push deal to HubSpot. New records are created and existing ones updated; none are deleted. | deal | invoice history headers |
| create invoice detail | The templates push line item to HubSpot. New records are created and existing ones updated; none are deleted. | line item | invoice history lines, items |
| create quote | The templates push deal to HubSpot. New records are created and existing ones updated; none are deleted. | deal | sales order headers |
| create quote detail | The templates push line item to HubSpot. New records are created and existing ones updated; none are deleted. | line item | sales order lines, items |
| create open invoice | The templates push deal to HubSpot. New records are created and existing ones updated; none are deleted. | deal | open invoices, customers |
| create open invoice detail | The templates push line item to HubSpot. New records are created and existing ones updated; none are deleted. | line item | invoice history lines, items |
Destination objects
- company
- products
- deal
- line item
Phase 2 — HubSpot back to Sage 100 2016
Setting up Sage 100 2016 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 Sage 100 2016'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 Sage 100 2016
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 <Sage 100 2016 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).
Source 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.
Sage 100 2016 and HubSpot: common questions
Which way does data move between Sage 100 2016 and HubSpot?
One way. Phase 1 (CRMPro) pushes Sage 100 2016 records into HubSpot. The repository ships no TxDownloaderPro write-back for this pair, so there is no supported Phase 2 from HubSpot back to Sage 100 2016.
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.
What does the forward sync into HubSpot actually create?
The shipped catalogue carries 10 template groups for this pair: create customer, create item, create order, create order detail, create invoice, create invoice detail, create quote, create quote detail and 2 more. Each group sets up its own sync process, and the integration page says what each one delivers.
Which HubSpot objects does the forward sync write?
company, products, deal, line item. Those are the kinds of HubSpot record the shipped templates write for a Sage 100 2016 source; nothing else is written unless you add templates of your own.
Does the forward sync delete anything in the CRM?
No. Every shipped group for this pair creates new records and updates existing ones; none are deleted.
Is there a write-back from HubSpot to Sage 100 2016?
No. The repository ships no TxDownloaderPro page for HubSpot into Sage 100 2016, so changes made in HubSpot are not carried back to Sage 100 2016 by a supported process. Only the Phase 1 forward sync exists for this pair.
View moreShow less
Can an AI agent set this up?
Yes, over the admin control plane or the CLI — the same tools either way. The crmpro_* 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
