Frappe CRM vs ERPNext CRM: which to choose

Which CRM should a Frappe or ERPNext team choose?

If your team already runs ERPNext and needs a CRM, start with a fact that changes the question: the ERPNext CRM documentation states that the CRM module is scheduled for deprecation and will be completely removed in version 17, and Frappe's June 18, 2025 blog says it receives only bug fixes with no new features. Choosing ERPNext CRM today means planning a move before that removal, not treating it as a long-term home. The decision turns on three things: how tightly you depend on the ERP, the removal date, and the same-site limit on the integration. ERPNext CRM fits when quotations, invoices and stock must stay in one flow. Its Lead, Opportunity and Quotation chain is tied to invoicing, inventory and projects, so a team that bills and ships from the same records gains from keeping them together. Choose it only if you are not planning a move, you accept bug-fix-only support, and you can confirm with your Frappe partner what a migration to Frappe CRM will involve for your data.

Frappe CRM fits when the sales team needs telephony, a deal pipeline, a phone-first interface or a standalone deployment. It offers leads and deals with stage-based pipelines, built-in Twilio and Exotel calling with call recording, and a progressive web app. Its ERPNext integration works through a Create Quotation button on a deal, but item and product sync runs only when both apps are on the same site. If your sales users need ERP records outside that site, or you want the CRM to run without ERPNext, plan for separate data handling and confirm the integration scope in writing before you commit. Before you choose, check three items: whether your ERPNext version is on Frappe's supported versions list, whether Frappe CRM's stable v1.x branch supports your Frappe and ERPNext versions, and whether your Server Script or LDAP and social login requirements are compatible with your hosting plan. Ask a partner to map every quotation and customer sync your sales process needs, and confirm whether those syncs work on a single site before the first sprint.

Which platform fits each team scenario

This table maps six common team situations to the platform that fits better, and names the ERP dependency behind each choice. Read it against your own invoicing, stock and sales process, because the ERP dependency is the main deciding factor.

Scenario	Better fit	Why
Invoicing and stock run in ERPNext, and sales works through quotations	ERPNext CRM for now, with a planned move	Lead, Opportunity and Quotation are tied to invoices, inventory and projects. ERPNext CRM is scheduled for removal in version 17, so plan the migration rather than staying indefinitely.
Sales needs calling, WhatsApp and a mobile-friendly deal pipeline	Frappe CRM	Built-in Twilio and Exotel calling, WhatsApp through the Frappe WhatsApp app, and a progressive web app suit field and phone-first sellers. Confirm your telephony provider is supported.
On ERPNext, with no decision on a move yet	Frappe CRM, evaluated on a copy of your data	ERPNext CRM receives bug fixes only, so new work favors Frappe CRM. Test the ERPNext integration on the same site before committing, since item and product sync requires both apps there.
Wants a CRM without an ERP	Neither, unless the ERP is planned	Frappe CRM can run alone, but its quotation and customer sync depends on ERPNext on the same site. Without ERPNext, evaluate a standalone CRM such as EspoCRM or Twenty.
Needs Meta lead syncing and assignment rules	Frappe CRM	The documentation describes lead syncing from Meta Facebook and Instagram ads, web forms and assignment rules. Confirm the Meta connection and rules against your own ad accounts during a trial.
Sales hierarchy must limit what each user sees	Frappe CRM, with a role review	The sales hierarchy restricts visibility, and Sales User, Manager and Admin roles apply. ERPNext CRM access depends on ERP roles, so map each team to both before choosing.

How each is built and what that means for operations

Both products sit on the Frappe Framework, so they share patching rhythms, runtime services and upgrade dependencies. The differences lie in how the CRM is packaged, which site it shares with ERP data and how closely its version must track ERPNext.

ERPNext CRM as an ERP module

