Urgent: Need help migrating from ERPNext to ERPClaw

[sofienesalem]

Hello,

I am currently using ERPNext and would like to urgently migrate our setup to ERPClaw. Could you please provide guidance or documentation on:

• Recommended migration steps/process from ERPNext to ERPClaw
• Data migration (customers, invoices, stock, accounting) compatibility
• Any existing migration scripts or tools
• Potential pitfalls or breaking differences between ERPNext and ERPClaw

This is time-sensitive on our end, so any pointers or assistance would be greatly appreciated.

Thanks!

[shridipavansaber]

Hi @sofienesalem, thanks for reaching out, and happy to help you plan this.

Recommended migration path

The proven route is file-based, in five steps:

1. Install ERPClaw. clawhub install erpclaw, or install from this repository. It takes minutes, and SQLite works out of the box (PostgreSQL is fully supported if that is your preference).
2. Export your masters from ERPNext. ERPNext's built-in Data Export gives you CSVs for customers, suppliers, items, and your chart of accounts.
3. Import into ERPClaw. The built-in import actions accept those CSVs: chart of accounts first, then customers, suppliers, and items. Each import runs as one transaction, so it fully lands or fully rolls back, with explicit duplicate handling.
4. Bring in balances, not history. Export a trial balance as of your cutover date and load it as opening balances, then enter your open (unpaid) invoices and bills individually so aging and collections carry over. Bank history comes straight from your bank as statement files (OFX, CAMT.053, MT940, or BAI2), and the imported lines match themselves to invoices and payments where they can.
5. Parallel-run, then cut over. Run both systems side by side for a week or two, compare the key reports, then make ERPClaw the system of record at a clean period boundary (month end is ideal). Keep ERPNext around read-only as your archive.

Full step-by-step guide: https://www.erpclaw.ai/migrate/from-erpnext/

Data compatibility

• Customers, suppliers, items, chart of accounts: clean CSV mapping via the import actions.
• Accounting: opening balances at the cutover date is the recommended approach, rather than replaying years of transaction history. Your ERPNext archive remains available for historical lookups.
• Stock: opening quantities and valuation import; FIFO and moving average are both supported.
• Open documents: unpaid invoices and bills are entered as opening documents so nothing falls through during the switch.

Existing tools

The import actions above ship with ERPClaw today. Honest note: there is no one-click ERPNext importer. The file-based path is what works, and for a typical small or mid-size setup it is a weekend-scale job; plan longer for multi-company setups with heavy history.

Pitfalls and differences worth knowing up front

• Custom DocTypes, server scripts, and print formats do not port. In practice, many of those customizations exist to bend the forms toward how you already talk about your business. ERPClaw's interface is plain language over your own vocabulary, which removes the reason for a lot of them. For anything genuinely custom that remains, tell us what it does and we will suggest a mapping.
• Multi-company is supported inside one install (including consolidated reporting across entities). What ERPClaw does not do is ERPNext-style multi-tenant hosting of unrelated organizations on one server; each business runs its own install.
• Tax depth is US-first in v1, with regional modules for the UK, EU, Canada, and India. If you rely on another region's localization, flag it before you commit to a timeline so we can tell you exactly what is and is not covered.
• The primary interface is plain language (you operate the system by asking in your own words), with a web dashboard in beta alongside it. Teams pick it up quickly, but plan a short familiarization day for whoever runs the books.

Since this is time-sensitive

Email us at support@avansaber.com with your ERPNext version, roughly how many companies you run, and which modules you use daily (stock, manufacturing, payroll, and so on). We will size the migration with you and flag anything specific to your setup before you start, so the weekend you spend on it is the only weekend you spend on it.