CRM for manufacturing: decide what your ERP owns first

A buyer calls your outside rep and asks when the order ships. The rep opens the CRM and finds the account, the contacts and six months of call notes, but no ship date. The ship date lives in the ERP, along with the price, the open orders and the fact that the account is on credit hold. The rep calls the plant. The CRM looks useless, and the rep stops logging calls in it.

Many CRM for manufacturing projects stall this way, and the outcome is decided before anyone picks software. The ERP owns orders, pricing, inventory, ship dates and invoices. The CRM owns people, opportunities, quotes in progress and the activity around them. Write that split down first, then sync only the handful of ERP fields your salespeople actually use, read only, into the CRM. Everything else in this guide follows from that decision.

What should a CRM do that the ERP does not?

An ERP is built around transactions: a part number, a price, an order, a work order, a shipment, an invoice. It is very good at what happened and weak at what might happen. Most ERPs have a customer record with a bill-to and ship-to address and maybe one contact. They rarely know that the account has a new buyer, a quality engineer who blocks every PPAP, and a plant manager in another state who is looking for a second source.

A CRM is built around people and the work before the order. In a manufacturer, that means:

Every contact at an account and their role in buying (buyer, engineer, quality, maintenance, owner)
Opportunities: the RFQ, the new program, the replacement cycle, the project in design
Quotes in progress, with revision history and the date the customer needs an answer
Activity: calls, emails, visits, samples sent, trade show conversations
Marketing history: which pages someone read, which webinar they attended, what they downloaded

If your ERP already does some of this well, let it. If it has an estimating module, an estimate built on routings and material costs belongs where the routings live. The CRM’s job is to know the estimate exists, what it is worth, who asked for it and when it is due.

How should a CRM and ERP connect?

For every object, one system is the record and the other system reads it. When two systems can both edit the same field, you get two answers and a monthly argument about which is right.

For a checkable public example of how an ERP and a CRM split the work, Microsoft documents the standard table mapping between its Business Central ERP and its Dynamics 365 Sales CRM. We use it here only because the mapping is public; it is not a product recommendation. In the integration documentation (last updated April 8, 2026):

Sales prices and customer price groups flow from the ERP to the CRM only. The CRM displays prices; it does not set them.
Posted invoices flow from the ERP to the CRM only.
A sales order created in the CRM is synchronized once a salesperson sets its status to Submitted. At that point, in Microsoft’s words, “you can no longer change information on the order’s lines,” and it arrives in the ERP as Released.
Item availability updates the CRM through a scheduled job that runs every 30 minutes.
Customer statistics from the ERP appear in the CRM as a read-only “Business Central Account Statistics” view on the account.

Accounts and contacts, by contrast, sync in both directions in Microsoft’s standard mapping. Accounts are where a manufacturer needs a rule of its own, because a CRM will happily create a prospect account that the ERP should not see until it orders.

Any pairing of ERP and CRM can follow the same split. Prices, orders, invoices and inventory are written in the ERP and displayed in the CRM. The CRM hands the ERP a finished order or a new customer request and then lets go.

The field-ownership map, by sales motion

This is our map. It is a starting point for the meeting where sales, operations and finance agree who owns what. The first rows are the same for every manufacturer. The quote row is where your sales motion changes the answer.

Data	System of record	Shown in the other system?
Customer master (legal name, bill-to, ship-to, terms, tax, credit limit)	ERP	Yes, read only in CRM
Prospects and accounts that have never ordered	CRM	No, until the first order
Contacts and their buying roles	CRM	Optional; most ERPs need only the AP and purchasing contact
Opportunities and pipeline	CRM	No
Price lists, customer-specific pricing, discounts	ERP	Yes, read only in CRM
Orders, promise dates, shipments, invoices	ERP	Summary only in CRM
Inventory and lead times	ERP	Only if reps quote availability
Calls, emails, visits, samples, marketing activity	CRM	No

Build to print

The estimate (routings, material, outside processing, setup) belongs in the ERP or the estimating tool attached to it. The CRM holds the quote header: customer, part numbers, total value, due date, status, win or loss reason and the drawing package. Revisions are common, so the CRM needs a revision number on the quote and a link to the estimate. Our RFQ-to-quote playbook for job shops covers the quoting work itself.

Engineered to order

