What was built
A two-way sync between weclapp, the ERP Heckner runs its commercial operations in, and HubSpot, where sales happens. The hard part was never the connection; it was the mapping between two systems that model companies, contacts and products differently, in a business that cannot afford a record to exist twice.
| Area | Description |
|---|---|
| Field mapping | Full mapping and import configuration between the two data models, worked through in several rounds with the client |
| Company & contact sync | weclapp companies and contacts kept in step with HubSpot in both directions, including the HubSpot-side updates that were previously lost |
| Product write-back | Products on a won HubSpot deal written into weclapp as selectable dropdown values, closing the loop between the sale and fulfilment |
| Update logger | Every change made by the integration recorded, so an unattended sync stays traceable after the fact |
| Deployment & handover | Scenarios deployed to Heroku, then moved onto the client's own account with a written installation and deployment guide |
Record history was a known limitation: weclapp does not expose a change log the way HubSpot does, so the sync compares against the HubSpot deal first and writes only what actually differs.
Tech stack
| Technology | Role |
|---|---|
| HubSpot | CRM, deals, products |
| weclapp | ERP, system of record for commercial data |
| Make.com | The sync scenarios, hosted on Heroku |
Project stats: 26 tasks, ~180h over 6 months.