There are three routes: Softland plugins and web services, when your installation has them; an intermediate layer that reads the Softland ERP database in SQL Server and writes through mechanisms Softland supports; or a file exchange. Which one fits depends on whether Softland runs on your servers or in its cloud, which modules and plugins you have and which data you need to move. In Chile, review that profile with your Softland provider before committing to dates.
The route is chosen with your Softland installation profile, not on assumptions.
Softland presents its integrations as plugins. The e-commerce plugin uses web services on the Softland database to read, create and update clients, read the catalog with prices and stock by warehouse, and create sales notes. The electronic documents plugin receives a sale from another system, generates and signs the document, sends it to the SII and returns the PDF.
As of October 2026, the Softland Chile website does not publish open technical documentation for its API. So before designing, ask your Softland provider which plugins and services your installation has, in which version and at what cost.
Softland ERP runs on Microsoft SQL Server, and Softland itself teaches in its courses how to query it with SQL Server Management Studio and Power BI. If the installation is on your servers, your administrator grants access; if it is in Softland's cloud, you need to contract the database access service called Réplica.
Reading from views is a valid route to bring clients, products, invoices and balances into HubSpot. Writing directly to the tables is not: it skips the ERP's validations. To create clients or sales notes, use a plugin or a mechanism Softland supports.
The client is born in HubSpot and, when the deal is won, it is looked up by tax ID in Softland and created if it does not exist. Products, prices and stock travel from Softland so quotes use the same codes. The won deal creates the sales note, and invoices come back to HubSpot with number, amount and status.
If you invoice under several legal entities, define in which one each sale is created based on the HubSpot brand or line. And decide which number rules: what was invoiced lives in Softland; the pipeline, in HubSpot, and each one is reconciled against its own records.
Every Softland integration needs an owner with access to the code, the credentials and the documentation, and a test database or company to validate before every ERP version change.
In HubSpot, the Record Source property shows which records the integration created, and a daily report by source tells you whether they keep arriving. A silence alert warns if no invoice arrives on a business day. In Chile and Latin America, a scheduled read that stops running can go weeks without anyone noticing.
Six steps to choose the route before committing.
On your servers or in Softland's cloud, version, contracted modules and available plugins, and who your Softland provider is.
Which web services you have for clients, catalog, stock and sales notes, and which can be contracted. Ask for the technical documentation.
On your own installation, a read-only user; in the cloud, the Réplica service. Read from views and never write to tables.
Client by tax ID, product by code, won deal to sales note and invoice back. A table with the owner of each piece of data.
In a test database or company, with clients, products and sales from your operation, before touching production.
Code and credentials in your company's name, a document of what syncs and an alert if data stops arriving.
Promising an integration without knowing which plugins or version the installation has.
Writing directly to Softland tables and skipping its validations.
Finding out late that, in the cloud, database access requires a separate service.
A scheduled read that stops and nobody checks for weeks.
30 minutes with Roberto. No demo and no access to your CRM.
We review with your Softland provider which plugins, services and access your installation has, and classify each point as confirmed, conditional or unsupported before quoting. If we move forward, it is at a fixed price, and we hand over code, credentials and manual in your name, with the silence alert active.
ERP, invoicing, WhatsApp and APIs, with code and manual in your name and an alert if they stop bringing data.
See IntegrationsIn 10 hours we inventory integrations, workflows and properties, with the risk list.
See the DiagnosticThe alert is reviewed weekly in Managed HubSpot and daily in Dedicated HubSpot.
See operations plansThe guarantees that apply
An automatic alert tells you if an integration or form stops bringing in data. You hear it from us first.
Workflows, integrations, code and keys documented and in your name. If you change partners, you lose nothing.
We put them in writing because they are what we control.
It offers plugins with web services, such as the e-commerce plugin, which reads and creates clients, reads the catalog with stock and creates sales notes. Since its Chile website does not publish open technical documentation, confirm with your provider what your installation has.
To read, yes, from views and with a read-only user; in Softland's cloud you need the Réplica service. To write, use a plugin or a supported mechanism: writing to the tables skips the ERP's validations.
Softland, with its electronic documents module or plugin, before the SII. HubSpot receives the number, amount and status so sales and collections can see them on the deal.
Check before building, filtering by your Softland version. If none covers your objects, the route is a Softland plugin, an intermediate layer or a file exchange.
It depends on the route, the plugins you have and access to your installation; that is why it should be evaluated before quoting. Ask for a fixed price, code in your name and an alert if the integration stops bringing data.
Designs the CRM architecture, integrations and operation of each account. He writes these guides from what he sees every week in HubSpot portals of B2B companies across Chile and Latin America.
Meet the teamWe review one concrete problem, its impact and your starting point. No demo and no access to your CRM.
