How to Migrate From ERPNext to Apragya Without Rebuilding Your Customisations
For businesses running ERPNext, self-hosted or managed: move masters, balances and stock at a period start, and replace custom scripts with settings and AI agents.
Teams that migrate from ERPNext rarely leave because of missing modules. ERPNext is a capable open-source ERP with accounting, stock, manufacturing and HR, and it serves many Indian firms well, especially those with an in-house developer who enjoys maintaining it.
The trouble starts when that developer leaves. Custom fields, server scripts and patched reports have to survive every upgrade, and self-hosting means someone owns backups, security and uptime.
This guide covers what to export from ERPNext, how to handle customisations, an illustrative move at a Ludhiana cycle parts maker, and who should stay.
How to migrate from ERPNext: the short answer
Export lists and reports from ERPNext as CSV or Excel: chart of accounts, customers, suppliers, items, bills of material, stock balance per warehouse, a closing trial balance, and outstanding invoices and bills. Include the values of any custom fields.
Before importing, list every customisation and decide its fate. In practice most server scripts become configured approvals or AI agents, custom fields become custom fields, and a few are retired. Then import in dependency order and agree totals at a financial year or quarter start.
- Export masters, BOMs, stock and open items.
- Audit customisations and decide each one.
- Import accounts, parties and items with custom fields.
- Load BOMs, opening stock and open items.
- Agree the trial balance and switch.
What changes after the move
Apragya
- Updates arrive without custom code to retest
- Hosted, with VPC or on-premise options
- Reports and fields configured by an admin
- AI agents on records, with human review
An illustrative move at a Ludhiana cycle parts maker
Take an illustrative maker of cycle chains and sprockets, 220 people, running ERPNext on its own server with fourteen custom fields and six server scripts. They moved at the start of the financial year.
What happened to each customisation
- Custom fieldsRecreated as custom fields on the same records.Done
- Credit limit scriptBecame a configured approval above the limit.Done
- BOM costing reportCovered by manufacturing analytics.Done
- Dispatch alertAn agent now flags late dispatches for review.Done
- Old print formatsInvoice layout matched to the old one.Checked
- Scrap valuation hackUnder review with the accountant.Pending
Five of the six scripts became settings or an agent, and the sixth was left for the accountant to decide. Opening stock came in per warehouse, bills of material were rebuilt for the forty items still in production, and the old server stayed up read-only for the audit.
How the ERPNext data migration works
Step 1 of 5
Export
Lists and reports downloaded as CSV or Excel.
- Export: Lists and reports downloaded as CSV or Excel.
- Customisation audit: Every custom field, script and report listed.
- Preview and map: Columns matched to Apragya fields, custom fields added.
- Import: Accounts, parties, items, BOMs, then opening stock.
- Open items: Unpaid invoices and bills, then the trial balance agreed.
ERPNext alternative: when a hosted platform fits better
ERPNext rewards teams that want to own and extend their system. Apragya suits teams that want to configure rather than code, with AI agents and Indian compliance maintained for them.
ERPNext and Apragya
| Feature | ERPNext | Apragya |
|---|---|---|
| Licence | Open source; hosting options vary | Subscription with published plans |
| Custom logic | Scripts and custom apps | Configuration and AI agents |
| Hosting | Self-hosted or managed | Hosted, VPC or on-premise |
| Indian compliance | Available through the product and apps | GST, e-invoice, TDS and payroll built in |
| AI agents | Check the project's current features | Agents on records, with human review |
Checked against public information on 16 September 2026.
What you stop maintaining
Upgrade testing
No custom scripts to retest after each release.
Servers
No self-run database or backups to watch.
Rules as settings
Approvals, fields and numbering configured by admins.
Agents instead of scripts
Checks run as agents and wait for human review.
Audit log
User, role, action, record, time and IP.
One record
Every app reads the same party, item and employee.
See the ERPNext comparison, bills of material and open-source ERP vs SaaS ERP.
Getting started
- List every custom field, script, report and print format.
- Decide for each: setting, custom field, agent, or retire.
- Export masters, BOMs, stock and open items at a period start.
- Import and agree the trial balance and stock.
- Keep the ERPNext server read-only for history.
Stay on ERPNext if you have a developer who owns it happily and your customisations are the heart of the business.
What it costs to start
ERPNext migration, answered
Can Apragya read the ERPNext database?
What about our custom fields?
Do we move all transactions?
Can server scripts be replaced?
What does it cost to start?
Keep the rules, lose the upkeep
Audit your customisations and move at the next period start.