The external system
Not us
A file, a table, a call. That ERP’s name is not in the code. Nesso is not that system.
Recipes
The recipe proposes the sheet and the columns. Whoever installs rereads the mapping before turning the run on.
Espo on one side
The price list does not invent Product.
Accounts, contacts, sites, and the price list are four starting points. Each names a sheet and some columns. They do not write on their own and they do not certify that the system on the other side has a particular name: that name is not in the code.
Propose the mapping uses synonyms, in the language of the page, and does not save until a person confirms. An unrecognized column stays empty.
They are not a certified connector. They do not replace the ERP. They do not create Espo users. They do not turn write-back on.
The price list points at Product. If this installation does not have the sheet, the fields stay empty. The recipe does not invent the catalog.
Look at the preview. Decide the owner of the fields a person corrects by hand. Leave write-back off until the return columns are named.
The switch-on plan is this: connection, sheet, mapping reread, run. The handover page does not contain passwords.
The passage
Nesso stands in the middle. It reads the channel, applies the mapping, and writes through Espo’s API. It does not open the CRM tables.
Not us
A file, a table, a call. That ERP’s name is not in the code. Nesso is not that system.
This is us
Channel, sheet, fields. If the write switch is off, it does not write. If the field belongs to Espo, it does not clear it.
The sheet
The record, if it is born, is born there. CRM mail stays in Espo. The Advanced Pack is not rewritten.
Nesso always has Espo on one side. It is not a bridge between any two systems.
The trial is the public repository. It starts an empty Espo. It does not import a production dump.
How the trial works