The ERP customer master anchors the match, so distributors, direct accounts, quotes and serialized equipment land in Salesforce under the right account.
Manufacturing migrations usually combine an older CRM or contact database, quote history from spreadsheets or a configuration tool, distributor and rep lists, and service records tied to serial numbers. We use the ERP customer master as the anchor for matching, load sold-to and ship-to relationships in the structure sales actually works with, and bring over open opportunities, recent quotes and installed products. Channel partners, independent reps and direct accounts each get clear ownership rules. Where a manual process is being retired, we clean part numbers and account names before loading so reports do not inherit old inconsistencies.
Manufacturers usually have more than one kind of customer in the same data: end users, OEMs, distributors and independent reps, all with different roles in a sale. ERP account structures are designed for billing and shipping, with many ship-to records per customer, and they rarely match how the sales team thinks about accounts. Product data is another difference. Quotes and installed equipment reference part numbers, revisions and configurations that may have changed or been retired since the record was created. Service history is tied to serial numbers rather than to people. A migration that moves only contacts and accounts misses the product and channel detail the business depends on.
Sold-to, bill-to and ship-to records from the ERP are consolidated into Salesforce accounts that match how sales manages relationships. The ERP number is stored as an external ID on every account so later integrations, reorders and service calls can find the right record without another round of matching. Ship-to locations that sales never works directly are kept as addresses rather than separate accounts.
Distributor branches, independent rep agencies and their territories are loaded as partner accounts with contacts and coverage assignments. Customer accounts are linked to the distributor and rep that serve them, which keeps commission reporting and lead routing accurate once opportunities start flowing through Salesforce. Terminated rep agreements are recorded with end dates so historical credit stays explainable to finance and sales leaders.
Open and recent quotes from spreadsheets or a legacy configuration tool are mapped to opportunities and quote records, with part numbers checked against the current catalog. Retired or superseded parts are flagged rather than silently dropped, so sales can still see what a customer bought or requested before the product line changed and can offer the right replacement part or successor model.
Equipment sold to customers is loaded as assets with serial number, model, install date and site. Warranty and service history attach to the asset, giving service and aftermarket sales teams a clear record of what each customer owns and what might need parts, upgrades or replacement. Equipment resold or moved between sites is reassigned to its current location during cleanup.
We start with sales operations, customer service and the ERP owner, because account structure decisions affect all three. A mapping of ERP account types to Salesforce accounts and relationships is agreed before any extract. Products and price data load first, followed by accounts, partners, assets and then opportunities and quotes. Each stage is reconciled against ERP reports by region and customer type. Sales managers review their territories in a sandbox. Cutover is aligned with a fiscal period end, and the legacy CRM or spreadsheets are made read-only on the day Salesforce goes live.
Customer numbers, ship-to addresses and order summaries anchor the migration, then become the basis for an ongoing sync so account and order data do not drift apart again.
Part numbers, revisions and configurations are validated against current records, so migrated quotes and assets reference products that sales and service teams can identify.
Point-of-sale and inventory reports from distributors are matched to partner and end customer accounts, giving the channel team history alongside the new opportunity data.
Copying every ship-to as a separate account produces a cluttered database that salespeople avoid. Decide which ERP records become accounts, which become addresses and which stay out, and test that decision with one sales team before loading everything. Reversing it after go-live is far more disruptive.
Quotes referencing retired or mistyped part numbers break reports and pricing rules. Resolve the product catalog first, map legacy part numbers to current ones where possible, and hold back records whose products cannot be identified until someone in product management or sales operations confirms them.
When distributors, reps and direct sales all touch a customer, ownership disputes surface after migration. Define who owns the account, who sees opportunities and how credit is assigned before loading, and reflect those rules in sharing and partner access so each group sees what it should.
Client names are anonymized.
Going beyond migration for manufacturing, the playbook covers which Salesforce products fit manufacturing, how to implement, migrate and integrate them, the regulation to plan for, what to measure, and a 14-point readiness checklist.
Selectively. Scanned documents can be attached to accounts or assets when they have lasting value, such as warranty registrations or signed agreements. Structured data from paper forms usually needs manual entry or extraction and review, so we focus that effort on active customers and installed equipment rather than digitizing every historical record in the filing cabinet.
We model the end customer as one account, then link the distributor or rep relationship and record the channel on each opportunity or order. That shows the complete relationship without double counting revenue. The ownership and visibility rules agreed with sales leadership decide who sees and works each opportunity, and partner users see only their own deals.
Open quotes and recent history that influence current deals should move. Older quotes with outdated products and pricing can stay in an archive. If Revenue Cloud or CPQ is part of the project, migrated quotes are loaded in a way that does not trigger new pricing calculations or approval requests, so historical prices stay exactly as they were quoted.
Warranty claims, service cases, field visits and parts replacements tied to serial numbers are usually worth moving, especially for equipment still in use. That history helps service agents troubleshoot and helps sales spot upgrade opportunities. Records for scrapped or long-retired equipment can be summarized at the account level instead of loaded record by record into the new org.
Last reviewed September 27, 2026.
Valuable insights on technology, CRM and AI, once a month.
Written by the consultants who do the work. One email a month, and you can unsubscribe anytime.
