Integration
SYSPRO 7 and above and Salesforce
SYSPRO 7 and above to Salesforce. 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 SYSPRO 7 and above are pushed into Salesforce. 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 SYSPRO 7 and above to Salesforce integration on commercient.com .
Phase 1 — SYSPRO 7 and above to Salesforce
What you getRecords from SYSPRO 7 and above become accounts, custom objects, products, price book entries in Salesforce. New records are created and existing ones updated.
| Group | Business outcome | Objects |
|---|---|---|
| Account | ERP customers become Salesforce Accounts, and the full AR customer record lands beside them in the managed package so sales sees terms, class, area, branch and salesperson from the ERP. Accounts and the AR objects are created and updated; nothing is deleted. | accounts, custom objects |
| Sal Area | ERP sales areas become lookup records the AR customer points at. Created and updated, never deleted. | custom objects |
| Branch/Division Details | Where the ERP tracks branches, divisions or locations on the AR customer master, those become records the Account hierarchy can be read through. Created and updated, never deleted. | custom objects |
| Salesorder | Sales orders and their lines arrive in full, so service and sales can see order status, requested ship dates, PO numbers, discounts and per-line quantities without leaving the CRM. Created and updated, never deleted. | custom objects |
| Invoice | Open and historical invoices, their payments and their transaction detail sync; a balance or terms change on an open invoice is reflected on the next run. Created and updated, never deleted. | custom objects |
| Product | ERP stock codes become Salesforce Products, with the inventory master and per-warehouse quantities alongside them. Created and updated, never deleted. | products, custom objects |
| Pricebook | ERP selling prices become price book entries. Shipped as create/update pairs — the create leg inserts only, the update leg updates only — for both the standard price book and custom ones. | price book entries |
| Customer Multi Ship Addresses | Every ship-to address on an AR customer appears as a related list on the Account. Created and updated, never deleted. | custom objects |
| Sales Move | ERP sales-movement history syncs for reporting on the Account. Created and updated, never deleted. | custom objects |
Destination objects
- accounts
- custom objects
- products
- price book entries
Phase 2 — Salesforce back to SYSPRO 7 and above
Setting up SYSPRO 7 and above and Salesforce 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 7 and above'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 Salesforce and declare SYSPRO 7 and above
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 Salesforce
# an OAuth CRM: the catalog’s callbackMode says which leg this one takes
$ dlake registration oauth --crm Salesforce
# 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 Salesforce
# the connection is incomplete without this call, however healthy the rest looks
$ dlake registration action --crm Salesforce --action SalesforceSetup
$ 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 7 and above 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
This page was generated from skill pages in the dlake CLI repository. The repository no longer publishes one of them; the site keeps the last published copy, without implementation-level table and field names, linked below. Whitelisted customers fetch the full operational skills from the admin plane with dlake admin get_skill.
SYSPRO 7 and above and Salesforce: common questions
Which way does data move between SYSPRO 7 and above and Salesforce?
One way. Phase 1 (CRMPro) pushes SYSPRO 7 and above records into Salesforce. The repository ships no TxDownloaderPro write-back for this pair, so there is no supported Phase 2 from Salesforce back to SYSPRO 7 and above.
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 Salesforce actually create?
The shipped catalogue carries 9 template groups for this pair: Account, Sal Area, Branch/Division Details, Salesorder, Invoice, Product, Pricebook, Customer Multi Ship Addresses and 1 more. Each group sets up its own sync process, and the integration page says what each one delivers.
Which Salesforce objects does the forward sync write?
accounts, custom objects, products, price book entries. Those are the kinds of Salesforce record the shipped templates write for a SYSPRO 7 and above source; nothing else is written unless you add templates of your own.
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.
Is there a write-back from Salesforce to SYSPRO 7 and above?
No. The repository ships no TxDownloaderPro page for Salesforce into SYSPRO 7 and above, so changes made in Salesforce are not carried back to SYSPRO 7 and above 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?
This page was generated from skill pages in the dlake CLI repository, which no longer publishes one of them. The site keeps the last published copy, without implementation-level table and field names, linked at the foot of the integration page. Whitelisted customers fetch the full operational skills from the admin plane with dlake admin get_skill.
Related
Every ERP and CRM integration · CRMPro (forward sync) · TxDownloaderPro (writeback sync) · AI agents & MCP · Salesforce integrations on commercient.com
