Integration
IFS and HubSpot
IFS to HubSpot, and changes in HubSpot back to IFS. 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 IFS are pushed into HubSpot, and changes made in HubSpot are carried back to IFS. 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 IFS to HubSpot integration on commercient.com .
Phase 1 — IFS to HubSpot
What you getRecords from IFS become products, deals (orders, invoices, quotes, opportunities), line item, companies (customer accounts) in HubSpot. New records are created and existing ones updated.
| Group | Business outcome | Objects | Source tables and views |
|---|---|---|---|
| create item | The templates push products to HubSpot. New records are created and existing ones updated; none are deleted. | products | inventory parts |
| create order | The templates push deal to HubSpot. New records are created and existing ones updated; none are deleted. | deal | customer orders, customer information records |
| create order detail | The templates push line item to HubSpot. New records are created and existing ones updated; none are deleted. | line item | customer order lines |
| create customer | ERP customer information records, customer information addresses data becomes company in HubSpot. New records are created and existing ones updated; none are deleted. | company | customer information records, customer information addresses |
| create invoice | The templates push deal to HubSpot. New records are created and existing ones updated; none are deleted. | deal | invoices, customer information records |
| create invoice detail | The templates push line item to HubSpot. New records are created and existing ones updated; none are deleted. | line item | invoice items |
Destination objects
- products
- deal
- line item
- company
Phase 2 — HubSpot back to IFS
What you getChanges made in HubSpot to companies (customer accounts), Customer, contacts, deals (orders, invoices, quotes, opportunities), Customer order, Order, products, Part, Project, Sales contract, Service contract are carried back to IFS.
| Process | What it delivers | Source → destination | Templates | Operations |
|---|---|---|---|---|
| Update Customer | HubSpot Update companies to IFS Update Customer | companies → Customer | 2 | update |
| Create Customer Contact | HubSpot contacts to IFS Contact | contacts → Contact | 1 | create |
| Create New Contact | HubSpot contacts to IFS Person, Address and Contact | contacts → Contact | 1 | create |
| Create New Customer | HubSpot companies to IFS Customer | companies → Customer | 1 | create |
| Create New Customer Order | HubSpot deals to IFS Customer order | deals → Customer order | 1 | create |
| Create New Customer with Address | HubSpot companies to IFS Customer with Address | companies → Customer | 1 | create |
| Create New Customer With Address With Tax | HubSpot companies to IFS Customer with Address and Tax | companies → Customer | 1 | create |
| Create New Order | HubSpot deals to IFS Order | deals → Order | 1 | create |
| Create New Part | HubSpot products to IFS Part | products → Part | 1 | create |
| Create New Project | HubSpot deals to IFS Project | deals → Project | 1 | create |
| Create New Sales Contract | HubSpot deals to IFS Sales contract | deals → Sales contract | 1 | create |
| Create New Service Contract | HubSpot deals to IFS Service contract | deals → Service contract | 1 | create |
| Create Order with Customer Tax | HubSpot deals to IFS Order with Customer Tax | deals → Order | 1 | create |
| (unnamed) | — | deals → Customer order | 1 | create |
| (unnamed) | HubSpot contacts to IFS Contact, Person and Address | contacts → Contact | 1 | create |
| (unnamed) | HubSpot companies to IFS Customer with Address | companies → Customer | 1 | create |
| (unnamed) | HubSpot companies to IFS Customer with Address and Tax | companies → Customer | 1 | create |
| Update Contact with Address | HubSpot Update contacts to IFS Update Contact with Address | contacts → Contact | 1 | update |
| Update Customer Contact | HubSpot Update contacts to IFS Update Contact | contacts → Contact | 1 | update |
| Update Customer with Address | HubSpot Update companies to IFS Update Customer with Address | companies → Customer | 1 | update |
| Update Project | HubSpot Update deals to IFS Update Project | deals → Project | 1 | update |
Objects moved
- companies
- Customer
- contacts
- Contact
- deals
- Customer order
- Order
- products
- Part
- Project
- Sales contract
- Service contract
Setting up IFS 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 IFS'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 IFS
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 <IFS 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/ifs.md
Phase 2 source
dlake-txdownloaderpro-hubspot/erps/ifs.md
Phase 1, in full
The complete upstream page for IFS into HubSpot, on this site.
Read the full pagePhase 2, in full
The complete upstream page for HubSpot back into IFS, on this site.
Read the full pageIFS and HubSpot: common questions
Which way does data move between IFS and HubSpot?
Both ways, as two separate syncs. Phase 1 is CRMPro, the forward sync that pushes IFS records into HubSpot. Phase 2 is TxDownloaderPro, the write-back that carries changes made in HubSpot back to IFS. 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.
What does the forward sync into HubSpot actually create?
The shipped catalogue carries 6 template groups for this pair: create item, create order, create order detail, create customer, create invoice, create invoice detail. 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?
products, deal, line item, company. Those are the kinds of HubSpot record the shipped templates write for a IFS 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.
What does the write-back from HubSpot create in IFS?
The default set ships 21 processes for this pair: Update Customer, Create Customer Contact, Create New Contact, Create New Customer, Create New Customer Order, Create New Customer with Address, Create New Customer With Address With Tax, Create New Order and 13 more. Each one takes a saved query against HubSpot, an inbound mapping document, and writes the result into IFS.
View moreShow less
Which objects does the write-back move?
companies, Customer, contacts, Contact, deals, Customer order, Order, products and 4 more. Those are the kinds of HubSpot record the shipped processes carry back to IFS.
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
