Learnings, and reasons to choose ERPNext over Odoo
summary
Describes moving from 23 Odoo clients to ERPNext after Odoo fails heavy customization needs, spinning up an ERPNext instance on a DigitalOcean droplet, and using the Frappe Framework’s patterns like test_driver.py and a Services directory for shared APIs. Argues ERPNext wins on unrestricted code-level customization, simpler pricing, and built-in modules (project management, e‑commerce) that avoid per-user fees; reports a migration request from a London client and running a hospital build while growing Upeosoft to six developers.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 2:31ERPNext document structure
- 5:02Transition from Odoo to ERPNext
- 8:18Client reactions to ERPNext
- 11:08Reasons to choose ERPNext over Odoo
- 15:21Closing and Q&A
related talks
03mInterview with Sreesanth Vithan
02mInterview with Vinay Kumar
03mInterview with Nikhil Karkare
37mKeynote: ERPNext
16mHow Do I Digitalize and Automate Myself in an Analog Environment?
15mState of the Frappeverse
13mKeynote: Frappe Framework
51mERP project for tens of thousands of users: scared but doing it — how?