Sound Familiar?

Your ERP runs the business. Nobody supports it.

The company that set up your ERPNext has moved on, or answers in weeks, not days. Errors pop up that nobody can explain. Custom features were built that no one understands, so you're afraid to upgrade. Your team works around the system instead of with it.

You don't need to start again. Most ERPNext systems can be stabilised, cleaned up and made to work properly, by a team that knows Frappe well enough to read what was built before.

How We Help

From rescue to routine support.

Takeover from your vendor

We take over support from your previous partner and move hosting, code and admin access into accounts you own.

Health check & audit

A review of your configuration, custom apps, data quality and permissions, with a written report on what's wrong, what's unused and what to fix first.

Fixes & improvements

Error fixes, approval workflows, notifications, scheduled reports, print formats and the small changes that make ERPNext fit your team.

Safe version upgrades

Upgrades tested on a staging copy first, custom apps made compatible, and production upgraded in a short, planned window.

Monthly support plans

A set number of hours each month for fixes, user questions and small changes, plus monitoring of backups, errors and updates.

Advisory & process review

A gap analysis of how ERPNext is used today against how your business should run, and a plan to close the gap.

How a Takeover Works

Secure it, understand it, then improve it.

  1. Secure access

    Hosting, code and admin access moved into your accounts, old vendor access removed, two-factor authentication on, and backups checked.

  2. Audit

    We map your setup, custom apps and data, and give you a written list of issues, ranked by business impact.

  3. Stabilise

    Urgent errors fixed, customisations brought under version control, and staging set up for safe changes.

  4. Improve & support

    Planned improvements and upgrades, then ongoing monthly support so the system keeps up with your business.

What Audits Usually Find

Small gaps, big consequences.

These are the issues we see most often in inherited ERPNext systems. Each one quietly costs time or makes your numbers less reliable, and each one can be fixed.

01

Documents that don't link up

Purchase invoices not linked to purchase orders, and payments recorded but never allocated to invoices, so ageing and reconciliation can't be trusted.

02

Custom features nobody uses

Custom doctypes and fields built for a process that changed, adding clutter and upgrade risk without adding value.

03

Customisations outside version control

Changes made directly on the live site and never saved to code, so they drift between environments and can be lost.

04

Old versions and loose controls

Missed updates and patches, approvals done over chat, and permissions wider than anyone intended.

Upgrades

Upgrades without the downtime drama.

Staying on an old ERPNext version means missing fixes, security patches and new features, and every year you wait makes the jump bigger. We check your custom apps against the new version, rehearse the full upgrade on a staging copy, fix what breaks, and only then upgrade production.

On a recent live system, a full upgrade of ERPNext, Frappe and its supporting apps ran dozens of database patches with under three minutes of downtime.

FAQ

ERPNext support questions.

Can you support an ERPNext system another company built?

Yes. Taking over existing systems is a large part of our work. We start with an audit of your configuration, custom apps and data, then stabilise, document and support it, without starting from scratch.

Our previous vendor controls the hosting and code. What can we do?

We help you move hosting accounts, code repositories and administrator access into accounts your company owns, then remove the old vendor's access and turn on two-factor authentication. You should always own your own system.

Do you support Frappe Cloud and self-hosted ERPNext?

Both. We work on Frappe Cloud sites and on self-hosted servers, and can help you move between them.

We're on an old ERPNext version. Can you upgrade it?

Yes. We check your custom apps for compatibility, run the upgrade on a staging copy first, fix anything that breaks, then upgrade production in a short, planned window.

What does a monthly support plan include?

A set number of hours each month for fixes, user questions, small changes and new reports, plus keeping an eye on backups, errors and updates. Hours and scope are agreed in your proposal.

How quickly do you respond?

We reply within one business day, and urgent issues that stop your team working are handled first.

Can you support us from another time zone?

Yes. All support is remote. We overlap the full working day with the Gulf, mornings with the UK and Europe, and early mornings with the Americas, and bill in USD, EUR, GBP, AED or INR.

Need someone to look after your ERPNext?

Tell us what's going wrong or who built your system. We'll reply within one business day with how we'd take it on.

Start the Conversation →