New: Odoo and Dynamics 365 cost calculators.Estimate your costs

Is Salesforce an ERP or a CRM? And which do you need first

Salesforce is a CRM, not an ERP. On its own product page, Salesforce calls itself a cloud-based customer relationship management (CRM) and agentic AI platform used for customer data…

FlecticUpdated 20 min read

Salesforce is a CRM, not an ERP. On its own product page, Salesforce calls itself a cloud-based customer relationship management (CRM) and agentic AI platform used for customer data, sales, marketing, and customer service. An ERP is the system for the ledger, purchasing, inventory, and production: Microsoft and SAP both define it that way. If your team already sells in Salesforce and retypes the order into the accounting file, the decision is which system owns money and stock, and which you build first. The platform-neutral split is in our guide to the ERP vs CRM difference and overlap. This page stays on the Salesforce-specific choice.

What Salesforce says it is

Salesforce's about page titles the company the #1 AI CRM. The IDC footnote on that page, from the Worldwide Semiannual Software Tracker in October 2025, limits the claim to sales force productivity and management, marketing campaign management, customer service, contact center, advertising, and digital commerce. Those are front-office categories. The same page does not describe a general ledger, a purchasing system, or a stock ledger as the product.

Salesforce's own CRM explainer defines CRM as technology for managing relationships and interactions with customers and potential customers, traditionally across marketing, sales, ecommerce, and customer service. On that page, a CRM can connect to other business apps, including accounting and billing. Accounting and billing are described as connected apps, not as the CRM itself.

Wikipedia's company profile says Salesforce is best known for CRM software. Named services include Sales Cloud, Service Cloud, Marketing Cloud, Commerce Cloud, Platform, Slack, and AppExchange. Fiscal year 2026 revenue, for the year ended 31 January 2026, is given as US$41.5 billion. Scale explains why people search "salesforce erp." It does not change the product Salesforce describes.

People who have had to draw the line in public use the short form. One comment puts it as "Salesforce is a crm not an erp". Another says "Salesforce is CRM, customer relationship management, and not an ERP.". Treat those comments as shorthand. The product pages above are the documentation.

IBM's November 2025 comparison uses the same split and names Salesforce as a CRM example. It names SAP S/4HANA and Oracle ERP Cloud as enterprise ERP examples. IBM is describing categories, not telling a 40-person distributor which license to buy. That choice comes later, from what your team retypes.

What an ERP owns when a CRM is already in place

Microsoft's ERP page, dated 8/12/26 on the page, calls an ERP business management software that integrates finance, supply chain, manufacturing, human resources, procurement, and project management, using one shared record instead of disconnected tools. The FAQ on that page states the difference in one pass: ERP focuses on operational and financial processes, and CRM focuses on customer relationships, sales, marketing, and service. Many organizations connect the two so customer, order, inventory, billing, and service data work together.

Microsoft lists the finance uses as accounts payable and receivable, the general ledger, forecasting, audits, and financial reports, and the procurement uses as vendor management, purchasing workflows, and spend analysis. SAP's definition covers finance, HR, manufacturing, supply chain, sales, and procurement, and it says finance uses the system to close the books, procurement uses it to source goods, and accounts payable uses it to pay suppliers.

For a firm that already runs Salesforce, the practical owner list is shorter than a vendor brochure:

  • Who the buyer is (Stays with the CRM: Accounts, contacts, pipeline, service cases · Belongs in the ERP: Customer record used for billing and credit)
  • What you sell (Stays with the CRM: Product and price lists used on quotes · Belongs in the ERP: Item, cost, and inventory valuation)
  • The commercial document (Stays with the CRM: Quote, and often the order the rep sends · Belongs in the ERP: Sales order that reserves stock and becomes an invoice)
  • Money (Stays with the CRM: Forecast and the deal value on the opportunity · Belongs in the ERP: Accounts receivable, accounts payable, cash application, general ledger)
  • Supply (Stays with the CRM: A note that the customer asked for a date · Belongs in the ERP: Purchase orders, receipts, warehouse quantity)
  • Making or delivering the work (Stays with the CRM: The case or the renewal · Belongs in the ERP: Manufacturing, projects, or service consumption posted to cost)