The CRM module ships inside ERPNext, which is GPL-3.0 and built on the MIT-licensed Frappe Framework. Lead, Opportunity and Quotation records live in the same database as invoices, stock and projects, so one upgrade touches sales and finance together. Before you patch, check which ERPNext modules your users depend on, because a CRM change can affect them. Note that the CRM module is scheduled for removal in version 17.

Frappe CRM as a standalone app

Frappe CRM is AGPL-3.0 and installs as its own app on the same framework, with a Vue interface built on Frappe UI. You can upgrade it on its own release cadence, which currently includes frequent tagged releases. Confirm which Frappe CRM tag your team will pin, and test the Vue front end on the browsers and phones your sales staff actually use.

Shared site for item and product sync

Item and product sync between Frappe CRM and ERPNext runs only when both apps are installed on the same site. Quotation creation from a deal works through that same link, so separating the two onto different sites removes those features. Plan the site layout before installation, and treat any move of the CRM to another site as a data and integration project with its own testing.

Bench, Compose and easy-install options

Frappe CRM can be installed with the easy-install script, the ghcr.io/frappe/crm image, or bench for development. The frappe_docker repository provides production Compose files with services for MariaDB, Redis, background workers, the scheduler, Socket.io and Nginx. Its single-file demo setup is intended only for short-lived evaluation, so production deployments need the full service set and a backup plan for MariaDB.

Compatibility with ERPNext 15 or 16

The stable v1.x branch of Frappe CRM supports Frappe and ERPNext versions 15 and 16. Any upgrade of ERPNext to a new major line must be matched by a compatible CRM branch, so the two version numbers should be recorded together in your change log. Ask Frappe or your implementation partner which CRM release works with your planned ERPNext target before scheduling the upgrade window.

Support windows govern both apps

Frappe lists version 15 as supported until the end of 2027 and version 16 until the end of 2029, and both apps follow those windows. Version 14 reached end of life on January 31, 2026. Warranty coverage from Frappe depends on running a listed version and holding a matching Frappe Cloud support plan. Use these dates to schedule the next major upgrade, not as a reason to delay security patches.

Feature and architecture comparison at a glance

This table sets the built-in ERPNext CRM module beside the standalone Frappe CRM app, row by row, so you can see where the two diverge on data model, integrations and deployment. Read the license and support rows first, because ERPNext CRM is scheduled for removal in version 17. Where a row shows a point to confirm, check it against your own Frappe Cloud or self-hosted environment before you commit.

Capability	ERPNext CRM	Frappe CRM
License	GPL-3.0 as part of ERPNext	AGPL-3.0
Support status	Scheduled for removal in version 17; no new features, bug fixes continue	Actively developed; stable v1.x branch targets ERPNext and Frappe versions 15 and 16
Data model	Lead, Opportunity and Quotation flow linked to quotations, invoices, inventory and projects	Leads and deals with stage-based pipelines and a unified activity timeline
Tie to invoicing and stock	Native, since quotations, invoices and inventory live in the same ERP	Through the ERPNext integration only; a deal can open a pre-filled quotation, and item sync needs both apps on the same site
Telephony	Confirm with your ERPNext setup; not part of the CRM module as described in the supplied sources	Built-in Twilio and Exotel calling with call recording
WhatsApp messaging	Confirm before relying on it; no supplied fact covers it for ERPNext CRM	Through the Frappe WhatsApp app
Meta lead sync	Confirm with your ERPNext setup; no supplied fact covers it	Lead syncing from Meta (Facebook and Instagram) ads, per the Frappe CRM documentation
Web forms	Confirm with your ERPNext setup; no supplied fact covers it	Web forms create leads directly
Assignment rules and sales hierarchy	Confirm the exact permission model in your ERPNext version	Assignment rules and a sales hierarchy that limits what users can see, with Sales User, Manager and Admin roles
Mobile use	Confirm mobile behavior in your ERPNext version	Works in a phone browser and can be added to the home screen like an app
Deployment options	Frappe Cloud, Docker Compose or bench; it is part of the ERPNext install	Frappe easy-install script, the ghcr.io/frappe/crm image, bench for development, or Frappe Cloud

