CRM + ERP Integration: Salesforce & HubSpot Guide

Why CRM and ERP data should be connected (but usually isn't)

Sales teams live in Salesforce or HubSpot. They track leads, manage pipeline, send proposals, and close deals there. Finance and operations live in NetSuite. They process sales orders, manage inventory, handle invoicing, and recognize revenue there.

Neither team sees what the other sees.

A sales rep doesn't know that their biggest account has three unpaid invoices totaling $87,000 and is 60 days past due. The finance team doesn't know that the same account just signed a $200,000 renewal in Salesforce last Tuesday. The customer success manager is working off a spreadsheet someone emailed last month.

The handoff problem is where it gets expensive. A rep closes a deal in CRM. Someone — usually an ops coordinator or the rep themselves — then manually creates a sales order in NetSuite. They re-type the customer name, line items, quantities, pricing, shipping address. Maybe they copy-paste from a PDF quote. Maybe they reference a Slack message from the rep. Errors compound. A single wrong SKU or pricing tier can cascade into fulfillment issues, billing disputes, and revenue recognition problems.

And revenue recognition is the core financial issue here. ASC 606 compliance starts when NetSuite records the transaction, not when Salesforce marks an opportunity as Closed Won. If there's a two-week lag between those events because someone is manually entering orders, your revenue reports are two weeks stale. For public companies or those preparing for audit, that gap is a material problem.

What data flows between CRM and ERP

Not everything should sync. One of the most common mistakes in CRM-ERP integration is syncing too much data and creating noise in both systems.

CRM to ERP is where revenue starts. Closed opportunities become sales orders. New accounts become customer records. Quotes become estimates. Product line items, pricing, discounts, and payment terms flow from the CRM deal into the NetSuite transaction. For companies with a configure-price-quote (CPQ) process, this flow also includes custom product configurations and approval chains.

ERP to CRM is where visibility lives. Invoice status, payment history, credit limits, and fulfillment tracking flow back to the CRM so sales reps can see the full customer picture. A rep calling on an account should know whether that customer's last three orders shipped on time, whether they have open credit memos, and whether they're on a payment plan. This data lives in NetSuite. Without integration, the rep calls blind.

Bidirectional sync covers contact information, addresses, and phone numbers. Both systems need current data, and customers update their information in unpredictable ways — sometimes through a sales call (CRM gets updated), sometimes through a billing inquiry (NetSuite gets updated). Bidirectional sync with conflict resolution rules prevents one system from overwriting the other with stale data.

The "source of truth" question comes up in every CRM-ERP integration project. Our guidance: CRM owns the relationship. ERP owns the transaction. Don't fight this. Salesforce or HubSpot should be authoritative for pipeline data, contact engagement history, and deal context. NetSuite should be authoritative for financial records, inventory, and fulfillment. When you try to make one system the master for everything, you end up with a brittle integration that breaks when either system's data model changes.

Salesforce + NetSuite integration

This is the most common CRM-ERP integration we implement. Salesforce dominates the enterprise CRM market, and most NetSuite customers at the mid-market level and above run Salesforce for their sales team.

Celigo offers a dedicated Salesforce-NetSuite integration pack with pre-built flows, field mapping templates, and documented deployment procedures. The pack covers the core use cases out of the box: Opportunity to Sales Order, Account to Customer, Contact sync, and Invoice status back to Salesforce. For standard implementations, this cuts deployment time from 8-12 weeks of custom work down to 3-5 weeks of configuration and testing.

Key data flows we configure in most Salesforce-NetSuite deployments:

• Opportunity → Sales Order. When an opportunity reaches Closed Won, Celigo creates a corresponding sales order in NetSuite with line items, pricing, and customer reference. Custom fields (deal source, sales region, contract terms) map through with additional configuration.
• Account → Customer. New Salesforce accounts create NetSuite customer records. Existing customers match on email or a shared external ID to prevent duplicates.
• Contact sync. Bidirectional. Changes in either system propagate to the other on a scheduled sync.
• Invoice status → Salesforce. Sales reps see payment status, aging, and credit information directly on the Salesforce account record.

There's also the Salesforce Connect option via OData, which gives Salesforce users read-only access to NetSuite data without a full middleware layer. It's lighter weight and cheaper, but limited — you can view NetSuite records in Salesforce, but you can't create or update NetSuite records from Salesforce. Good for reporting use cases, not for transactional workflows.

Gotchas we've encountered repeatedly: multi-currency handling differs significantly between Salesforce and NetSuite and requires explicit mapping rules. Custom object mapping adds complexity when either side has heavily customized their data model. And you should always maintain a sandbox sync environment for testing — CRM-ERP integration bugs don't just cause data problems, they affect revenue recognition and financial reporting.

For a detailed breakdown of this integration, see our Salesforce-NetSuite integration services pagearrow_forward.

HubSpot + NetSuite integration

HubSpot's move upmarket has made this integration increasingly common. Three years ago, most of our HubSpot-NetSuite work involved small companies outgrowing basic tools. Now we're implementing it for companies with $20M-$100M in revenue who chose HubSpot over Salesforce for its simpler UX and lower total cost of ownership.

Celigo has a HubSpot-NetSuite integration pack, though it's less mature than the Salesforce one. Fewer pre-built field mappings, fewer edge cases handled out of the box. That said, HubSpot's simpler data model (compared to Salesforce's highly extensible object structure) makes the underlying integration somewhat easier to build and maintain.

The core flows mirror the Salesforce integration:

• Deal → Sales Order. When a HubSpot deal moves to Closed Won, a sales order generates in NetSuite.
• Company → Customer. New HubSpot companies create NetSuite customer records with standard field mapping (name, address, payment terms).
• Contact sync. Bidirectional, with HubSpot as the relationship owner.
• Invoice and payment data → HubSpot. Custom properties on the HubSpot company record display NetSuite financial data.

HubSpot does offer a native NetSuite integration through its app marketplace. It handles basic record syncing but supports limited fields and has minimal error handling. For companies with straightforward needs — a small sales team closing 20-30 deals per month with simple product configurations — the native integration can work. For anything more complex, Celigo or a custom integration is necessary.

One HubSpot-specific advantage: the marketing automation side. Companies already using HubSpot for marketing and sales can trigger NetSuite workflows from marketing events — a webinar attendee who requests a quote can have that quote started in NetSuite based on HubSpot form data. This kind of cross-functional automation is harder to achieve with Salesforce unless you're also running Pardot or Marketing Cloud.

For more details, see our HubSpot-NetSuite integration services pagearrow_forward.

Other CRMs + NetSuite

Not every company runs Salesforce or HubSpot. Here's what we see with other CRM platforms.

Zoho CRM integrates with NetSuite via Celigo or custom middleware. Zoho has its own integration platform (Zoho Flow), which can handle basic data syncing, but it lacks the NetSuite-specific depth that Celigo provides. For companies already invested in the Zoho ecosystem (Zoho Books, Zoho Inventory, Zoho Desk), the decision often comes down to whether NetSuite is replacing Zoho's back-office tools or coexisting with them.

Microsoft Dynamics 365 integrations are typically built on Boomi or custom middleware. Dynamics has a more complex data model than most CRMs — its tight coupling with the Microsoft Power Platform, Dataverse, and Azure services means the integration architecture involves more moving parts. We see this most often in companies that standardized on Microsoft across the organization but chose NetSuite for financials.

NetSuite CRM (native) is the option people forget. If you're already running NetSuite, you have a CRM built in. No middleware required. Customer records, opportunities, quotes, sales orders — it's all in one system. The catch: NetSuite CRM is functional but limited compared to Salesforce or HubSpot for pure CRM use. Pipeline management is basic. Email tracking is minimal. There's no marketing automation. Reporting works but isn't intuitive.

When is NetSuite CRM enough? Small sales teams (under 10 reps), simple sales pipelines without complex stages or approvals, and companies that don't need marketing automation tied to their CRM. If your sales process is "get a lead, send a quote, close the deal," NetSuite CRM handles that without adding another system to your stack.

Integration architecture decisions

The technical decisions you make during the integration design phase determine how reliable, fast, and maintainable the system will be. These aren't decisions to defer to your integration vendor without understanding the tradeoffs.

Real-time vs. scheduled sync. Most companies think they need real-time sync. Most companies are wrong. A scheduled sync running every 5-15 minutes is sufficient for the vast majority of CRM-ERP workflows. A sales order doesn't need to appear in NetSuite within milliseconds of an opportunity closing — appearing within 10 minutes is fine. Real-time sync adds complexity (webhook management, retry logic, rate limiting) and cost. Reserve it for use cases that genuinely require it: payment processing, inventory reservation for high-velocity ecommerce, or customer-facing status pages.

Record matching. When a Salesforce account syncs to NetSuite, how does the system know whether to create a new customer or update an existing one? Email address is the most reliable cross-system identifier for customer records. It's unique (usually), it exists in both systems, and it doesn't change often. Company name matching is unreliable — "Acme Corp," "Acme Corporation," and "ACME" are the same company but won't match. Some implementations use a shared external ID field that both systems maintain, which is cleaner but requires initial data cleanup to populate.

Error handling. Integrations fail. Records don't map. Required fields are missing. API rate limits get hit. The question isn't whether errors will occur — it's what happens when they do. A good integration architecture queues failed records, alerts the responsible team, and provides enough context to resolve the issue without digging through logs. Celigo handles this well with its built-in error management dashboard. Custom integrations need this built from scratch, and it's often the piece that gets skipped during initial development and regretted six months later.

Testing. Always test in sandbox first. Both Salesforce and HubSpot offer sandbox environments, and NetSuite sandbox accounts mirror production configuration. Test with realistic data volumes — an integration that works with 10 test records can fail with 10,000 real ones due to API rate limits, timeout thresholds, or memory constraints. CRM-ERP integration bugs aren't cosmetic. They affect financial data, revenue recognition, and customer-facing processes. Treat integration testing with the same rigor you'd apply to a financial system upgrade.

---

See how a CRM-ERP integration plays out in practice.

Frequently Asked Questions

Frequently Asked Questions

How long does a CRM-NetSuite integration take to implement?expand_more

Should I use Celigo or build a custom integration for my CRM and NetSuite?expand_more

Can I sync custom fields between Salesforce and NetSuite?expand_more

What happens to historical data when I set up a CRM-ERP integration?expand_more

Do I still need a CRM if I use NetSuite CRM?expand_more