Read the table as ownership, not as a feature claim about every Salesforce edition. Your CRM can hold a price. The ERP is where that price becomes cost of goods, a payable, and a closed period. IBM describes the same front office and back office: CRM for sales, service, and marketing; ERP for finance, supply chain, project management, and HR.

Dynamics 365 Business Central is sold as one system for finance, sales, service, and operations. Essentials is described as business management for finance, sales, and operations; Premium adds service management and manufacturing. That is the shape of an ERP a 20 to 100 person firm usually compares when Salesforce is already the CRM. A heavier finance product sits beside it: Dynamics 365 Finance is listed at USD 210 per user per month, and Finance Premium at USD 300, both paid yearly, as of October 2026. Microsoft says displayed prices may differ at checkout by currency, country, and region. If Finance is in scope for a Canadian company, have the Canada checkout shown before you put a number in the budget. The Canada figures in the license section below are Business Central.

Who should own the customer, the order, and the ledger

Pick one owner per record before anyone talks about middleware. Firms this size get into trouble when two systems both edit the customer and neither posts the ledger.

The CRM owns the relationship. Salesforce keeps the account, the contacts, the opportunity stages, and the service case. Reps live there. Marketing and service live there. You do not move pipeline hygiene into the accounting system to avoid an integration.

The ERP owns anything that hits a financial statement or a quantity on hand. Chart of accounts, vendor bills, customer invoices, inventory valuation, purchase orders, and manufacturing or project cost sit there. When finance is reconciling two sets of numbers, build that system first. Leave Salesforce as the CRM. Do not spend the project teaching the CRM to imitate a ledger.

Shared records need a direction, not two editors. Customer, product, price, quote, order, and invoice are the usual collisions. IBM lists the overlap as contact and account data, customer orders, and transaction history on the CRM side, and financials, inventory, and order management on the ERP side. Duplicate customers, products, prices, and orders show up when those records are typed in both places.

A CRM can hold commercial documents that the ERP will also post. Dynamics 365 Sales Professional's published notes include leads, opportunities, accounts, contacts, product and price lists, bundles, quotes, orders, and invoices. That is useful context if you ever compare a Salesforce-plus-ERP stack with a Microsoft stack. It is also the reason a quote in one system and an invoice in another drift. The document can exist twice. The ledger should exist once.

Where the same order gets typed twice

The costly overlap is a quote that becomes an order only after someone rekeys it, then an invoice that accounting types again, then a warehouse that never saw the original request. A duplicate contact is the small version of the same gap.

IBM's description of a connected pair is the standard you can hold a bidder to. A sales order created in the CRM triggers inventory checks, production planning, and invoicing in the ERP, and that removes a second round of data entry. Until that path exists, the day looks like this:

  1. A rep marks the opportunity won in Salesforce and sends a quote from the CRM, a spreadsheet, or email.
  2. Someone creates the customer again in the accounting file, because the billing name, tax, and terms were never the CRM's job.
  3. The order is typed a second time so stock can be promised. If the warehouse cannot see Salesforce, the promise waits on a message.
  4. The invoice is typed a third time, or exported and repaired, so accounts receivable and the general ledger can close.
  5. Month-end is a matching exercise: CRM revenue, accounting revenue, and the quantity the warehouse shipped.

Two 2025 promotional posts for another product use the same language. One post says "manually copying data between systems", describes a stack where "nothing talked to each other", and cites books that split: "QuickBooks and our inventory system showed different numbers". A separate promotional post says "No more \"I'll email the warehouse\" delays.". The remedy is an owner for each record and a direction for the order, which is what a CRM and ERP integration has to specify.

For a distributor or a light manufacturer, the records to map first are customer, item, price, sales order, shipment, and invoice. For a project firm, map project and time in place of shipment. Write the direction in a sentence a new hire can follow: Salesforce creates the account and the opportunity; the ERP creates the customer, the order, the invoice, and the inventory movement; price changes start in one system and are sent to the other on a schedule you can name.

Which system to build first

Three situations cover most 20 to 100 person firms that already pay for Salesforce.

Pipeline and service are the pain. Reps miss follow-up, cases sit in inboxes, and the accounting file is dull but consistent. Stay on the CRM. Add process and, if the edition is wrong, a Salesforce license change. An ERP will not fix a stage definition nobody uses. Our CRM implementation work is the path when the front office is the gap and the books are already trusted.