What each option costs in licensing and paid services

ERPNext is licensed under GPL-3.0, and the Frappe Framework it runs on is licensed under MIT, according to the license metadata of the frappe/erpnext and frappe/frappe repositories. The CRM module ships inside ERPNext, so there is no separate licence line for it. Your cost sits in hosting, administration and any implementation work.

Software licence: ERPNext is GPL-3.0, so you can self-host it without a licence fee. Ask counsel how GPL-3.0 applies to any modifications you distribute.
Self-hosting: The ERPNext pricing page says self-hosting ERPNext is free. Servers, storage, backups and staff time are still yours to fund.
Implementation: The ERPNext pricing page says implementation is available through certified partners. Each partner sets its own fees in its quote, so compare written scopes rather than headline rates.
Recurring work: Both supported major versions receive frequent minor releases, so patching and upgrade testing recur every year.
Future migration: ERPNext CRM is scheduled for removal in version 17. Plan the move to Frappe CRM as a cost you will likely carry, and price it into your budget now.

Before you sign, ask any partner which version it will target, whether migrating CRM data to Frappe CRM is in scope, and what the fixed fee covers if the module is removed.

What ERPNext CRM's removal in version 17 changes for your plan

The ERPNext CRM module is scheduled for complete removal in version 17. The ERPNext documentation for the develop version says the module is scheduled for deprecation, will be fully removed in version 17, and that Frappe recommends Frappe CRM instead. Frappe's June 18, 2025 post, ERPNext vs Frappe CRM, what's the difference, adds that ERPNext CRM is no longer evolving: it gets bug fixes but no new features, and Frappe is building a migrator to Frappe CRM. Until that migrator ships, the standard data import tool is the documented route for moving leads, opportunities and customers sooner. For the current supported lines, Frappe's supported versions page lists version 15 until the end of 2027 and version 16 until the end of 2029, so a team on either line has a support window that runs past version 17. Confirm the removal timing in the current ERPNext release notes before you set a plan, because the date that matters is the first release that drops the module, not the date of the blog post.

The practical risk is not that ERPNext stops working on the day version 17 arrives. It is that a team which stays on ERPNext CRM ends up with a module that gets only bug fixes, then has to move its Lead and Opportunity records, quotation links and sales hierarchy under a deadline set by an upgrade. Before you commit, inventory what your users rely on: the Lead to Opportunity to Quotation flow, the custom fields and scripts attached to those doctypes, and any reports that read them. Check whether those customizations depend on Server Scripts, which from version 15 are disabled by default and must be enabled with server_script_enabled, and whether your hosting permits them. Ask your implementation partner to test an import of a representative sample of records into a staging site on the target version, then confirm that quotations, invoices and stock still link correctly after the move.

What drives the running cost of each option

Running cost splits into a few payers: the software licence, the hosting, the people who run and upgrade the stack, and the partner who implements the work. Each one is one-time or recurring, and each moves with decisions you make early, including whether CRM data lives on the same site as ERPNext.

ERP licence cost

ERPNext is free and open source under GPL-3.0, and self-hosting it carries no licence fee, so the licence line is zero for both the ERPNext CRM module and a standalone Frappe CRM app that sits on the same Frappe stack. The recurring cost is not the licence. It is the hosting, the people and any paid support you add. Ask a partner to confirm in writing that no third-party modules in the quote carry their own licence fees.

Hosting on Frappe Cloud or your servers

Frappe Cloud bills a shared site per month, and dedicated servers are billed separately, so the hosting line recurs for as long as the site runs. Self-hosting moves that cost to your own cloud account or data centre, where it depends on server size, backups and storage. Costs rise with dedicated capacity and with a second environment for testing upgrades. Confirm which hosting model the quote assumes and whether a staging site is included.

Skills for bench and Docker Compose

