Skip to main content

ERPNext how-to & fixes

ERPNext Health Check: 12 Things to Review in Your System (2026)

A 12-point ERPNext health check you can run in an afternoon: version support, restored backups, background jobs, custom code, permissions, stock against the ledger and who supports it.

Published 11 Nov 20266 min readBy Manoj

An ERPNext health check finds problems long before something breaks: a slow report, a stock figure that does not match the ledger, a backup nobody has restored. This is a 12-point check you can run in an afternoon, with no tools beyond your own system.

Short answer

An ERPNext health check reviews twelve areas: version and support window, backups you have restored, background jobs, custom code, roles and permissions, stock against the ledger, print formats, integrations, performance, data quality, upgrade readiness, and who supports the system. Score each one green, amber or red. Two or more reds mean get help before the next upgrade.

What are the 12 points?

12 rows · click a column to sort

What to look atRed flag
1Version and support windowVersion in Help > About. Compare with the supported-versions pageA version outside its support window
2Runtimes and serverPython, Node, database, operating system versions against your version's requirementsRuntimes older than your version needs (v16 needs Python 3.14 and Node 24)
3BackupsLast backup date, where it is stored, date of the last restore testNo restore test in the last quarter
4Background jobsScheduler on, job queue not growing, no repeated failures in Error LogJobs stuck for days
5Custom codeCustom apps in a repository; no edits in core files; custom scripts listedAny change made directly to ERPNext or Frappe files
6Roles and permissionsWho can submit, cancel and amend; user permissions on company and warehouseShared logins; "System Manager" on many users
7Stock against ledgerStock Balance report against the stock account in the General LedgerA gap you cannot explain
8Print formats and PDFsInvoices, delivery notes and cheques print correctly; custom formats are versionedFormats copied and edited by hand with no owner
9IntegrationsPayment gateway, e-invoicing, WhatsApp, courier: each one has a named owner and a failure alertA failed sync nobody sees
10PerformanceSlow list views and reports; database tuning; background load at month endReports that time out
11Data qualityDuplicate items and parties, unused custom fields, old draft documentsThousands of draft documents
12Support and ownershipWho fixes a problem at 10 pm; contract; access to code and serverOne person holds every password

How do you check each point?

1 and 2: Version and runtimes. Find your version, then compare it with Frappe's supported versions. Frappe's v16 migration notes list the runtime minimums. If you plan to move, see ERPNext v15 vs v16 and the upgrade impact preview.

3: Backups. Restore the latest backup on a separate test site and open three real documents. See how to test an ERPNext backup restore.

4: Background jobs. Open the job queue and the Error Log. If jobs stall, see ERPNext v16 background jobs stuck.

5: Custom code. List every custom app and every Server Script and Client Script. Ask who owns each one. A change made inside core files will be lost or will break on the next update.

6: Permissions. Run the Role Permissions Manager report for one sensitive document, such as Sales Invoice. See strict user permissions on invoices.

7: Stock against ledger. Compare the Stock Balance report total with the stock account balance. If they differ, read Repost Item Valuation and stock reconciliation before you post any correcting entry.

8–11: Formats, integrations, performance, data. Print one document of each type. List each integration with its owner. Time your three slowest reports. See database tuning. Export the count of draft documents by type.

12: Support. Write down who responds, how fast, and who holds the server and repository access. If you are unhappy with your current support, read how to change your ERPNext support provider.

How do you score it?

Count the reds.

  1. No reds: schedule the next check in six months.
  2. One red: fix it this month; it is usually backups, permissions or a missing owner.
  3. Two or more reds: do not upgrade until they are fixed. A system in this state needs a proper audit; see ERPNext implementation rescue.

Want a second pair of eyes?

We run this audit for ERPNext users: findings and a fix order, written down. See the ERPNext audit. Want to see a clean system first? Open the live demo, no sign-up, or book a 30-minute call.

Frequently asked questions

How often should I run an ERPNext health check?

Every six months, and before any major version upgrade.

Can I do an ERPNext health check myself?

Yes, points 1 to 12 need no special tools. Points 5, 7 and 10 need someone who can read the database or custom code.

Does a health check cost money?

The self-check is free. The audit page says what we offer and how to ask for it.

Want a second pair of eyes on your ERPNext?

MithTech is a team of Frappe specialists. We run this check as an audit: findings and a fix order, written down.

See the ERPNext audit

Your next step

ERPNext how-to & fixes

Now see what an audit finds in yours

When the same problems keep coming back, tick what you see and get an audit of the ERPNext you have, then fixes in order of what costs you most.

Comments & ratings

No comments yet. Start a new discussion.

0

Manoj · Published on 11 November 2026

Worked with us? Leave a Google review

Questions about this? Talk to the team.

Book a 30-minute Google Meet, WhatsApp us, or send a message. The engineer who works on this replies.

Send us a message

Your details go to our team's CRM and are used only to reply.