Quotes and orders are typed again into the accounting file. Add an ERP and integrate it. Salesforce remains the place reps live. The new system takes the ledger, inventory valuation, and purchasing. This is the common case for a distributor, a wholesaler, or a company that has outgrown QuickBooks while Salesforce still fits the sales team.

Finance is reconciling two sets of numbers. Build the system for money and stock first. A prettier pipeline on top of two revenue totals will not survive an audit question or a stock count. Connect Salesforce after the ERP can post an invoice and show a quantity. Our ERP implementation for companies that already run a CRM is scoped that way: the back office goes live in a defined phase, and the CRM stays.

A single-vendor suite is the other branch, and it is a replacement of the CRM as well as the books. Odoo is the suite in this size range that prices both on one fee: its Standard and Custom plans include Sales, CRM, Accounting, Inventory, and Purchase for one per-user fee, and Accounting links to Sales for invoices, Purchase for bills, and Inventory for valuation, per Odoo's pricing page. Choose that only if you are willing to move the pipeline, not if the sales team has years of Salesforce history you intend to keep.

What the licenses cost beside Salesforce as of October 2026

License cost and project cost are different bills. The figures below are published list prices as of October 2026. They are not an implementation quote. Ask each bidder to price data migration, the Salesforce connection, and training as their own lines.

Salesforce Sales list prices, from the US Sales pricing page, which says pricing is informational and subject to change:

  • Free Suite: 0
  • Starter Suite: 25
  • Pro Suite: 100
  • Sales Core: 195
  • Sales Advanced: 395
  • Sales Max: 550

The Sales pricing page lists USD, AUD, GBP, EUR, JPY, and SEK. CAD is absent from that list. The page also does not state whether the figure assumes an annual commitment. Compare Canadian ERP prices with Microsoft's Canada page, and ask Salesforce for a CAD quote before you convert the US list.

Business Central, paid yearly, as of October 2026. Microsoft warns that displayed prices may differ at checkout by currency, country, and region.

  • Business Central Essentials (United States: USD 80.00 per user per month · Canada: CAD 108.50 per user per month, plus applicable tax)
  • Business Central Premium (United States: USD 110.00 per user per month · Canada: CAD 149.20 per user per month, plus applicable tax)
  • Business Central Team Members (United States: USD 8.00 per user per month · Canada: CAD 10.90 per user per month, plus applicable tax)

Essentials is the finance, sales, and operations license. Premium is the one that adds service management and manufacturing. Team Members is the light license, not a seat for someone who posts journals or runs MRP. If manufacturing is in phase one, price Premium for the people who plan and consume production, and keep Team Members for people who only look up a document.

Odoo's pricing page shows two USD amounts for Standard, US$31.10 and US$38.90 per user per month, and two for Custom, US$61.00 and US$76.20, on a page with yearly and monthly toggles. A note says the discount is valid for 12 months for the initial users ordered. Do not treat one figure as the yearly rate and the other as the monthly rate until you confirm the toggle. A Light User is listed next to Custom at US$8.90, limited to time off, expenses, attendances, field service, barcode, and similar employee tasks. One App Free is US$0 for one app, unlimited users, on Odoo Online. Subscription does not include implementation. Companies under 50 employees are pointed to Success Packs. Larger companies are pointed to partners.

Those Success Packs are Odoo's published hour bundles for its own services, not a Salesforce integration quote. New-customer list prices are USD 493, USD 3,060, USD 5,950, USD 10,625, and USD 21,250 for 4, 25, 50, 100, or 200 consultant hours. Returning-customer list prices on the same page are USD 580, USD 3,600, USD 7,000, USD 12,500, and USD 25,000. Source: Odoo Success Packs, October 2026. Use them as a reminder that hours are a separate line. Use your own statement of work for a Salesforce connection.

A worked license stack

Assume a 40-person US distributor. Twelve people use Salesforce Sales Pro Suite at the October 2026 list price of USD 100 per user per month. That Salesforce line is USD 1,200 per month. Eight people need Business Central Essentials at USD 80 per user per month, paid yearly: USD 640 per month, USD 7,680 per year. Five warehouse and purchasing roles use Team Members at USD 8: USD 40 per month, USD 480 per year. Business Central list licenses together are USD 680 per month, or USD 8,160 per year. Adding the Salesforce list gives USD 1,880 per month before tax, discounts, and any services.

