Migrate from ERPNext to ERPClaw
Open source to open source. AI-assisted DocType transcription, schema mapping, cutover. Single-stack install. Both GPL v3.
Why teams move from ERPNext
ERPNext by Frappe Technologies is a respected open-source ERP with 15 years of history, but the operational and AI stories both create friction. The Frappe stack requires MariaDB or PostgreSQL plus Redis plus Node.js plus Nginx plus Bench, each with its own install and upgrade lifecycle. AI capabilities depend on third-party Frappe apps like NextAI or ChatNext, which fragment install and version management. Install and upgrade pain is a common community complaint.
ERPClaw is AI-native at the action layer, single-stack (Python plus SQLite or PostgreSQL), open source under GPL v3, self-hosted, and $0 forever.
- ·Single-stack install. Python plus one database. No Redis, Node, Nginx, or Bench.
- ·AI-native, not bolt-on. Every action callable from a chat agent, no third-party AI app required.
- ·12-step GL validation. Constitutional invariants enforced at write time.
- ·Database-agnostic. SQLite default or PostgreSQL via PyPika.
What ERPClaw replaces
DocType-to-module mapping. Most ERPNext modules have a direct ERPClaw equivalent.
What ERPNext does better
Honest disclosure. Both projects are open source and we respect the work. If any of these are core to your business, weigh them before committing.
Frappe DocType system is mature
Frappe's DocType abstraction has 15 years of polish. Define a DocType in the UI and you get list views, form views, permissions, and REST API endpoints for free. ERPClaw's spec-first approach is different: you describe what you want in a SKILL.md spec and an AI agent generates the action. Different model, different audience.
Multi-tenant per-site model
ERPNext's Frappe framework supports multiple sites per server with isolated databases. ERPClaw runs one ERP per install today; multi-tenancy is on the roadmap but not shipped. If you host ERPNext for multiple separate customer companies on one server, that pattern needs a different setup in ERPClaw.
Large existing community
ERPNext has 15 years of community contributions, regional partners worldwide, and a deep base of third-party apps on Frappe Cloud. ERPClaw is a newer project with a smaller but growing community. If you rely on a specific Frappe app or regional partner, verify the ERPClaw equivalent before committing.
Polished web UI for non-technical users
ERPNext ships a full web UI for daily operations. ERPClaw is action-first: the canonical interface is the AI agent and CLI; webclaw is dev-only for now. If your finance and operations team need a polished click-through UI today, that is the real constraint.
How the migration works
- 1
Export from ERPNext
ERPNext exports cleanly per DocType. Use Bench (the bench export-doc command with a site flag), or use the Report Builder UI to export each DocType to CSV. Pull Account, Customer, Supplier, Item, Journal Entry, Sales Invoice, Purchase Invoice, Stock Ledger Entry, and your custom DocTypes. Save each as CSV in erpnext-export-YYYYMMDD/. Take a MariaDB or PostgreSQL dump as your safety net.
- 2
Map DocTypes to ERPClaw modules
Walk an AI agent through the ERPNext to ERPClaw field map. Account becomes ERPClaw account, Customer becomes customer, Item becomes item, Journal Entry rows become gl_entry rows. The agent reads SKILL.md specs for each ERPClaw module and produces a mapping plan. Custom DocTypes need explicit decisions: which ones map to existing ERPClaw modules, which need a new module generated from spec.
- 3
Install ERPClaw and run the data transfer
Follow /docs/core/install/. ERPClaw is single-stack: Python plus SQLite (default) or PostgreSQL via PyPika. No MariaDB, no Redis, no Node.js, no Nginx, no Bench. Point the AI agent at the export folder and your fresh ERPClaw install. The agent calls setup-chart-of-accounts, add-account, add-customer, add-supplier, add-item, and post-gl-entries to recreate your books. Frappe Server Scripts and Client Scripts need a separate AI conversation per script.
- 4
Verify and cut over
Run check-gl-integrity in ERPClaw. Compare trial balance, AR aging, AP aging, stock valuation against the ERPNext reports you exported. Investigate any drift before going live. Run parallel for one to two weeks, then cut over. ERPNext is free so timing is less critical than for a SaaS subscription; you just stop using it on cutover day.
Realistic timeline: 3 to 6 weeks elapsed for a team with vanilla ERPNext. 6 to 10 weeks for teams with heavy DocType customization and many Server Scripts.
Stack comparison
ERPNext + Frappe
- ·Python 3.10+
- ·Frappe framework
- ·MariaDB or PostgreSQL
- ·Redis (cache, queue, socketio)
- ·Node.js (for build tooling and socketio)
- ·Nginx (production)
- ·Bench (process manager and CLI)
ERPClaw
- ·Python 3.10+
- ·SQLite (default) or PostgreSQL
- ·No Redis required
- ·No Node.js required
- ·No Nginx required for core
- ·No separate process manager
The single-stack install matters most for self-hosted teams running their own infrastructure. Fewer components means fewer upgrade paths, fewer security patches to track, and faster recovery when something breaks.
Frequently asked questions
Can I export my ERPNext data?
Yes, cleanly. Every DocType in ERPNext exports to CSV via Bench (bench export-doc) or the Report Builder UI. You can also take a full MariaDB or PostgreSQL dump as a safety net. The AI agent reads the CSV exports and runs ERPClaw import actions; you do not write a migration script by hand.
Will my custom DocTypes port?
Mapping is straightforward for custom DocTypes that mirror the common ERP modules (custom Customer or Item extensions, for example). Vertical-specific custom DocTypes need module-level work: the AI agent can generate a new ERPClaw module from spec if your custom DocType is not covered by an existing module. Budget extra time if you have 10 or more custom DocTypes that are not simple field extensions.
Both ERPClaw and ERPNext are GPL v3 and open source. Why switch?
Three structural reasons. First, ERPClaw is AI-native at the action layer: every action is callable from a chat agent, with no third-party AI app. ERPNext relies on third-party Frappe apps like NextAI or ChatNext for AI, which adds install and version complexity. Second, ERPClaw is single-stack: Python plus SQLite or PostgreSQL. No MariaDB, Redis, Node.js, Nginx, or Bench. Third, ERPClaw enforces 12-step GL validation at write time and 23 invariant checks across the system. ERPNext has accounting validation but the constitutional invariant pattern is unique to ERPClaw.
What about my Frappe Server Scripts and Client Scripts?
Server Scripts and Client Scripts need re-implementation in ERPClaw. The good news: ERPClaw's spec-first regen pattern means an AI agent can generate the new action from a SKILL.md description. Tell the agent what each script does and it produces the ERPClaw equivalent. Most server-side logic ports cleanly; complex Frappe-specific framework calls need more care.
How long does the migration take?
For a team with vanilla ERPNext and few custom DocTypes, expect 3 to 6 weeks elapsed including the parallel run. For teams with heavy DocType customization and many Server Scripts, expect 6 to 10 weeks. The AI agent handles bulk data transcription quickly; the customization translation is the variable cost.
Is ERPClaw really free given ERPNext is also free?
Yes, both are free at the software level. The forward cost difference is in operational complexity: ERPNext requires you to operate MariaDB or PostgreSQL plus Redis plus Node.js plus Nginx plus Bench. ERPClaw requires only Python plus your chosen database. For self-hosted teams, that is a meaningful operational cost reduction. For Frappe Cloud users, ERPClaw self-hosted is genuinely $0 versus a Frappe Cloud subscription.
What about Frappe Cloud or hosted ERPNext?
Frappe Cloud and other hosted ERPNext providers charge monthly subscriptions per site. ERPClaw self-hosted is $0 forever. If you currently pay for Frappe Cloud or a managed ERPNext provider, the migration is also a cost reduction. AvanSaber Inc. offers paid implementation services if you prefer managed help; the cost is far below ongoing managed-ERPNext fees.
Ready to start?
Book a demo. We will walk through your specific ERPNext footprint and produce a written migration estimate before you commit to anything.
Book a demoRelated: read the ERPNext comparison, the stack complexity deep-dive, the ERPNext AI ecosystem comparison, the migration hub, or book a demo.