Integration
Acumatica and Zoho CRM
Acumatica to Zoho CRM. 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 Acumatica are pushed into Zoho CRM. There is no shipped write-back in the other direction for this pair.
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 Acumatica to Zoho CRM integration on commercient.com .
Phase 1 — Acumatica to Zoho CRM
What you getRecords from Acumatica become users, Accounts, contacts, Commercient Acumatica customer object, Acumatica opportunity (custom object), Commercient Acumatica customer contact object, Commercient Acumatica sales order header object, Commercient Acumatica sales order detail object, Commercient Acumatica invoice header object, Commercient Acumatica invoice detail object in Zoho CRM. New records are created and existing ones updated.
| Group | Business outcome | Objects | Source tables and views |
|---|---|---|---|
| Users | The templates push users to Zoho CRM. New records are created and existing ones updated; none are deleted. | users | — |
| Accounts | The templates push Accounts to Zoho CRM. New records are created and existing ones updated; none are deleted. | Accounts | sales invoices, customers, billing contacts, sales reps, customer billing addresses, customer shipping addresses |
| Contacts | The templates push Contacts to Zoho CRM. New records are created and existing ones updated; none are deleted. | Contacts | contacts, customer main addresses |
| Acumatica Customer | The templates push Commercient Acumatica customer object to Zoho CRM. New records are created and existing ones updated; none are deleted. | Commercient Acumatica customer object | customers |
| Acumatica Opportunity | The templates push Acumatica opportunity (custom object) to Zoho CRM. New records are created and existing ones updated; none are deleted. | Acumatica opportunity (custom object) | opportunities, sales reps |
| Acumatica Contacts | The templates push Commercient Acumatica customer contact object to Zoho CRM. New records are created and existing ones updated; none are deleted. | Commercient Acumatica customer contact object | contacts, customer main addresses |
| Acumatica Sales order | The templates push Commercient Acumatica sales order header object to Zoho CRM. New records are created and existing ones updated; none are deleted. | Commercient Acumatica sales order header object | sales orders |
| Acumatica Sales order line | The templates push Commercient Acumatica sales order detail object to Zoho CRM. New records are created and existing ones updated; none are deleted. | Commercient Acumatica sales order detail object | sales order details |
| Acumatica Invoice | The templates push Commercient Acumatica invoice header object to Zoho CRM. New records are created and existing ones updated; none are deleted. | Commercient Acumatica invoice header object | sales invoices |
| Acumatica invoice line | The templates push Commercient Acumatica invoice detail object to Zoho CRM. New records are created and existing ones updated; none are deleted. | Commercient Acumatica invoice detail object | sales invoice lines |
Destination objects
- users
- Accounts
- Contacts
- Commercient Acumatica customer object
- Acumatica opportunity (custom object)
- Commercient Acumatica customer contact object
- Commercient Acumatica sales order header object
- Commercient Acumatica sales order detail object
- Commercient Acumatica invoice header object
- Commercient Acumatica invoice detail object
Phase 2 — Zoho CRM back to Acumatica
Setting up Acumatica and Zoho CRM 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 Acumatica'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 Zoho CRM and declare Acumatica
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 <Crm>
# an OAuth CRM: the catalog’s callbackMode says which leg this one takes
$ dlake registration oauth --crm <Crm>
$ 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 <Acumatica 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.
Acumatica and Zoho CRM: common questions
Which way does data move between Acumatica and Zoho CRM?
One way. Phase 1 (CRMPro) pushes Acumatica records into Zoho CRM. The repository ships no TxDownloaderPro write-back for this pair, so there is no supported Phase 2 from Zoho CRM back to Acumatica.
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 Zoho CRM actually create?
The shipped catalogue carries 10 template groups for this pair: Users, Accounts, Contacts, Acumatica Customer, Acumatica Opportunity, Acumatica Contacts, Acumatica Sales order, Acumatica Sales order line and 2 more. Each group sets up its own sync process, and the integration page says what each one delivers.
Which Zoho CRM objects does the forward sync write?
users, Accounts, Contacts, Commercient Acumatica customer object, Acumatica opportunity (custom object), Commercient Acumatica customer contact object, Commercient Acumatica sales order header object, Commercient Acumatica sales order detail object and 2 more. Those are the kinds of Zoho CRM record the shipped templates write for a Acumatica 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 Zoho CRM to Acumatica?
No. The repository ships no TxDownloaderPro page for Zoho CRM into Acumatica, so changes made in Zoho CRM are not carried back to Acumatica 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 · Zoho CRM integrations on commercient.com
