Map the information
We identify systems, records, ownership, timing and the decisions the connection must support.
We connect HubSpot to the tools your business depends on and build custom integrations when a suitable connection doesn’t already exist.
Quick answer
A HubSpot integration moves agreed information between HubSpot and another system. Project36 defines record ownership, field mappings, sync direction, timing and failure handling before choosing a native connection, integration platform or custom API. We test representative records and document who maintains the connection.
Key takeaway: Migration moves existing data. An integration keeps systems connected afterwards; you may need one, both or neither.
| Your situation | A useful next step | What to keep in mind |
|---|---|---|
| An existing connector appears to cover the records and sync rules you need | Plan the integration requirements | Check supported fields, conflict handling, permissions and ongoing costs in your actual accounts before choosing it. |
| Your required process isn't covered by a supported connection | Assess a custom HubSpot integration | Feasibility depends on both systems' APIs and access. Custom connections also need monitoring and maintenance. |
| You're replacing a system and need its existing records in HubSpot | Plan a CRM data migration | Agree record matching, cleanup and validation; a one-time import isn't an ongoing synchronisation service. |
Disconnected systems create copying, checking, delay and disagreement about which information is right. The answer isn’t always to move everything into one platform.
We define what needs to move, when it should move, which system owns it and how failures should be handled. Then we select, configure or build the right connection.
Every one of these platforms works seamlessly with HubSpot. Together they can form your entire tech stack, and we can help you with all of it: choosing the right tools, connecting them and making them work together.
Less duplicate data entry
Reliable information across teams
Clear ownership of each data point
Visible error handling
Integrations designed to be maintained
We identify systems, records, ownership, timing and the decisions the connection must support.
We compare native connections, integration platforms and custom API development.
We implement mappings, rules, monitoring and tests using representative data.
Your team gets clear ownership, support information and a route for future change.
Project36 designed and maintained a reliable bidirectional connection for Modulr Finance as the business grew.
Read the client storyCRM and revenue operations
Official definitions of a 'small business' are changing. For a founder, this is a prompt to ask: is the HubSpot that got us here ready for where we go next?
ReadCRM and revenue operations
HubSpot has confirmed it won't proceed with the 1 July 2026 terms changes on data enrichment, contact discovery and AI. Customer CRM data stays under customer control, and any future enrichment features will be opt-in. Here's what I'd do with the breathing room.
ReadCRM and revenue operations
A recent Google warning highlights a major risk for SMEs. Your HubSpot permissions could be leaving the door wide open for data theft. Here's how to fix it.
ReadWhere the available APIs and platform capabilities allow it, yes. We assess feasibility before agreeing delivery.
Not necessarily. We’ll recommend a simpler supported connection when it meets the requirement.
We help you choose the right setup, organise your data and build HubSpot around how your business actually works.
Find out moreWe find the friction, underused capability and avoidable admin holding your team back, then turn the best opportunities into practical improvements.
Find out moreWe help you put Breeze to work on specific jobs, with a clear purpose, controlled usage and a way to judge the result.
Find out moreTell us about the time-consuming task, disconnected system or idea you haven’t quite worked out yet.
A reliable integration needs clear record ownership, mappings, sync rules and monitoring. Start with the business process before choosing a connector or custom API.