You can move an MSME from Excel and WhatsApp to an ERP in about 30 days, as long as you move one process at a time instead of everything at once. Week 1: choose one process, name an internal owner and clean your master data (customers, items, staff). Week 2: configure the ERP and pilot it with one team. Week 3: go live for that process while the old sheet runs in parallel. Week 4: expand to the rest of the team and formally retire the old sheet or WhatsApp group. Throughout, your accountant keeps using Tally for the books; the ERP runs operations.
From what we’ve seen setting up Stagewise ERP for businesses, switch-overs rarely struggle because of software. They struggle because the scope was too big, the data was messy, nobody inside the company owned the change, or go-live landed in the middle of Diwali dispatches. This plan is built around those four problems, and it applies whichever ERP you choose.
Before day 1: three decisions
1. Scope: one stage, not the whole business
Pick the one process that hurts most and where improvement will be visible quickly. For many businesses that’s leads and quotations (enquiries slipping, quotes slow) or attendance and payroll (month-end chaos). Leave the rest for month two. It helps to think of the business as stages: leads, quotes, execution, service, people. You processify one stage, then the next.
2. Owner: one person inside the company
Not the business owner, and not the software vendor. Choose a trusted manager or senior executive who understands the process, is respected by the team and can give two to three hours a day for the next month. They make the small decisions (field names, statuses, who sees what) so those don’t all queue up for you.
3. Timing: avoid your busiest weeks
Don’t go live in Diwali month, in your peak dispatch season, or in the last two weeks of March when accounts is closing the year. Choose a month that is quiet for your industry and count back 30 days from that go-live date.
Week 1 (days 1–7): scope, owner and clean masters
Master data is your list of customers, suppliers, items and staff. Every transaction in an ERP points to it, so if it goes in dirty, every report afterwards is wrong. This is the most boring week of the project and the most important.
Assign each list to the person who knows it best (accounts for parties, stores for items, HR or admin for staff), set a deadline of day 5, and have the internal owner review everything on days 6 and 7.
Master-data cleanup checklist
Customers and suppliers
- One list, exported from Tally and merged with the sales team’s Excel sheets
- Duplicates merged (“Patel Engg.”, “Patel Engineering” and “PATEL ENGINEERING WORKS” become one)
- GSTIN checked for every registered party
- Billing and shipping addresses kept separate
- A contact person and mobile number for each
- Parties with no business in two years marked inactive, not imported
Items and products
- One code per item, with a consistent naming pattern (for example type–size–grade)
- One unit of measure per item (kg, nos or metre, not a mix)
- HSN code and GST rate for each item
- Current selling and purchase rates
- Obsolete items removed
Staff
- Employee list with department, designation and reporting manager
- Mobile number (for the app) and date of joining
- Salary structure, shift and weekly off
- Opening leave balances, loans and advances
Also in week 1, write down on one page how the chosen process works today and how you want it to work. If you don’t have this yet, our guide to writing SOPs shows a simple format.
Week 2 (days 8–14): configure and pilot with one team
- Import the clean master data.
- Configure only what the chosen process needs: stages, statuses, approval rules, document formats and user roles. Resist adding “nice to have” fields.
- Pick a pilot team of three to six people, including at least one sceptic. If the sceptic is convinced, the rest will follow.
- Run real work through the system for three or four days: real enquiries, real tasks, real attendance. The old method continues as usual alongside.
- Keep every problem in one list and fix configuration issues the same day where possible.
Training: keep sessions to 30–45 minutes, on the phones staff will actually use. Train in Gujarati or Hindi if that’s what the team speaks. Record a two-minute screen video for each common action, in that language, and share it in the team group. A one-page cheat sheet with screenshots beats a long manual.
Week 3 (days 15–21): go live for one process, with a parallel run
Going live means one thing: from this date, the ERP is the source of truth for this process. The old sheet becomes a backup, not the master.
Rules for the parallel run:
- New work is entered in the ERP first. The sheet is updated only as a backup, and only this week.
- At the end of each day, the internal owner spends ten minutes comparing the ERP with the sheet. Mismatches are corrected in the ERP.
- The parallel run has a fixed end date, one to two weeks at most. Open-ended parallel runs mean people do double work indefinitely and slowly drift back to Excel.
- Questions go to the internal owner, not to you.
As the business owner, you have one job this week: ask for information from the ERP, not from the sheet or WhatsApp. If you say “just send me the Excel”, the team will keep the Excel alive.
Week 4 (days 22–30): expand and retire the old way
- Bring the rest of the team onto the same process.
- Stop updating the old sheet. Make it read-only and archive it with the date in the file name.
- Change the old WhatsApp group so only admins can post, and pin a message pointing people to the ERP. Keep WhatsApp for conversation; stop using it as the record.
- Hold a short review: what worked, what’s still clumsy, which process goes next.
- Pick the next stage and start its week 1.
The 30-day checklist
| Day | Task | Owner | Done |
|---|---|---|---|
| 1 | Choose the process and the go-live date | Business owner | ☐ |
| 1 | Name the internal owner | Business owner | ☐ |
| 2 | Write today’s and the desired process on one page | Internal owner | ☐ |
| 2–5 | Clean customer, supplier, item and staff masters | Accounts, stores, HR | ☐ |
| 6–7 | Review and approve master data | Internal owner | ☐ |
| 8–9 | Import masters and configure the process | Internal owner with vendor | ☐ |
| 10 | Train the pilot team in their language | Internal owner | ☐ |
| 10–14 | Pilot with real work and log every issue | Pilot team | ☐ |
| 14 | Fix issues and confirm go-live | Internal owner | ☐ |
| 15 | Go live: the ERP becomes the source of truth | Everyone in the process | ☐ |
| 15–21 | Daily ten-minute ERP-versus-sheet check | Internal owner | ☐ |
| 21 | End the parallel run | Internal owner | ☐ |
| 22–25 | Train and onboard the rest of the team | Internal owner | ☐ |
| 26 | Archive the old sheet; restrict the old WhatsApp group | Internal owner | ☐ |
| 28–30 | Review and choose the next stage | Business owner and internal owner | ☐ |
Keep Tally for the books
You don’t have to choose between an ERP and Tally. A common split looks like this:
| Runs in the ERP (operations) | Stays in Tally (accounts) |
|---|---|
| Leads, follow-ups and quotations | Ledgers and vouchers |
| Sales and purchase orders, delivery challans | Bank reconciliation |
| Tasks, service tickets, AMCs and projects | Final accounts and balance sheet |
| Attendance, payroll and field staff | Whatever your CA prefers to handle in Tally |
Decide upfront which system raises the invoice and how it reaches the books, and write it down, so accounts isn’t entering the same bill twice. Bring your accountant into week 1 rather than informing them after go-live.
Handling resistance from senior staff
Expect it, especially from long-serving staff whose value has always been “knowing everything”. What helps:
- Involve them in week 1. Let them design the statuses and checklists for their area. People defend what they helped build.
- Show them what they’ll stop doing: fewer calls, no month-end attendance totals, no retyping.
- Make them the trainers for their own team.
- Don’t use the ERP to catch people out in the first month. If the first thing the system is used for is a scolding, everyone will quietly avoid entering data.
- Be patient with phones. Some excellent supervisors aren’t comfortable with apps. Pair them with a younger colleague for the first two weeks.
How Stagewise ERP onboarding works
If you choose Stagewise ERP, the plan above maps directly onto how we onboard:
- Timeline: basic configuration (company setup, adding your team and switching on core modules) typically takes one to two weeks. A full rollout, including custom workflows and data migration, usually takes four to six weeks. Your first process can be live within the first month, with the other stages following one by one.
- Tally stays: Stagewise ERP works alongside Tally, so your accountant can continue in TallyPrime. On the operations side it handles e-invoices, e-way bills, GSTR reports and profit and loss statements. See GST and accounting.
- Language: our team supports customers in English, Hindi and Gujarati, from offices in Vadodara and Ahmedabad.
- Your own server: each client runs on a dedicated, isolated server and database.
- Pricing: ₹999 per user per month, minimum 20 users, all modules included. Details are on the pricing page.
When Stagewise ERP is not the right fit
- You have fewer than 20 people. Well-run Google Sheets and WhatsApp, with the discipline in this plan, may be all you need.
- You only need accounting and GST filing. Tally does that well on its own.
- Nobody internal can give the project two to three hours a day for a month. Wait until someone can; an ERP without an internal owner rarely sticks.
- Peak season is about to start. Schedule the switch for after it.
When you’re ready, talk to us about which stage to start with. The other stages are covered in our playbook.
Written with Claude Opus 5.5, an AI model by Anthropic, and published by Stagewise Software Solutions Pvt. Ltd., Vadodara and Ahmedabad, Gujarat.
Frequently asked questions
How long does it take to switch from Excel to an ERP?
For one process, about 30 days: a week to clean master data, a week to configure and pilot, a week of go-live with a parallel run and a week to expand and retire the old sheet. A full rollout across all departments takes longer. For Stagewise ERP, basic configuration typically takes one to two weeks and a full rollout four to six weeks.
Can I keep using Tally after implementing an ERP?
Yes. Many MSMEs keep Tally for ledgers, vouchers, bank reconciliation and final accounts while the ERP runs operations such as leads, quotations, orders, tasks, service and payroll. Decide upfront which system creates invoices and how they reach the books, so nothing is entered twice. Stagewise ERP works alongside TallyPrime.
How long should the parallel run with Excel last?
One to two weeks at most, with a fixed end date. During the parallel run, new work goes into the ERP first and the sheet is only a backup. Open-ended parallel runs make people do double work and slowly drift back to Excel.
When is the best time to implement an ERP in India?
Choose a month that is quiet for your business. Avoid Diwali month, your peak dispatch season and the last two weeks of March, when accounts is closing the financial year. Count back 30 days from a calm go-live date so the pilot and parallel run don’t clash with your busiest weeks.
How do I get senior staff to accept a new ERP?
Involve them early by letting them design the statuses and checklists for their area, show them the work they will stop doing, make them trainers for their own teams and train in their language. Avoid using the system to catch people out in the first month, or they will quietly stop entering data.