A self-hosted stack needs people who can run bench or the frappe_docker Compose files, and who can operate MariaDB, Redis, background workers, the scheduler, Socket.io and Nginx. This is a recurring cost in staff time, and it rises when the same team also maintains ERPNext. Frappe's own guidance treats the single-file demo setup as suitable only for short-lived evaluation, so budget for a production layout from the start. Ask who on your team will own upgrades and on-call response.

Paid support and warranty coverage

Frappe's supported versions policy ties warranty coverage to running a listed version and holding a Frappe Cloud support plan that matches it. That makes support a recurring subscription, and it is a condition of warranty rather than an optional extra. Support cost moves with the major version you run, since version 14 is past end of life and version 15 is supported only until the end of 2027. Check which version the support plan covers before you commit to a timeline.

Certified partner implementation

Implementation is a one-time cost paid to a certified partner, and it covers configuring Lead and Opportunity flows, the Quotation link to invoicing and stock, user roles and the Frappe CRM app itself. Cost rises with custom Server Scripts, which are disabled by default from version 15 and must be enabled, and with telephony and WhatsApp setup. Ask the partner for the written scope, the named deliverables and whether acceptance testing is included.

Migrating ERPNext CRM data

Moving from ERPNext CRM is a one-time project. Frappe says a migrator is in progress, and the standard Data Import tool can move records sooner, but it advises importing only a few thousand records at a time. Volume, child table rows, custom fields and the number of batches drive the effort. Ask for a record count, a mapping of Lead, Opportunity and Quotation fields, and a rollback plan before import begins.

How to move from ERPNext CRM to Frappe CRM in order

This sequence moves Lead, Opportunity and Quotation work from the ERPNext CRM module into the standalone Frappe CRM app while keeping the quotation and customer links that matter to sales and finance.

Inventory leads, opportunities and linked quotations
Sales operations lists every Lead, Opportunity and Quotation in ERPNext CRM, along with the invoices, customers, items and projects those records link to. Export counts by status and owner so you know what must move and what can be archived. Record which fields your team relies on, because the standard import will not carry every link automatically. Done means you have a signed-off inventory that shows the record volumes and the linked documents each team depends on.
Decide whether Frappe CRM shares the ERPNext site
The platform owner and the sales lead decide whether Frappe CRM will run on the same site as ERPNext. Quotation creation from deals and item and product sync work only when both apps share one site, and customer creation on Won also depends on that arrangement. If you need those flows, plan the target as one site. If the CRM will run separately, document which quotation and customer links will be manual. Done means a written decision on site layout is approved before any data moves.
Confirm a supported version pairing
The platform team checks that the Frappe CRM version you plan to deploy is compatible with the ERPNext and Frappe Framework versions in use. The stable Frappe CRM v1.x branch is listed as compatible with versions 15 and 16, and version 14 has reached end of life. Confirm the target versions against Frappe's supported versions page and, if you use Frappe Cloud, confirm the matching support plan. Done means a documented version pairing that is on a supported line, with a rollback path if an upgrade fails.
Import records with the Data Import tool
The data owner exports Leads, Opportunities and Quotations from ERPNext CRM into the CSV or Excel templates that the Data Import tool provides, then imports them in batches. The documentation advises importing only a few thousand records at a time, so split large sets by status or owner. Child table rows, such as quotation items, must be checked against the parent records after each batch. Done means each batch reconciles against record counts, and a sample of parent and child rows matches the source.
Rebuild assignment, web forms, email and roles
The CRM administrator recreates assignment rules, web forms, email accounts and templates, and the sales hierarchy in Frappe CRM. Assign users to the Sales User, Manager or Admin roles so visibility matches the current team structure. Note that Server Scripts are disabled by default from version 15 and must be enabled with the server_script_enabled setting, and that Frappe Cloud public shared benches do not allow them, so any custom logic must be redesigned or hosted elsewhere. Done means each rule and role is tested with a named user from each team.
Test quotation and Won-to-customer flows before cutover
Sales and finance run test deals through the Create Quotation button and through the path that creates an ERPNext customer when a deal is marked Won or reaches the chosen status. Check that the quotation is pre-filled correctly, that items sync, and that the customer record is not duplicated. Repeat the tests with a Manager and a Sales User to confirm visibility. Done means the test log shows every flow passing, with failures fixed and retested before the production cutover is scheduled.