The same eight Essentials users in Canada are CAD 108.50 each: CAD 868 per month, CAD 10,416 per year, plus applicable tax. The five Team Members are CAD 10.90 each: CAD 54.50 per month, CAD 654 per year, plus tax. Business Central in that Canadian mix is CAD 922.50 per month, or CAD 11,070 per year, plus tax. Salesforce stays on a separate quote because the US Sales pricing page has no CAD column.

If those twelve Salesforce users were on Starter Suite at USD 25, the CRM list would be USD 300 per month. If they were on Sales Max at USD 550, it would be USD 6,600 per month. The ERP line in the US example does not move with that choice. That is the budgeting point: CRM edition and ERP seats are independent, and the services to connect them are a third number you still have to request.

If the same firm dropped Salesforce and put 18 full users on Odoo Standard, the pricing page's two displayed rates imply either USD 559.80 per month (18 times US$31.10) or USD 700.20 per month (18 times US$38.90). Confirm which toggle applies before you put either number in a budget. That subscription includes the CRM apps and the accounting and inventory apps, and it still excludes implementation.

If the decision is to replace Salesforce with Dynamics 365 Sales, the US list as of October 2026 is USD 65 per user per month for Sales Professional, USD 105 for Sales Enterprise, and USD 150 for Sales Premium, each paid yearly, with the same checkout caveat. Twelve Sales Enterprise users would be USD 1,260 per month, paid yearly, close to twelve Salesforce Pro seats at the US list. Read that beside the Dynamics 365 vs Salesforce comparison and the Dynamics 365 scope when replacement is already on the table.

What a first phase should include

A first phase for this situation covers the records that stop the re-key.

Include the chart of accounts, accounts payable, accounts receivable, the item master, inventory valuation if you hold stock, and purchase orders if buyers live in email today. Include the customer and item maps to Salesforce, with one direction each. Include opening balances and open documents, migrated once, with a reconciliation the controller signs.

Leave advanced manufacturing, multi-warehouse optimization, and a CRM rebuild out of phase one unless the business cannot ship without them. Premium versus Essentials is the manufacturing fork: if you need production orders in the first go-live, price Premium for those users from the start. If production is a later phase, Essentials can carry finance and distribution first.

For a first phase on a bounded finance and inventory scope, Flectic's written proposal sets the timeline and a fixed price before work starts. Opening balances, the number of price lists, and whether Salesforce is the customer master all move that timeline. A multi-entity manufacturing rollout needs its own phase plan.

Hold the bidder to four artifacts before you sign: a named list of people and hours, two references of similar headcount and order volume, a phase plan that states what is not in go-live, and a written statement of who owns the code and the integration after go-live. Partner badges do not answer those four. A fixed-scope first phase is realistic when the shared records are listed and the Salesforce objects you will touch are listed. It is not realistic when "integrate the CRM" is one line with no object map.

How to decide without a second sales system

Use the symptoms you can point at in your own files.

Stay on Salesforce, and keep the accounting product you have, when three things are true at once. The pipeline is the complaint. You do not hold inventory that has to be valued. Finance closes from one set of numbers and does not retype Salesforce quotes to get there. Spend the next dollar on CRM discipline.

Add Business Central, or another ERP, beside Salesforce when orders, stock, or vendor bills are maintained outside the CRM and the totals disagree. Price Essentials first when phase one is finance and distribution for a single entity. Price Premium when service management or manufacturing is in that same go-live. Move up to Dynamics 365 Finance, at the USD 210 or USD 300 list, only after someone has shown you a close that Business Central does not cover. Have that shown on your chart of accounts and entities.

Consider Odoo when you want Sales, CRM, Accounting, Inventory, and Purchase on one per-user subscription and you are prepared to move off Salesforce. The Odoo vs Salesforce comparison is the place to test that replacement before you price the subscription. The license can look lower than Salesforce Pro plus Business Central. The project is a replacement of the CRM as well as the books, so the training and the history migration belong in the same proposal. Implementation is not inside the US$31.10 or US$38.90 figures.

In all three paths, write the owner matrix before you write the purchase order. Salesforce keeps accounts, contacts, pipeline, and cases unless you have decided to leave it. The ERP keeps the ledger, payables, receivables, inventory valuation, and purchase orders. The integration, in IBM's terms, lets the CRM order trigger inventory, production, and invoicing so nobody types the order twice. From there, match the list price to the seats you counted and fund the phase you can reconcile.

