ERPNext Support in Kenya: Why Your ERP Needs a Team After Go-Live

Karani GeoffreyJuly 15, 20266 min read

Go-live is not the finish line. It is the moment your ERP stops being a project and becomes infrastructure - the thing your invoices, stock and payroll depend on every single working day. Yet this is exactly the point where many Kenyan businesses let their consultant walk away and hope the in-house team will cope.

Three months later the symptoms arrive. Reports run slowly. Nobody remembers why a workflow was configured that way. A custom script broke after an update. Stock does not reconcile and finance has quietly gone back to Excel. The system did not fail on go-live day. It eroded.

This article explains what ERPNext support and maintenance actually covers, why it matters more than the implementation itself, and how to buy it properly.

What ERPNext support and maintenance includes

Proper support is four different jobs bundled under one name. Understanding the difference stops you from paying for one and expecting another.

1. User support

The everyday questions. "Why can't I submit this invoice?" "Where did that delivery note go?" "How do I reverse a stock entry?" Volume is highest in the first ninety days, then falls sharply if training was done well. If it never falls, you have a training problem being paid for as a support problem.

2. Technical operations

The server side, invisible until it breaks:

Monitored, offsite backups with tested restores - a backup you have never restored is a rumour, not a backup
SSL certificate renewal and expiry monitoring
Disk, memory and CPU headroom monitoring before saturation, not after
MariaDB tuning, slow query review and index maintenance as the database grows
Scheduler and background worker health - the silent cause of "emails stopped sending" and "auto repeat did not run"
Security hardening, patching and access review

3. Functional evolution

Your business changes. A new branch opens. A new tax rule arrives. A supplier wants a different document format. Someone finally needs the report they promised to specify during implementation. This is planned change work, not firefighting.

4. Version upgrades

ERPNext moves fast. Falling three versions behind turns a routine upgrade into a migration project, particularly if customisation was done badly. Staying current is cheaper than catching up.

The failure modes we get called in to fix

Most rescue work we do at Upeosoft Limited follows a small number of predictable patterns.

Customisation on the core app

Someone edited files inside the erpnext or frappe app directly instead of building a custom app. It worked. Then bench update ran and either the changes vanished or the update refused to apply. The business is now frozen on an old version and every fix compounds the problem.

The correct pattern is a custom app with hooks and overrides:

# custom_app/hooks.py
doc_events = {
    "Sales Invoice": {
        "validate": "custom_app.overrides.sales_invoice.enforce_credit_policy",
    }
}

Your logic lives in version control, survives updates, and can be reviewed. Direct core edits cannot.

Backups nobody has ever restored

We ask one question during every health check: "when did you last restore a backup to a test server?" The usual answer is silence. A backup strategy without a restore drill is an untested assumption about the survival of your business.

The database that quietly grew

Error logs, version history, email queue, scheduled job logs and activity logs expand relentlessly. Left alone for two years, a modest instance becomes tens of gigabytes and every report slows down. Routine housekeeping and archiving are maintenance tasks, not emergencies - until they are.

Permission drift

Someone needed to fix something urgently, so they got System Manager. That was eighteen months ago. Now nine people can delete submitted documents and no audit trail is meaningful. Access review is a support deliverable.

The one person who knows everything

Single-person knowledge risk is the most common and least discussed ERP risk in Kenyan businesses. When that person resigns, the system becomes a black box overnight. Support from a team, with documentation, removes that exposure.

What it costs to run without support

Skipping support looks like a saving on a monthly line item. The real costs land elsewhere:

What happens	What it actually costs
Server down during month-end	Invoicing stops, collections slip, cash flow moves right
Stock valuation wrong for months	Every margin decision made on false numbers
Cannot upgrade due to bad customisation	A rebuild priced like a new implementation
Team loses trust in the system	Parallel spreadsheets return, and you pay for both
No restore capability during data loss	Reconstruction from paper, if it is possible at all

An ERP does not usually fail loudly. It fails by slowly becoming something people work around.

What good ERPNext support looks like in practice

When you evaluate a support agreement, look for these specifics rather than the word "support" repeated in a proposal:

Defined response times by severity. "System down" and "please add a column to a report" must not share a queue.
A named channel and named people. Email, WhatsApp, phone - and someone who answers.
Proactive monitoring, not reactive only. Your provider should know about the failing backup before you do.
A monthly or quarterly health report. Backup status, restore test date, disk and database growth, error trends, slow queries, pending updates.
An agreed change process. Small changes included, larger work quoted, everything logged.
A staging environment. Nothing goes to production untested. This is non-negotiable for a system running your money.
Documentation that stays current. Customisations, integrations, credentials custody, runbooks.

Questions to ask any ERPNext support provider

Where do you put customisations, and can I see the repository?
How often do you test restores, and will you show me the last test?
What is your escalation path outside working hours?
How do you handle version upgrades - included, or quoted separately?
If we part ways, what do we get handed over?

That last question is the most revealing. A provider confident in their work will happily describe the handover. A provider relying on lock-in will not.

Support is what makes the clever stuff possible

Businesses often ask us about AI assistants, predictive reordering and automated reconciliation while their scheduler has been dead for two weeks and stock is out by fifteen percent. Automation built on unreliable data does not fix the data - it amplifies the error and distributes it faster.

We have written about this pressure to buy the shiny layer too early in don't get pressured into buying AI before your business is ready. Solid maintenance is unglamorous, and it is precisely what turns an ERP into a foundation you can build automation, dashboards and mobile apps on top of.

How to start

If your ERPNext is already live, start with an honest health check rather than a support contract. You want to know the state of your backups, your customisation approach, your database growth, your security posture and your version gap before anyone quotes you a monthly figure.

Upeosoft Limited is a Nairobi-based ERPNext consultancy, extended with custom engineering, integrations and AI automation. We support ERPNext systems across retail and distribution, manufacturing, automotive, real estate, waste management, security services, professional services and lending, and we have delivered over 200 systems.

Whether your system was built by us or inherited from someone else, we will look at it properly and tell you what we find.

Email: consult@upeosoft.com
Phone: 0116 888 777
Web: upeosoft.com

#ERPNext#ERPNext Support#Maintenance#Kenya#Upeosoft