An ERPNext AMC (annual maintenance contract) covers bug fixes, small changes, version upgrades and user support. What it costs depends on five things: how many people use the system, how much custom code you carry, the response time you need, how often you upgrade, and whether hosting is in the contract. This guide explains each one and what to ask before you sign. To see support priced with the rest of your rollout, see ERPNext implementation cost and pricing in India, by stage.
If you already run ERPNext, an AMC is what keeps it patched, upgraded and supported when something breaks. "Support" is priced very differently from one provider to the next, and vague contracts hide surprises.
The short version: size the AMC to your users, your custom code and the response time you really need, get a written scope (what is covered, response times, upgrade policy), and never accept "support" as an undefined word. I am Manoj; I run support and managed operations for production ERPNext and Frappe systems at MithTech, a team of Frappe specialists in Bengaluru.
What decides ERPNext AMC cost in India?
Five things: the number and kind of users, the custom code you carry, the response time you need, how often you upgrade, and whether hosting sits inside the contract. A lightly customised system on business-hours support needs far less effort than a multi-company system with custom apps and a priority SLA, so it costs less. Ask each provider to price against the same answers, or the quotes will not compare.
| Why it moves the cost | What to ask | |
|---|---|---|
| Users and roles | More users and more distinct jobs mean more tickets, training questions and permission changes | How many active users, and how many departments raise requests? |
| Custom code | Every custom DocType, report, workflow and integration must be retested, and often fixed, at each upgrade | How many custom apps and integrations will the provider be responsible for? |
| SLA and response time | A one-hour response on a priority line needs people on standby; next business day does not | What response and resolution times do we need, for which severity? |
| Upgrade cadence | Minor releases are routine; a major upgrade needs a staging copy and regression testing | How many major upgrades a year are included, and who tests them? |
| Hosting model | On your own server the provider has less control; in a managed plan they also run backups, patching and uptime | Is hosting in the contract, and with what server and backup policy? |
| Change allowance | A monthly cap on small changes is effort the provider must reserve | How many hours of small changes a month, and does unused time roll over? |
Budget the AMC apart from hosting; the ERPNext hosting cost guide covers that layer. To price support with implementation for your scope, estimate your price.
Skimmable summary: users, custom code, response-time SLA, upgrade cadence and whether hosting is bundled decide the AMC; budget it apart from hosting.
What does an ERPNext AMC include?
Bug fixes, small changes, version and security updates, user support within agreed response times, and often periodic health checks. Anything larger, such as a new module, a major integration or a big customisation, is usually quoted as a separate project. The line between "covered" and "extra" is where contracts go wrong, so it must be written down.
A well-scoped AMC covers:
- Bug fixes in the delivered system.
- Small changes: fields, reports and tweaks, within a monthly effort cap.
- Version upgrades: ERPNext and app updates on a tested schedule.
- Security updates, applied promptly.
- User support with agreed response and resolution times.
- Health checks: backups, performance and error monitoring.
Usually outside the AMC: new modules, major custom apps and large integrations. Ask for the contract to name both lists.
Skimmable summary: bug fixes, small changes, upgrades, security updates, user support and health checks are in; new modules and big integrations are separate projects.
How is ERPNext support sold?
Three ways: a fixed monthly retainer, ticket or hour packs, or a fully managed plan that bundles support with hosting and monitoring. A retainer gives a predictable cost and priority. Hour packs suit low, irregular needs. A managed plan suits teams that want one party accountable for uptime and support together.
| Model | How it works | Fits |
|---|---|---|
| Retainer (AMC) | Fixed monthly or annual fee, defined scope and SLA | Steady support needs, predictable cost |
| Ticket or hour packs | Buy blocks of hours, use as needed | Low, irregular demand |
| Fully managed | Support, hosting and monitoring in one | Teams wanting one accountable provider |
MithTech's support and AMC covers the support layer, and managed hosting adds the servers: monitored, patched and backed up on infrastructure you own. The right model depends on how critical ERPNext is to your day and how much capacity you have in house.
Skimmable summary: a retainer, hour packs, or a managed plan; choose by how critical the system is and what your team can handle.
Do you actually need an ERPNext AMC?
It is optional, because the software is open source, but a business-critical ERPNext with nobody on call is a real operational risk. A broken integration, a failed upgrade or a change in a GST return format can stall operations. For a system that runs your accounts and stock, that downtime usually costs more than the contract.
You can skip a formal AMC if you have a capable in-house Frappe developer who maintains the system, applies updates and runs upgrades. Most SMEs do not, so a support contract, even a small one, is cheaper than the risk. Size it to how critical ERPNext is to daily work; do not buy a premium SLA you will never use.
Skimmable summary: optional, but a business-critical system without support risks costly downtime; skip it only with an in-house Frappe developer.
How do you choose an ERPNext support provider?
On written scope, response-time SLAs, upgrade policy and data-ownership terms, not on the lowest quote. The best signal is how clearly a provider defines what is covered, how fast they respond, and how you leave. Because ERPNext is open source, a good provider gives you full backups on request and never holds your system hostage.
Ask: What is covered and what is billed extra? What are the response and resolution times? Who runs version upgrades, and how often? Can I export my full database and files at any time? A provider who answers these crisply has run real support before. For broader criteria, see how to choose an ERPNext implementer.
Skimmable summary: choose on written scope, SLAs, upgrade policy and export rights; crisp answers on what is covered and how you leave are the signal.
Frequently asked questions
+How much does ERPNext annual support cost in India?
It scales with users, custom code, response-time SLA and upgrade cadence. A lightly customised system on business-hours support sits at the lower end; a multi-company, heavily customised system with priority response sits higher. Hosting is a separate line, set by server size, provider and who runs it. Neither includes a licence fee: ERPNext is GPL-3.0 with no per-user charge.
+Is ERPNext AMC separate from hosting?
Yes. Hosting is the infrastructure: the server, backups and uptime. The AMC is the support and maintenance on top: fixes, small changes, upgrades and user help. Some providers bundle both into one managed plan, which gives one accountable party, but they are separate cost lines and you should see both spelled out.
+What should an ERPNext support contract cover?
Bug fixes, small changes within an effort cap, version and security updates, user support with agreed response times, and periodic health checks. It should also say what is not covered (new modules, major integrations, large customisations, which are quoted as projects). The out-of-scope list matters as much as the in-scope one.
+Can I run ERPNext without any AMC?
Yes, since ERPNext is open source, but it is only wise with an in-house Frappe developer to maintain it. With neither an AMC nor in-house capacity, a failed upgrade, broken integration or compliance change can stall operations with nobody to call. For a business-critical system, a small support contract is usually cheaper than the downtime.
+Can I change my ERPNext support provider later?
Yes. You own the code and the data, so you can switch providers without losing the system. A good provider hands over full database and file backups on request and documents your setup so another team can take over. Confirm these export rights in the contract before you sign.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 9 July 2026
Worked with us? Leave a Google review