Opportunities run for months and the quote changes as the design changes. The opportunity and its revision log belong in the CRM, with the configuration or engineering estimate in whatever system engineering uses. Add fields for decision date, competing bidders and the buying committee. The ERP does not need to know about it until the order.

Proprietary products

Quotes are usually price list plus discount, so they can live in the CRM as long as prices come read only from the ERP. The most important CRM object here is often the reorder: who bought last year and has not bought this year.

Spec-driven

Much of the selling happens before a buyer exists. The CRM needs a project object (project name, location, architect or engineer of record, spec status, bid date, the contractor who wins it) and a way to link many companies to one project. Quotes go to contractors late in the cycle, and the ERP sees only the eventual order.

Which ERP fields should sync to the CRM?

A common first-year mistake is syncing the whole item master and the full order history, then spending months cleaning up duplicates. In year one, sync these five, read only, on the account record:

The ERP customer number. It is the key that ties the two records together. Without it, every other sync breaks.
Sales this year and last year to date. One pair of numbers tells a rep whether the account is growing or slipping.
Open orders with promise dates. This answers the call that opened this article.
Last order date, the simplest early warning for a lost customer.
Credit status. A rep who knows an account is on hold avoids an awkward conversation.

Going the other way, the CRM sends the ERP two things: a won quote ready to become an order, and a request to create a new customer. Finance approves both.

What to skip in year one

We would leave these out of a first-year CRM project at a 50 to 500 person manufacturer, even if the vendor demo makes them look easy:

Two-way order editing. Orders are changed in the ERP. If sales needs to change one, they ask customer service.
A full item master sync. A job shop with 40,000 part numbers does not need them in the CRM. Sync product families or your top sellers.
Configure-price-quote software. It can be worth it for complex configured products later, once you know your quote volume and win rates.
Lead scoring. Score leads after you have a year of data on which leads became customers.
Custom objects for everything. Start with accounts, contacts, opportunities, quotes and, for spec-driven sellers, projects.

The goal in year one is that every rep logs every opportunity and every quote, and that the five ERP fields are always right. Those two habits alone give you a pipeline report and a quote win rate you can trust. If the CRM lands on your desk in a new job, our plan for your first 90 days as a marketing leader shows where it fits.

What should a CRM for manufacturing have? A requirements checklist

Take this to any vendor demo and ask to see each item on screen.

Parent and child accounts, so a corporate parent and its plants roll up
Multiple contacts per account with a role field you define
Opportunity stages you can rename to match your RFQ or project process
A quote record with revision number, due date, value, status and loss reason
File attachments on quotes (drawings, specs, STEP files) or links to where they live
Email and calendar logging that works without the rep doing anything extra
A mobile app that outside reps will actually use in a parking lot
Access for independent reps or distributors, limited to their accounts
A native or well-documented connector to your ERP, with a field-level mapping you can read before you sign
Reports on pipeline by stage, quote win rate by customer and by salesperson, and accounts with no activity in 90 days
An import tool for your existing spreadsheets and contact lists
Total cost for your user count over three years, including the integration

If a vendor cannot show you the ERP field mapping before you buy, assume the integration is a custom project and budget for it.

In your industry

Metals and Machining

Build to print dominates. Quote volume is high and quotes are small, so the quote record and win rate by customer matter more than pipeline forecasting. Make the RFQ intake form create the CRM quote automatically if you can.

Plastics and Rubber

Molders often quote tooling and piece price separately. Track them as two lines on the quote, because the tool is a one-time decision and the piece price is the annuity.

Industrial Machinery and Equipment

Long cycles and buying committees make the opportunity record, contact roles and decision dates the core of the system. The installed base is your next pipeline, so record which customers own which machines and when they shipped. Our piece on aftermarket parts and service covers how to sell to it.

Automation and Industrial Tech

Integrators and channel partners influence many deals. Give partners limited access, or at least a field for the integrator on every opportunity. If you sell through distributors as well, our guide to CRM for distributors shows what their inside, outside and counter teams track.

Building Products

The project object is the system. Track the architect, the spec status and the bid date, and accept that the order may come through a distributor you never quoted.

What to do Monday

Book one hour with whoever runs sales, customer service and finance. Put the ownership table above on the screen and fill in the right-hand column for your company. Then pick the five ERP fields, write down who approves new customers, and decide whether quotes live in the ERP, the CRM or both with a link. Take that page to every CRM demo. The vendors who can work with it are the ones worth a second meeting.