ERPNext CRM vs Frappe CRM: the workflow decides the switch
· Shrivardhan Goenka · 11 min read
Cover image and comparison background: Frappe's official ERPNext versus Frappe CRM article. Integration details: Frappe CRM's ERPNext integration guide.
Frappe CRM is the product Frappe is building for the future of sales. It has a dedicated interface, kanban pipelines, telephony, WhatsApp, service-level agreements and better tools for assigning leads. The CRM module inside ERPNext still reaches further into the transaction and retains several capabilities that Frappe CRM does not replace.
That makes the migration decision narrower than the warning shown in ERPNext v16. The banner says the CRM module will be removed in version 17. The current v17 preview still includes the full module, its navigation has been rebuilt, and the warning has disappeared. Frappe CRM is receiving the new sales features, while the ERPNext module is feature-frozen. Frappe has not published a replacement removal date, so the transition now depends on product parity rather than a hard v17 cutoff.
For the broader release picture, our ERPNext v16 vs v15 comparison separates shipped ERPNext changes from Framework changes and later v16 work.
ERPNext CRM and Frappe CRM solve different parts of the sale
ERPNext CRM starts with a Lead and Opportunity, then continues through Quotation, Sales Order and Customer without leaving the ERP. It also includes Prospect, Market Segment, Competitor and CRM Note records. That shape suits a team whose sales process is tightly connected to products, price lists, procurement, contracts and downstream commissions.
Frappe CRM has its own lead, deal and organization records. Its dedicated sales interface is built around daily sales work: kanban boards, saved views, quick filters, group-by controls and a mobile PWA. Stages have their own probability and position, while dashboards show forecast revenue and conversion by stage, source, territory or salesperson.
The new app is the better place to work a pipeline. ERPNext remains the deeper place to model everything that happens around it.
| Capability | ERPNext CRM in v16 | Frappe CRM |
|---|---|---|
| Pipeline | Lead, Opportunity, Quotation, Sales Order and Customer | CRM Lead, CRM Deal and CRM Organization |
| Daily interface | Frappe Desk lists, forms and reports | Dedicated Vue app with kanban, saved views, quick filters and PWA |
| Reporting | Nine script reports plus Desk report builder | Forecast and funnel widgets, with no report builder |
| Communications and Email Campaign drip sequences | Threaded email, shared accounts and templates, with no campaign drip | |
| Campaign attribution | Campaign and UTM Campaign links reach Quotation, Sales Order and Invoice | Lead Source only, with no UTM revenue chain |
| Calling and messaging | No built-in CRM calling or WhatsApp | Twilio, Exotel and WhatsApp through the Frappe WhatsApp app |
| Service levels | First Response Time report | Deal SLA engine with holidays and rolling response time |
| Lead capture | Web forms, Contact Us and inbound email | Web forms, Facebook Lead Ads and domain enrichment |
| Assignment | Standard Desk Assignment Rule | Assignment rules UI and sales hierarchy permissions |
| Commercial records | Appointments, Contracts, Competitors and supplier quotation paths | No direct equivalents for those records |
What Frappe CRM adds
Frappe CRM fixes a daily usability problem. A salesperson can move deals on a board, group them, save a view and work from a phone without treating an ERP form as a sales application. The forecast dashboard calculates expected value from deal amounts and probabilities, which makes pipeline review part of the product rather than a spreadsheet assembled after the meeting.
Communication is also closer to the deal. Twilio supports browser calling, Exotel adds another telephony route, and call logs remain attached to CRM activity. WhatsApp conversations can appear through the separate Frappe WhatsApp app. Shared email accounts and templates keep correspondence inside the sales workspace.
Frappe CRM goes further on response discipline. Its SLA engine can track deal response times against holidays and calculate a rolling response time. Assignment rules have their own interface, and sales hierarchy permissions use an organization tree so managers can see and distribute work without giving every salesperson the same access.
Lead capture is stronger too. Facebook Lead Ads can feed records into CRM, embedded web forms collect enquiries, and the domain-enrichment crawler can add company information. These additions remove repeated entry before the first sales conversation begins.
What ERPNext CRM still does that Frappe CRM does not
Switching also removes ERPNext-only sales workflows. ERPNext Email Campaigns can run drip sequences, while Campaign and UTM Campaign records carry attribution into quotations, orders and invoices. Frappe CRM has a source field, but it does not reproduce that revenue trail or the email-campaign engine.
ERPNext also keeps several commercial records beside the Opportunity. Contracts have templates and fulfilment terms. Appointment settings expose public booking slots. Competitor records can be attached to opportunities and quotations. An Opportunity can lead into a Request for Quotation and Supplier Quotation when a sale needs a procurement step.
The Sales Person tree and Sales Team tables continue into downstream documents and commission reporting. SMS Center, automatic lead or opportunity creation from inbound Communications, and the Desk report builder also lack direct Frappe CRM equivalents. Standard Frappe workflows can be applied to the ERPNext records that already run the business.
A team using any of those features must design the migration around them. It must decide where each missing workflow will live and how the resulting records will connect to the sale.
The same-site integration stops at the quotation handoff
Frappe CRM includes ERPNext CRM Settings, where an administrator can enable the connection, choose the ERPNext company, decide when a deal should create a Customer and turn on product synchronization.
The richest path runs both apps on the same Frappe site. Enabling it adds links between CRM Deal, Quotation, Customer and Item. The CRM Deal then shows Create Quotation and View Customer actions. Create Quotation opens a new ERPNext Quotation with the deal and its product lines already filled in.
The integration does not copy the full deal into ERPNext. The transaction begins in ERPNext at the quotation boundary. A Customer can be created when the deal reaches a configured status, which defaults to Won, or when a Sales Order validates a quotation linked to a CRM deal.
Product synchronization is more substantial. ERPNext Item acts as the source of truth, including a selling price from the configured price list. Creating, editing, renaming or deleting an Item can update the CRM Product. An optional reverse sync sends product changes back. User Permissions and DocShares are mirrored, and the settings page records synchronization failures for an administrator to resolve.
Leads, deals, activities, emails and tasks remain in Frappe CRM. They do not synchronize into ERPNext CRM. The integration moves a qualified deal into quotation and customer workflows, then keeps products and selected permissions aligned.
Remote integration is much thinner
Frappe CRM can run on a different site and connect to ERPNext with an API key and secret. It can create a Prospect or Customer against a CRM deal. The ERPNext administrator must also enable Frappe CRM data synchronization in CRM Settings and choose which users may create those records.
Remote mode does not provide same-site Item synchronization or local customer resolution. It may also leave ERPNext's synchronization switch disabled after setup, so the administrator should confirm that setting manually before testing the handoff.
Same-site deployment gives product sync and a direct quotation handoff. Separate sites can create Prospects and Customers, but leave more records and failure handling to the implementation.
rtCamp provides the practical migration path
Frappe's June 2025 comparison said migration tools were in development. Frappe CRM still has no official ERPNext CRM importer. Its generic Data Import page can load CSV records, but it cannot carry activity, email and reference history without custom work.
rtCamp's ERPNext CRM to Frappe CRM migrator is the most complete available route. It maps Lead to CRM Lead, Opportunity to CRM Deal and Prospect to CRM Organization. It also handles masters such as Territory, Industry, UTM Source, Lost Reasons and Items, then rewrites references across comments, ToDos, notes and versions. An interactive interface supports field mapping, and the migration can be undone before cleanup.
rtCamp maintains the migrator independently; Frappe does not support it. Frappe, ERPNext and CRM must all be on v16 or later and installed on the same site. Teams with separate CRM and ERPNext sites cannot treat it as a drop-in route. rtCamp archived its next_crm project and now points users to Frappe CRM and the migrator.
Run the migrator against a restored production backup on staging. Count leads, opportunities, organizations, activities and linked masters before and after. Open representative records with long histories, custom fields and unusual permissions. Do not delete the source records until the new pipeline, quotation handoff and rollback have been verified.
Switch now, wait, or run both
Switch now when the sales team needs kanban, telephony, WhatsApp, deal SLAs, Facebook capture, sales hierarchy permissions and forecasting more than it needs ERPNext's campaign and commercial records. The case is strongest on a same-site v16 bench because product sync and the quotation handoff are available, and the rtCamp migrator can preserve more history.
Wait when Email Campaigns, UTM revenue attribution, Contracts, Appointments, Competitors, supplier quotation workflows, downstream Sales Team commissions, SMS or Desk reporting carry real work. Frappe CRM does not yet offer like-for-like replacements. A two-site deployment also deserves caution because its integration is narrower.
Running both can be sensible during the transition. Frappe CRM can own new sales activity while ERPNext remains the system for quotations, orders, customers and the older records that have no destination yet. The boundary must be written down so salespeople do not update two pipelines for the same deal.
Frappe's published direction favors the standalone app, while its older module receives no new features. Plan the move around workflow parity and a tested migration instead of an unconfirmed deletion date.