Where Frappe CRM and ERPNext CRM projects usually run long

Projects slip most often when teams treat the CRM move as a data import rather than a change to how the ERP and the CRM share a deployment. Start by cleaning lead and account records before anything is loaded. ERPNext's Data Import tool handles CSV, Excel and public Google Sheets with child table rows, but its documentation advises importing only a few thousand records at a time, so large legacy pulls need batching and a reconciliation pass. Custom fields and Server Scripts are the second risk. Server Scripts run Python on document events or as API endpoints, and from version 15 they are disabled by default until the server_script_enabled setting is turned on. Confirm with your ERP administrator whether that setting is permitted on your hosting tier, because Frappe Cloud public shared benches do not allow Server Scripts at all. The same-site constraint shapes the architecture. Item and product sync between Frappe CRM and ERPNext runs only when both apps are on the same site, so choosing a standalone CRM hosting arrangement can silently remove quotation sync. Decide early whether the sales team will work quotations from deals in the shared ERP site, and plan the deployment, backups and upgrades around that single site. Sales operations should also map deal stages, assignment rules and the sales hierarchy that limits record visibility before go-live, since those choices are hard to unwind once users have built habits on them.

Channel configuration is where scope tends to grow. Telephony needs a Twilio or Exotel account, call recording settings and agent mapping. WhatsApp messaging depends on the separate Frappe WhatsApp app. Meta lead sync for Facebook and Instagram ads needs its own connection, field mapping and assignment rules, and each of these depends on credentials the client must provide and approve. Your security owner should review the identity side as well, including any LDAP or social login configuration, using the ERPNext LDAP integration and Frappe's Social Login Key documentation as the starting references, and confirm who may hold those credentials and where they are stored. The work needs three client roles: ERP administrators for site, Server Script and data decisions, a security owner for identity and credential approval, and sales operations for pipeline and assignment design. DeployOpen plans and implements these items within a fixed written scope, so the scope document should list each channel, integration and data source explicitly, with acceptance criteria for each. Ask for those items to be named in any quote, since telephony, WhatsApp and Meta sync are the first places where unlisted work appears.

Questions buyers ask before moving from ERPNext CRM to Frappe CRM

Does ERPNext CRM have to be removed before version 17 arrives?

Yes, the ERPNext CRM documentation states that the module is scheduled for deprecation and will be completely removed in version 17, and that Frappe recommends using Frappe CRM instead. Frappe's June 18, 2025 blog adds that ERPNext CRM receives bug fixes but no new features, so a move is a planning decision with a known end point. Confirm the exact removal schedule against the current ERPNext documentation and your own ERPNext upgrade calendar before you set a date.

Does self-hosting Frappe CRM cost anything in license fees?

No license fee applies to the software itself, because Frappe CRM is licensed under AGPL-3.0. The costs you carry are the servers, storage, backups, and the people who run the platform, plus any implementation work you buy. If you use Frappe Cloud, the Frappe CRM product page lists plans from 5 US dollars a month per site with unlimited users and no per-seat charges, billed by usage. Ask any partner to separate one-time migration work from recurring hosting and support in the quote.

How much effort does the move take, and what drives it?

Effort depends on how much of your sales process runs through quotations, invoices and stock in ERPNext, the volume and quality of existing CRM records, and how many custom scripts or reports you rely on. Records move through the standard data import tool, which the ERPNext documentation advises using a few thousand records at a time. Custom Server Scripts also need review, because from version 15 they are disabled by default and must be enabled with the server_script_enabled setting. Ask for a written inventory of these items before agreeing a fixed scope.

