Loading…
Loading…
How an ERPNext implementation runs in India, phase by phase, what moves the cost and timeline, and what to ask an implementation partner.
ERPNext is open source, so there is no software to buy and no per-user licence fee. That changes where the money goes. With ERPNext, nearly all of the cost and effort sits in the implementation: understanding how your business runs, setting the system up to match, moving your data across and getting your people to use it.
This guide walks through how an ERPNext implementation in India usually runs, what makes it take longer or cost more, and the questions worth asking before you sign with an ERPNext consultant or implementation partner. It is written for owners and managers of manufacturing and trading businesses, not for developers.
Most implementations follow the same six phases. The names change from partner to partner, but the work is the same.
Before anyone opens ERPNext, someone has to understand how work moves through your business today. That means sitting with the people in sales, purchase, stores, production, quality and accounts, and following real documents from enquiry to payment.
The walkthrough should produce a written scope: which modules are in, which processes they cover, what data comes across, which reports matter and where ERPNext will need to be extended. A partner who gives you a fixed price before this step is guessing.
Configuration is setting ERPNext up without writing code. It covers:
For GST, e-invoicing and e-way bills, current ERPNext uses the India Compliance app, which is installed alongside ERPNext.
Every business has a few processes that standard ERPNext does not handle the way they need. Small gaps are closed with custom fields, scripts and reports. Larger gaps, such as a dedicated quality module or a link to a machine or weighbridge, are built as a custom app on the Frappe framework.
The rule a good partner follows: customise through a separate app, never by editing ERPNext's own code. Core edits break when you upgrade, and they tie you to whoever made them.
Your opening data has to come across before you can go live. That usually means:
Data migration is often the most underestimated phase. Exporting is easy. Cleaning duplicate customers, inconsistent item names and stock that does not match the books takes time, and someone in your team has to decide what is right. If you are moving from Tally, our Tally to ERPNext migration guide covers this in detail.
Training works best by role and on your own data. A stores person needs to know receipts, transfers and stock entries, not the whole system. Accounts staff need to see their familiar reports in the new place.
Go-live is the day ERPNext becomes the system of record. Many businesses run their old system in parallel for a few weeks so they can compare numbers. Plan go-live for a quiet period, and make sure the partner is available that week.
The first month after go-live brings the most questions. After that, support shifts to small changes: a new report, a new print format, a new product line. Agree before you start how support works, who you call and how quickly they respond.
There is no honest single answer, because the timeline depends on scope. A single plant using standard modules, with clean masters and a team that is available, can go live in weeks. Several plants, many custom apps and years of history to migrate can take months.
What usually slows things down is not the software. It is:
A good partner gives you a timeline after the walkthrough, broken down by phase, and tells you what they need from your side to meet it.
Since there is no licence fee, ERPNext implementation cost is mostly people's time. These are the factors that push it up or down.
Accounts, stock and buying are the base for most businesses. Manufacturing, quality, subcontracting, CRM, projects and HR each add configuration, testing and training. Starting with the modules you need now and adding others later keeps the first phase smaller.
There is no per-user fee, but more users mean more roles to design, more permissions to test and more people to train. Ten users in two departments is a different job from sixty users across six.
Each extra plant, branch or legal entity adds warehouses, GST registrations, inter-company transactions and reporting. Multi-company setups need careful thought about how stock and money move between entities.
This is usually the largest variable. A few custom fields and print formats cost little. A custom app with its own forms, workflows and integrations costs more, and it also needs maintaining through upgrades.
Migrating masters and opening balances is routine. Migrating years of transaction history is not. Decide early whether you really need history inside ERPNext, or whether the old system can stay available for reference.
ERPNext can run on your own server, a cloud server or Frappe Cloud. Each has a monthly cost and a different split of who looks after backups, security and upgrades. Ongoing support is usually a separate yearly agreement.
In our earlier guide on choosing an ERP for a small manufacturer, we gave a rough estimate of Rs 3-8 lakh for a one-time ERPNext implementation at a small manufacturing company. Treat that as a rough estimate only. Your number depends on the factors above, and anyone quoting a firm price before seeing your process is guessing.
The partner matters more than the software. ERPNext set up badly is just as frustrating as any other system. These are the questions worth asking.
Be wary of anyone who promises a fixed go-live date before the walkthrough, or who says ERPNext can do everything you need without asking how you work.
Tanush Digital is a small, senior team that sets up and customises ERPNext for manufacturers across India. Across 30+ projects, we have not had a failed go-live.
At CSE India, a Korean-owned water booster pump maker in Gurugram, that meant multi-level BOMs for over 200 product variants, subcontracting, incoming quality control with inspection checklists, documents in Korean and English, five years of history brought across from Excel and training for more than 25 users. You can see how we run each phase on our ERPNext page.
ERPNext is open source, so there is no licence fee and no charge per user. You still pay for hosting, for the implementation and for ongoing support.
It depends on the modules, users, sites, customisation and data migration in scope. As a rough estimate, a small manufacturer might spend Rs 3-8 lakh on a one-time implementation, but get a quote based on a walkthrough of your own process.
A single site with standard modules and clean data can go live in weeks. Multiple sites, custom apps and large migrations take months. Ask for a phase-by-phase timeline after the process walkthrough.
Yes. Small changes use custom fields, scripts and print formats. Larger gaps are closed with custom apps on the Frappe framework, kept separate from ERPNext's core so upgrades still work.
Yes. Current versions handle GST, e-invoicing and e-way bills through the India Compliance app, which runs alongside ERPNext.
Book a walkthrough and we will map your process before we quote.
In a free 30-minute call we map your process and tell you plainly what would change, whether that is Tanush LIMS, ERPNext or something built for you. We reply within 24 hours.