How Flectic can help

Flectic implements ERP on Odoo or Dynamics 365 for companies of 20 to 100 people that need the order, the ledger and stock in one system beside their CRM. Flectic sends a written proposal with a fixed price for each phase before work starts. Read ERP implementation to see how Flectic builds that scope with your team. Book a free discovery call with Flectic to decide which system owns each record.

Sources

What is Salesforce?, Salesforce, October 2026

We're Salesforce, the #1 AI CRM, Salesforce, October 2026

What Is CRM?, Salesforce, October 2026

Salesforce Sales Pricing, Salesforce, October 2026

What is ERP?, Microsoft, October 2026

Dynamics 365 Business Central pricing (US), Microsoft, October 2026

Dynamics 365 Business Central pricing (Canada), Microsoft, October 2026

Dynamics 365 Finance pricing, Microsoft, October 2026

Dynamics 365 Sales pricing, Microsoft, October 2026

What is ERP?, SAP, October 2026

ERP versus CRM: What's the difference?, IBM, November 2025

Odoo Pricing, Odoo, October 2026

Odoo Success Packs, Odoo, October 2026

Salesforce, Wikipedia, October 2026

Salesforce is a crm not an erp, Hacker News, 2022

Salesforce is CRM, not an ERP, Hacker News, 2023

Manually copying data between systems, Promotional post, 2025

Email the warehouse, Promotional post, 2025

Frequently asked questions

Is Salesforce an ERP?

No. Salesforce describes itself as a cloud CRM and agentic AI platform for customer data, sales, marketing, and customer service. An ERP is the system for finance, procurement, inventory, manufacturing, and the close. Salesforce's own CRM explainer treats accounting and billing as apps you connect, which is a different job from running the books.

Is Salesforce a CRM or an ERP?

It is a CRM. Salesforce, IBM, and the company's product pages place it with sales, service, marketing, and commerce. The ledger, payables, receivables, inventory valuation, and purchasing belong in an ERP that you integrate, or in a suite you adopt if you decide to leave Salesforce.

What does ERP stand for?

ERP stands for enterprise resource planning. In vendor definitions from Microsoft and SAP, that means software that runs finance, supply chain, manufacturing, human resources, procurement, and projects on one shared record. The label matters less than whether the system closes the books and values stock.

What's an example of an ERP next to Salesforce?

Dynamics 365 Business Central is the usual example for a 20 to 100 person firm: Essentials covers finance, sales, and operations, and Premium adds service management and manufacturing. Dynamics 365 Finance is a separate, higher list price when the close needs that product. Odoo is the suite example, because Accounting, Inventory, and Purchase sit on the same per-user plan as its CRM. SAP S/4HANA and Oracle ERP Cloud are the enterprise examples IBM names.

How long does an ERP implementation take beside Salesforce?

Duration follows the phase you sign, not a universal calendar. A first phase limited to the ledger, inventory, purchasing, and a mapped connection to Salesforce is a different project from a multi-entity manufacturing rollout. Ask each bidder for a phase plan with named hours, and treat opening balances and price lists as the items that move the date.

Where can we get implementation services, and how much do they cost?

License lists are not a services price. Salesforce and Microsoft do not publish a project fee to implement an ERP beside Salesforce or to integrate it with Business Central. Odoo's Success Packs are hour bundles for Odoo implementation, from a few hours to 200 hours, and they are not a Salesforce integration quote. Ask every bidder to price migration, the connection, and training as separate lines.

How much does CRM cost if we keep Salesforce?

As of October 2026, Salesforce's US Sales list runs from USD 0 for the Free Suite to USD 550 per user per month for Sales Max, with Starter at USD 25 and Pro Suite at USD 100. The page says those figures are informational and does not show a CAD column. Dynamics 365 Sales, if you ever replace Salesforce, lists Professional at USD 65, Enterprise at USD 105, and Premium at USD 150 per user per month, paid yearly.

Which do we need: an ERP, a CRM, or both?

If you already run Salesforce and the pain is pipeline or cases, you need the CRM you have, worked properly. If quotes and orders are typed again into accounting, or finance is reconciling two sets of numbers, you need both: Salesforce for the relationship, and an ERP for the ledger and stock. Build the money and stock system first when the totals disagree.