Can our team do the move alone with the import tool?

A small team with clean data and a simple pipeline can often handle a move with the import tool, while a team with many custom fields, linked quotations and multiple sites needs a plan first. The ERPNext Data Import tool imports and updates records from CSV or Excel files using templates and supports child table rows, but it does not carry the full ERPNext CRM flow into Frappe CRM by itself. Frappe has said it is working on a dedicated migrator, so check its current status before you choose a method. Test on a copy of the site and verify record counts and links before cutover.

Does Frappe CRM work without ERPNext?

Yes, Frappe CRM is a standalone app built on the Frappe Framework, and the Frappe blog notes it was launched as a standalone app in 2023. It provides leads and deals with stage-based pipelines, a unified activity timeline, telephony through Twilio or Exotial, WhatsApp messaging, web forms and lead syncing from Meta ads. ERPNext integration is optional and only needed if you want quotations and customers to flow into the accounting and stock modules. Confirm that your required telephony provider and Meta integration fit your region and account setup.

What does the ERPNext integration require on one site?

Most syncing works only when Frappe CRM and ERPNext run on the same site. The integration lets a Create Quotation button on a deal open a pre-filled ERPNext quotation, and it can create an ERPNext customer when a deal is marked Won or reaches a chosen status. Item and product sync runs only under the same-site condition. Check that your Frappe and ERPNext versions match a compatible pair, since the Frappe CRM stable v1.x branch supports versions 15 and 16, and plan your site layout before the move.

Do we need a Frappe Cloud support plan to keep warranty coverage?

Frappe's supported versions policy says customers must be on a listed version and subscribed to a matching Frappe Cloud support plan to receive warranty coverage from Frappe. This applies to Frappe's own warranty terms, not to your right to self-host the open-source code under its license. Confirm which ERPNext and Frappe version you will run, check the supported versions page, and decide whether vendor warranty or a third-party support retainer fits your risk profile. Ask a partner to state how upgrades and security patches will be handled under your chosen model.

What should we ask a partner for in a quote?

Ask for a written scope that lists the data to migrate, the integrations to rebuild, the environments to set up, and the testing and cutover steps. DeployOpen plans, implements, integrates, backs up, upgrades and documents self-hosted open-source platforms inside your own infrastructure, and most engagements are fixed-scope with scope, deliverables and timelines agreed in writing before work starts. Ask for the assumptions behind the price, which items are one-time and which recur, what ongoing support covers, and how change requests are priced. DeployOpen does not publish a price list, so a quote follows from the written scope.

How DeployOpen helps choose, implement or migrate

DeployOpen plans, implements, customizes, integrates and documents self-hosted open-source platforms inside the client's own infrastructure. For Frappe CRM vs ERPNext CRM, we start with a written view of which CRM fits your ERPNext data, users and deployment, then carry the chosen path through to a documented handover.

How we scope

Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
We map which Lead, Opportunity and Quotation records, and which ERPNext customers and items, must move or stay in place.
We confirm your ERPNext version and whether Frappe CRM will share a site with ERPNext, since most sync depends on it.

How we build

We install Frappe CRM on your infrastructure with the method you choose, then configure leads, deals, roles and the sales hierarchy.
We test the Create Quotation and customer creation flows on a staging site before any live users depend on them.
We review custom Server Scripts and telephony or WhatsApp settings against your security and data handling rules.

How we hand over

We deliver written documentation of the configuration, integrations, data migration steps and the decisions behind them.
We run the migration from ERPNext CRM records and validate counts and ownership with your team before cutover.
We walk your administrators through backups, upgrades and the rollback steps they will need to run themselves.

How we support

Ongoing support, upgrades and continuous testing are available as retainers after handover.
We can plan Frappe CRM upgrades against the Frappe and ERPNext versions your site runs, with testing before each change.
Ask us to confirm the support scope, response expectations and retainer terms in your written quote before engagement.

Frappe CRM vs ERPNext CRM