Solution challenges
Solution challengeDelivered
ERP and HubSpot data architecture
Deciding what HubSpot owns, what the ERP owns, and how they stay consistent.
Project-level detail for this record is still being verified internally. Treat the summary below as capability and approach, not as a specific delivered claim.
- Forbidden's experience
- Forbidden treats this as an ownership question before an integration question: every object needs one system of record and one direction of truth.
- Architecture considerations
- System of record defined per object and per field, not per system
- Customer matching key that survives both systems
- Sync direction, frequency and conflict handling
- What belongs in HubSpot as a custom object versus a read-only view
- Error handling and reconciliation when a sync fails
- Common failure points
- Bi-directional sync on fields with no clear owner
- Recreating the entire ERP schema inside HubSpot
- No reconciliation process, so silent drift goes unnoticed
- Integration built before the commercial process is agreed
- Worth resolving in discovery
- Which fields does the commercial team actually need to see?
- What is the reliable matching key between systems?
- Who resolves a conflict when both systems change a record?
- What happens commercially if the sync is down for a day?