No. This is a build-to-order per-tenant AL extension. ECOSIRE builds it to your data model and HubSpot portal, then installs it directly on your Business Central tenant. There is no instant AppSource listing to download — you get a connector fitted to your fields, tax setup and numbering instead of a generic app.

A typical build is one working week from kickoff. After a short scoping call to confirm your objects, custom fields and conflict rules, we develop in a sandbox, run an end-to-end sync test you can review, then schedule production install and go-live. Complex custom-field or multi-entity setups can extend the timeline; we confirm a date during scoping.

Every build includes a post-go-live support window for bug fixes and for keeping the extension compatible with Business Central monthly updates and HubSpot API changes. We maintain the .app, re-test after major BC releases, and can extend support or add mappings under a maintenance arrangement. You are never left holding unmaintained custom code.

No. It installs as a separate per-tenant extension with its own object range, permission set and Isolated Storage. It coexists with other extensions and with the standard Dataverse/Dynamics 365 Sales integration — useful if you run HubSpot for marketing/sales while keeping Dataverse for other workloads.

Each object has a configurable per-field policy: last-write-wins by timestamp, a fixed source-of-truth per field, or hold-for-review where the change is flagged in the audit log instead of applied automatically. This prevents either system from silently overwriting the other and is set during configuration.

Contacts and companies sync both ways; HubSpot deals convert into BC Sales Orders; BC Items sync out to HubSpot products; and posted Sales Invoices plus applied payments write back to the HubSpot timeline. Direction and trigger stage are configured per object, and custom-property mappings are added in code so your specific schema is respected.