The best time to go live with a new ERP is the first day of a month, ideally at the start of a quarter after your audit has closed, and away from peak production seasons, festival dispatch rushes and GST return due dates. A month start gives you one clean month of transactions on the new system, so your first month-end close is simple to check. For most Indian manufacturers, 1 April is popular but rarely the calmest choice.
Because go-live is the one moment when your old system stops and the new one starts, and anything that is already busy gets harder. A good date gives your team time to learn, makes data easy to reconcile and lets you fix problems before a deadline. A bad date puts a cut-over on top of a dispatch rush, a tax deadline or an audit.
Pothera’s ERP implementation roadmap guide treats the date as a decision to make early, not a date to be picked at the end.
Go live at the start of a month, usually on the 1st or the first working day. This gives you a full month of transactions in one system, so the month-end close, stock and ledgers can be checked against a single starting point. It also keeps opening balances simple: you load closing figures from the month that just ended.
Going live mid-month splits one month’s transactions across two systems. Reconciling them takes much longer.
Not automatically. Many companies like 1 April because the new financial year starts cleanly. But it is often a poor choice in practice:
A start-of-quarter date after the audit has closed is often calmer. Ask your CA how audit and opening balances should be handled for your case.
Avoid five periods:
| Option | Best for | Main advantage | Main risk |
| Start of a month | Most manufacturers | Clean month-end close | Avoid if a rush or tax date overlaps |
| Start of a quarter, after audit | Companies with year-end audit pressure | Calmer finance team and final opening balances | Waiting may delay benefits |
| 1 April | Companies with a calm March and an early audit | Clean financial year | Provisional balances, year-end workload |
| Mid-month | Rarely advised | None for most | Transactions split across two systems |
Work backwards from the date you want. Pothera’s guide gives these ranges for time to first go-live:
| Scenario | Time to first go-live |
| Single plant, focused scope | 4 to 5 months |
| 2 to 3 plants or warehouses | 6 to 7 months |
| Multi-entity or multi-country | 8 to 10 months |
Illustrative example (not a client case): a single-plant manufacturer starts an implementation on 1 December. At 4 to 5 months, the earliest realistic readiness is 1 April to 1 May. If the audit is still open in April, a go-live on 1 May or 1 July is safer than forcing 1 April. If testing is still incomplete, the right call is to move the date, not to skip testing.
For the full sequence of work behind these ranges, read the 8 phases of an ERP implementation.
Usually not. Most plants do not need a full stoppage. Common approaches include:
Before cut-over, make sure inventory management and production and planning management are loaded and checked against the physical count.
Pothera’s guide suggests going live with all core modules together at the first site, then rolling out quickly to other sites, with complex production planning following a few weeks later if needed.
| Approach | Best when | Watch out for |
| Big-bang | A single plant with tightly connected processes | Higher pressure on go-live day |
| Phased by module | Core modules first, production later | Running two ways of working for a while |
| Phased by site | Several plants, one at a time | Interface risks between old and new sites |
Confirm these nine points before you announce the date. They come from the go-live readiness checklist in Pothera’s guide:
If any item is missing a week before the date, move the date.
Plan four to six weeks of intensive support, called hypercare. It ends when the first month-end close is complete and users trust the reports. Do not schedule another major change, such as a new plant or a policy change, during this window.
If you are moving from Tally and Excel, read how to migrate data from Tally and Excel to a steel ERP to plan the data side of your date.
For a budget range, use the Bsquare ERP cost estimator.
Share your project scope and calendar, and we will help you plan a realistic date. Read Pothera’s full ERP implementation roadmap guide, then book a free implementation consultation to get a draft plan for your plant. You can also visit Pothera ERP or Bsquare Solutions.