Skip to content
Hardik Zinzuvadiya
Let's connect

ERPNext and Odoo support and maintenance

Bug fixes, performance work, upgrades and proactive monitoring for ERP systems already in production.

What this covers

  • Bug fixes and performance work on the system you are running now, custom apps included
  • Version upgrades planned as a rehearsal on a copy of production, not as an evening's work
  • Custom apps kept working across upgrades — the part that breaks when a major version lands
  • Monitoring and alerting that pages on what users would feel, with a runbook per environment
  • Backups verified by restoring them on a schedule
  • Taking over a system somebody else built, starting with a read of what is actually installed

How an engagement runs

  1. 01

    A first conversation

    You describe what is slow, manual or fragile. I ask questions, not for a budget, and say plainly whether it is work I should do.

  2. 02

    Scope in writing

    What changes, what does not, how we will know it worked, and what I need from you: access, a copy of the site, a person who knows the process.

  3. 03

    Build on a copy

    Work happens on a staging copy of your site. You review it there before anything touches production.

  4. 04

    Go-live with a gate

    Releases and migrations follow a rehearsed plan with a tested rollback. Nothing writes to production without approval.

  5. 05

    After go-live

    Fixes, monitoring and upgrades under support and maintenance, if you want them.

Related work

High-availability ERP infrastructureTwo application servers, a primary MariaDB with a replica promoted on failure, and Grafana alerting on every environment.Sales Order MonitorOne ERPNext page that shows every Sales Order with its delivery, invoice and payment status and the next action.Attachment Manager for FrappeCard and list views, inline preview for 15+ file formats, and zip download of every attachment inside any Frappe form.

Questions I get asked

We did not build it with you. Will you still support it?
Yes, and that is a common start. The first pass is an audit of what is installed — core version, custom apps, anything patched in place — because that is what any later upgrade depends on.
How do upgrades work once you are supporting us?
The same way as a migration: compatibility audit of the custom apps, a rehearsal on a copy of production, data validation, and a rollback plan that has been tested.
What counts as an emergency?
Whatever users would feel — the system down, a queue stuck, a failed posting run. Those are what the alerts are tuned to, so the page usually arrives before the phone call.