How do we stop re-keying CRM orders into the ERP?
Create ERP sales orders from won CRM deals automatically: map the fields, trigger on Closed won, store the ERP order ID to stop duplicates, alert on errors and test in a sandbox.
- Time needed
- 45 min
- Steps
- 5
- Level
- Intermediate
In short: Connect the CRM to the ERP so a won deal creates the sales order automatically. Trigger on one clear event (the deal reaching Closed won with required fields filled), map each deal field and line item to the ERP's sales order fields, store the ERP order ID back on the deal so the same deal can never create two orders, and alert a named person when something does not match. Test it in an ERP sandbox with real past deals before you switch it on.
Step 1: Map the fields
| CRM (deal) | ERP (sales order) | Notes |
|---|---|---|
| Company | Customer | Match on a stable ID, not the name |
| Deal line items: product, quantity, price | Order lines: item, quantity, rate | Product SKUs must match the ERP item list |
| Discount | Discount line or item rate | Agree one method with finance |
| Close date | Order date | Or the date the order is approved |
| Deal owner | Sales rep | Map users to ERP employees |
| Currency | Currency | Must exist in the ERP for that customer |
| Billing and shipping address | Bill-to and ship-to | Validate before sending |
| Deal ID | External ID or memo | Lets you trace both ways |
Write this table with finance before building anything. Most rekeying errors come from fields that mean different things in each system.
Step 2: Trigger on a stage, not on every edit
Start the sync when a deal reaches Closed won and a required checklist is complete: customer matched, SKUs valid, addresses present. Do not trigger on every deal update, or each small edit will try to create or change an order.
Step 3: Make it impossible to create duplicates
- Before creating an order, check whether the deal already has an ERP order ID.
- If it does, stop or update that order according to your rules.
- After creating the order, write the ERP order ID and a link back to the deal.
- Use the deal ID as an external ID in the ERP where the ERP supports it, so a retry finds the existing order.
Step 4: Handle errors where people will see them
| Problem | What the workflow does |
|---|---|
| Customer not found in the ERP | Creates a task for finance or creates the customer by rule |
| SKU not found | Stops, flags the deal, alerts the owner |
| ERP API error or timeout | Retries with backoff, then alerts |
| Price differs from the price list | Sends for approval before posting |
Post the reason on the deal so the sales rep can fix it without asking IT.
Step 5: Test in a sandbox, then roll out
- Run 20 to 30 past deals through the sync into an ERP sandbox and compare with the real orders finance keyed.
- Fix mapping differences.
- Go live for one team or region, with finance reviewing every synced order for the first weeks.
- Then widen it. Staging the first writes in a spreadsheet can help; see stage ERP syncs in a spreadsheet before the first write.
Connector or custom?
Native connectors and iPaaS tools work well when your fields and process match what they expect. Custom integrations make sense when you have custom objects, special pricing, approvals or several ERPs. Our integration architecture page explains the patterns we use. If orders then go to a warehouse, the 3PL EDI integration playbook covers the next hop.
FAQ
Can HubSpot create sales orders in NetSuite automatically?
Yes. With a connector or a custom integration, a won HubSpot deal can create a NetSuite sales order with its line items, as long as customers and items are matched first.
What should trigger the order?
A deal reaching Closed won with a completed checklist. Avoid triggering on every update.
How do we prevent duplicate orders?
Store the ERP order ID on the deal and check it before creating an order. Use the deal ID as an external ID in the ERP where possible.
Should changes in the ERP update the CRM?
Often status, invoice and shipment updates should flow back. Decide which system owns each field before you build.
How Octacer helps
Octacer builds CRM and ERP integrations for HubSpot, Salesforce, NetSuite, Odoo and Business Central. See our CRM and ERP integration solution, the order processing use case and NetSuite services.
Next step
Ask finance for three orders they keyed last week and compare them to the deals they came from. Every difference is a rule your sync needs. Then book a call.
Sources
- HubSpot Knowledge Base, Use deals: https://knowledge.hubspot.com/records/create-deals
Keep going
More guides
Want it running on your stack?
We implement this guide for clients, tailored to your stack, your data, and your team's workflow, and handed over documented.