Go live on ERPNext by 1 April 2027: a 20-week plan that starts this month
If you want to run your business on ERPNext from 1 April 2027, the clock has already started. Count back from that Thursday and you have 22 weeks. Take out a cutover window at the end and you are left with an ERPNext implementation timeline of 20 working weeks, starting the first Monday of November. That is enough time to do this properly. It is not enough time to spend November “evaluating” and still hit the date.

Why 1 April is the cleanest go-live date in India
Section 2(41) of the Companies Act treats the financial year as the period ending 31 March. Your auditor, your GST returns and your board all think in April to March. Start the new system on the first day of a financial year and every one of those conversations gets simpler.
Look at it from the auditor’s chair. Go live on 1 April and the whole of FY 2026-27 sits in your old system, the whole of FY 2027-28 in ERPNext. One year, one ledger. No split year with a stitched trial balance in the middle.
GST adds its own reason. Rule 46 of the CGST Rules requires a tax invoice to carry a consecutive serial number that is unique for a financial year. A new year is the natural point to start fresh invoice series in ERPNext, with no risk of clashing with numbers already billed from the old software. Your annual GST return for FY 2026-27 is also prepared from one system instead of two.
There is an ERPNext reason too. If you start at the beginning of a fiscal year, the year-end close stays in the legacy system, and your first Period Closing Voucher in ERPNext covers a full year of ERPNext data.
The 20-week ERPNext implementation timeline, phase by phase
Here is how we would lay out this ERPNext implementation timeline for a mid-sized manufacturer or distributor starting on Monday 2 November 2026. Treat the week ranges as a planning skeleton: a single-warehouse distributor will move faster than a Coimbatore foundry with job work, heat-wise traceability and three stores.
| Weeks | Dates (Mondays) | Phase | What gets finished |
|---|---|---|---|
| 1 to 3 | 2 Nov to 16 Nov | Discovery | Process walkthroughs, phase-one scope, decision owners and data owners named |
| 4 to 7 | 23 Nov to 14 Dec | Design | Company and Fiscal Year setup, chart of accounts, warehouse and item code structure, document flows signed off |
| 8 to 12 | 21 Dec to 18 Jan | Build and configuration | Masters, BOMs, workflows, print formats, GST and e-invoicing setup, first load of masters |
| 13 to 15 | 25 Jan to 8 Feb | Migration rehearsal one | Trial load of 31 December balances, reconciled to the old trial balance |
| 16 to 18 | 15 Feb to 1 Mar | UAT and rehearsal two | Users run real transactions in a test site, second load using 28 February balances |
| 19 to 20 | 8 Mar to 15 Mar | Training and go/no-go | Role-wise training, cutover runbook signed, go/no-go by 19 March |
| Cutover | 22 Mar to 1 Apr | Freeze and go-live | Master freeze, open order list, stock count on 31 March, live on 1 April |
Notice what is missing: there is no single “data migration” week. Migration runs as rehearsals, because the first load always fails somewhere. Better it fails in January against December numbers than on 2 April against real ones.
Weeks 1 to 7: discovery and design
Discovery is three weeks of sitting with the people who raise Sales Orders, issue material to the shop floor and chase payments, and writing down what actually happens. For a Tiruppur knitwear exporter, that means tracing yarn out to the knitter, fabric to the dyer and back. For a Chennai distributor, it means schemes, credit limits and returns.
Design turns that into ERPNext structure: how many Companies, which Fiscal Year records, the chart of accounts, warehouse naming, batch or serial tracking. These are expensive to reverse once transactions exist, which is why they sit in November and not in February.
Weeks 8 to 15: build, configure and rehearse
We keep customisation to what the business genuinely needs. This phase is mostly configuration: item masters, BOMs, Work Order flows, Stock Entry types, approvals and the print formats your customers will see. E-invoicing gets tested against your own GSTINs in a sandbox.
The first rehearsal uses 31 December balances, loaded in order: chart of accounts, outstanding customer and supplier invoices through the Opening Invoice Creation Tool, opening stock through Stock Reconciliation, then a Journal Entry for the remaining balances. Run a trial balance after each step. Our data migration playbook covers the cleaning work that makes this pass.
Weeks 16 to 20: UAT and training
User acceptance testing works best with real paper. Take last month’s purchase bills, delivery challans and production slips and have users enter them. If the stores team at a Pune auto-component unit cannot post a Purchase Receipt against a partial delivery without calling someone, you have found a gap, and you have found it in February.
The second rehearsal, on 28 February balances, should be boring. If it is not, the go/no-go meeting should say so honestly.
What must be decided by when
Most projects that slip do not slip on technology. They slip because a decision sat with a busy promoter for three weeks. Here is who decides what, and the latest safe date on this ERPNext implementation timeline.
- By 13 November, the promoter or CEO: phase-one scope, the internal project owner, and whether group companies come in now or later.
- By 27 November, the CFO: number of Companies, chart of accounts, cost centers and any accounting dimensions such as plant or product line.
- By 11 December, operations and plant heads: item code logic, warehouses, batch and serial rules, BOM ownership.
- By 8 January, the CFO with the auditor: opening balance method, posting date for opening entries, and invoice naming series for FY 2027-28.
- By 19 March, the steering group: go or no-go, with a written fallback.
The questions behind these decisions are in our ERP implementation readiness framework. If you cannot put a name against each line this week, fix that first. An ERPNext implementation timeline without decision owners is just a wish list with dates.
Cutover at year end: March closes in the old system
The last ten days of March look quiet on the plan and are busy everywhere else. Masters freeze around 22 March. The team lists open Sales Orders and Purchase Orders to re-enter in ERPNext. Stores plans the 31 March count, because opening stock should come from a count, not a book balance nobody has checked.
On 1 April users start transacting in ERPNext. Meanwhile accounts keeps closing FY 2026-27 in the old system: late March bills, provisions, depreciation, audit adjustments. That close often runs well into April, so day-one opening balances are provisional. Receivables, payables and stock can go in early because they come from documents and the count. Ledger balances get trued up through a Journal Entry once the auditor signs the 31 March trial balance. Our 8-step cutover playbook covers that sequence and the cutover log for invoices that land in the gap.
One practical point: agree with your auditor in January whether opening entries carry a 31 March or 1 April posting date. Five minutes in January, a headache in April.
What slips if your ERPNext implementation timeline starts in January
A January start gives you about 11 working weeks instead of 20. Something has to give, and it is usually the parts that protect you.
| Area | Start in November | Start in January |
|---|---|---|
| Migration rehearsals | Two, on December and February balances | One at best, often none |
| UAT | Three weeks with real transactions | A few days, during year-end pressure |
| Design decisions | Made calmly in November and December | Rushed, often revisited after go-live |
| Training | Role-wise, before the year-end rush | Squeezed into year-end weeks |
| Realistic fallback | Go live 1 April with confidence | Push to mid-year and accept a split financial year |
A mid-year go-live is not a disaster. But it means two systems for one year’s audit, opening balances at an odd date and an annual GST return built from two sources. If 1 April matters, a January start is a bet, not a plan.
Checklist: start your ERPNext implementation timeline this week
- Name one internal project owner with authority to make process decisions.
- List every legal entity and GSTIN in scope for 1 April.
- Pull the 31 October trial balance, debtor and creditor ageing and stock summary to gauge data quality.
- Book discovery workshops for the first three weeks of November.
- Size the budget with the ERPNext cost estimator so finance can approve it early.
- Tell your auditor the go-live date and ask for their opening balance preferences.
None of this needs a signed contract. All of it shortens the ERPNext implementation timeline once you start.
Is 1 April realistic for you? Bring your entity list and current software to a free 30-minute ERPNext consultation and we will tell you plainly whether a 20-week plan fits, or what to cut from phase one so it does.
Frequently asked questions
How long does an ERPNext implementation take in India?
Your ERPNext implementation timeline depends on scope more than company size. A trading company using accounts, buying, selling and stock can be live in a few weeks. A manufacturer with production planning, job work and several warehouses usually needs a few months. The ERPNext implementation timeline in this article assumes a mid-sized manufacturer or distributor aiming for 1 April.
Can we go live on ERPNext in the middle of a financial year?
Yes. ERPNext accepts opening balances on any date. The trade-off is one financial year split across two systems, which adds work at audit and for the annual GST return.
How do we load opening stock into ERPNext?
Through Stock Reconciliation, with quantity and valuation rate per item and warehouse. Base it on a physical count at year end, not the old system’s book stock, and reconcile the total to the trial balance.
What is the Opening Invoice Creation Tool used for?
It brings unpaid and part-paid customer and supplier invoices into ERPNext with due dates, so ageing works from day one and payments can be allocated against the original bills. It does not carry item-level history.
Do we need to finish the March close before going live?
No. Users can start in ERPNext on 1 April while accounts finishes the FY 2026-27 close in the old system. Opening balances are loaded provisionally and trued up once the final 31 March trial balance is signed.
Is a December start too late for a 1 April go-live?
Not always. A December start leaves about 16 working weeks. That can work if scope is tight, decisions come fast and data is reasonably clean. Protect the second migration rehearsal above everything else.
ERPNext implementation timeline: key takeaways
From late October 2026 there are about 22 weeks to 1 April 2027, enough for a 20-week ERPNext implementation timeline plus a cutover window if work starts in early November. Lock Companies, chart of accounts and item codes by December, run at least two migration rehearsals, and let March close in the old system while ERPNext starts the new year on provisional opening balances trued up after audit. The Frappe documentation on opening and closing in ERPNext sets out the recommended loading order.