What they have bought
Order history at the account, so a rep never asks a twenty-year customer what they buy. A nightly one-way load of sales orders linked to the company record does this.
We sell outcomes. Not hours.
The instinct is to put the ERP inside HubSpot so sales can see everything. It is expensive, it takes months, and it produces a second copy of your data that drifts within a quarter. A rep preparing for a call needs to answer three questions: has this company bought from us, what do they owe, and can we make what they are asking for on time. Those three fields go into HubSpot. Everything else stays in the ERP and gets opened when the detail matters.
Each one is a single value on the company or contact, refreshed overnight. None of them needs a live two-way sync.
Order history at the account, so a rep never asks a twenty-year customer what they buy. A nightly one-way load of sales orders linked to the company record does this.
Open balance and terms, visible before the next quote goes out. One number and one date.
Capacity and lead time for the item they are asking about. Often a link into the ERP screen rather than a copied field, because the answer changes by the hour and a stale copy is worse than none.
Line items, bills of material, inventory positions, invoices. Looked up in the ERP when needed, never copied into the CRM. The full argument: They Need Three Fields →
Where HubSpot has a connector for your ERP, it maps standard objects and fields and keeps them in step. That covers the three-fields pattern for most companies, and it is the $2.5k end of our pricing. It stops at five places, and each one is where the $10k build begins.
The price follows the connector and the logic, not the logo.
Standard mapping covers the three fields. The work is in what the sync leaves out: lookup fields, history and clean-up.
$2.5knativeNative for the simple field set. Where Dynamics is also the CRM you are leaving, that is a migration first: leaving Dynamics CRM →
$2.5knativeERPs without a HubSpot connector. Middleware with transformation logic, sized to the field set and the direction.
$10kcustomThe platform holds the quote, HubSpot holds the deal. We built a real-time Paperless Parts integration for Uptive after batch sync left quote data 24 to 48 hours behind.
$10kcustomManufacturing is where this pattern comes up most, because the quote is the unit of work. More on the manufacturing page.
Salesforce and Paperless Parts pushed data once a night, so quote data arrived a day or two late and often incomplete, which broke reporting and territory assignment. We migrated Uptive to HubSpot and built a custom Paperless Parts integration with real-time sync.
Sales and marketing moved from Dynamics CRM to HubSpot. The parent company's Dynamics kept project IDs and resource planning, with the ID written back onto the HubSpot deal so nobody re-keys it.
Two prices, published here, on our pricing page and inside the migration calculator. Same figures in all three places. If a real project lands outside them, we fix the model, not the invoice.
HubSpot's connector to your ERP, standard mapping, one way. The three fields and whatever else the connector carries cleanly.
Middleware or a custom build where the connector does not exist, the mapping needs transformation, or the integration has to hold business logic. Two-way sync, historical loads and quoting-platform work land here.
What moves it from one figure to the other: direction and data quality. A one-way nightly load of clean data is the first price. Anything you would describe with the word "reconcile" is the second. Inside a migration, the integration is one component on top of the migration fee.
Three answers we give before we quote anything.
Almost never. Sales needs three things from the ERP: what the customer has bought, what they owe, and whether it can be made on time. The rest stays where it is and gets looked up when the detail matters.
Yes. It maps standard objects and fields one way or two way. It does not write transformation logic, translate lookup fields or clean the source data, which is where most of the work in a NetSuite integration sits.
$2.5k on a native connector with standard mapping. $10k for a custom integration where the connector does not exist, the mapping needs transformation, or the integration carries business logic such as quoting rules.
One-way from the ERP into HubSpot covers the three fields and is the reliable shape. Two-way is for closed-won deals and accepted quotes going back into the ERP as orders, and it roughly doubles the testing.
A native-connector integration is measured in weeks. A custom build depends on the field set, the direction and the state of the source data; we scope it in discovery and price it as a fixed figure.
Tell us which ERP and which three questions your reps need answered. If a nightly export does it, we will say so before we quote a line.
+972-54-819-1655
info@penguinstrategies.com
4 Dolev Street, Ra'anana, Israel
