MeshCo started on Tally in 2009 with a single legal entity and ₹4cr turnover. Today it has three manufacturing plants in Maharashtra and Gujarat, two regional warehouses, a small Bengaluru R&D centre, 215 employees, and ₹85cr revenue across two legal entities.
The accounting team runs five Tally companies in parallel (one per location). Inventory across locations is reconciled via a 14-tab Excel master. GST returns require pulling reports from all five Tally instances + adjustments via the Excel master. Month-end close: 11 working days. Branch P&Ls take another week. Annual audit: 6 weeks because nothing reconciles cleanly.
The new CFO, joining last month, asks: "When did we cross the line where Tally stopped being enough?" Internal estimate: 2019. They've been running on duct tape for six years.
- Tally is excellent at what it does — single-entity book-keeping, GST returns, basic inventory. It's the default for ~80% of Indian SMEs and rightly so.
- Tally starts breaking when you cross 2 of these: multi-entity / multi-branch books, >₹50cr turnover, >100 employees, real-time inter-branch inventory, multi-currency transactions, project-cost or job-cost accounting, multi-level approval workflows, integrations with non-Tally systems (CRM, WMS, MES, Magento, Shopify).
- The realistic alternatives at SME-to-mid-market scale: Microsoft Dynamics 365 Business Central (₹6,000-8,500/user/month, cloud, ~3-5 month implementation), SAP Business One (₹4,500-7,000/user/month, on-prem or cloud, ~4-6 month implementation), Zoho One / Books with custom workflows (low cost, lower depth).
- Migration is more about data discipline + process design than software. The actual software install is 6-8 weeks; the chart of accounts, master data cleanup, and user training is the other 12-18 weeks.
- The "right time" to migrate is usually 12-18 months before you absolutely have to. Past the breaking point, you're migrating under stress with a broken team.
The seven signs you've outgrown Tally
- Sign 1: You run multiple Tally "companies" for what should be one legal entity (one per branch, one for stocks, one for projects). You spend more time consolidating than recording.
- Sign 2: Inventory reconciliation lives in Excel. Stock-in at one warehouse and stock-out at another don't match in real time. Year-end physical count vs system always shows variance ≥ 2%.
- Sign 3: Branch P&Ls take days of manual work. Cost centres aren't a primary dimension in Tally — they're a workaround. Multi-dimensional analysis (by branch, by product, by customer segment) is impossible without exports + pivot tables.
- Sign 4: Approvals run on WhatsApp. Tally doesn't have built-in approval workflows. Purchase order approvals, payment release approvals, journal entry approvals — all flow over chat. Compliance audit nightmare.
- Sign 5: Integration is glue and tape. You have a separate CRM (Salesforce / Zoho), separate inventory system (Unicommerce / EasyEcom), separate payroll (greytHR / Keka), separate banking (multiple banks). They don't talk to each other; data flows via CSV exports + monthly imports.
- Sign 6: Forecasting is by gut. No rolling forecast capability. No what-if scenario modelling. Budget vs actual is a quarterly retrospective, not a forward-looking instrument.
- Sign 7: Your auditor is increasingly grumpy. Statutory audit takes 6+ weeks. Internal controls testing fails because there's no audit trail on adjustments. ITGC review flags concerns about who can change what.
The three realistic options
Stay on Tally
+ TallyPrime + 3rd-party glue
Upgrade to TallyPrime, buy add-on modules (Tally.NET sync, voucher approval, branch consolidation tools). Keep the Excel master more disciplined. Buys 12-24 more months. Real cost: lost CFO sleep + audit fees. Works if you'll exit / restructure soon.
D365 Business Central
Cloud, sweet spot
Microsoft's mid-market ERP. Cloud-native, monthly subscription. Strong on financials, inventory, project accounting, approvals. Native Office 365 integration. Indian localisation pack for GST/TDS. The default modern choice for ₹50-500cr Indian businesses.
SAP Business One
On-prem or cloud
SAP's mid-market product. Strong in manufacturing-heavy / multi-currency / complex supply chains. Stronger production-planning module than BC. Slightly cheaper per-user license. Implementation partner ecosystem in India is mature.
The actual cost — be realistic
Implementation cost for a mid-market ERP project varies wildly based on scope, customisation, integrations. Realistic ranges for ₹50-300cr businesses with 30-80 users:
- Licenses: Essentials ₹6,500/user/month, Premium ₹9,300/user/month. Team Member ₹600/user/month (read-only/limited write). For 30 users mix: ~₹3.5-5L/month = ₹42-60L/year.
- Implementation (one-time): ₹15-40L for a clean single-entity rollout. ₹40-90L for multi-entity, multi-currency, with integrations.
- Customisation: ₹500-1,200/hr for Indian implementation partners; ₹1,500-2,500/hr for boutique custom dev. Typical SME spend: 100-300 hours total over the rollout.
- 3-year TCO (30 users): ~₹2.0-2.8cr including licenses + implementation + customisation + training. About 6-8x what 5 Tally licenses + Excel cost.
- SAP Business One alternative: similar 3-year TCO, slightly lower licensing, similar implementation cost.
- Tally + add-ons alternative: ~₹15-25L/year ongoing if you push it hard. Saves money but doesn't solve the structural problems.
The 4-6 month migration sequence
Document current state. List all Tally companies, Excel sheets, integrations. Define target Chart of Accounts. Decide which modules (Financials, Sales, Purchase, Inventory, Project, Service). Pick implementation partner. Sign SOW.
Implementation partner sets up entities, COA, dimensions (departments / branches / projects), users + roles. Master data migration: customers, vendors, items, BOMs, FA register. This is the slowest, most painful phase — Tally's clean master data rarely exists; you'll discover years of duplicates and typos.
Connect bank feeds, CRM, payroll, GST portal. Build custom reports the business actually uses (vs default). Approval workflows. Mobile app rollout.
Key users test their workflows. Finance, sales, purchase, store-in-charge all sign off. Training: typically 2-3 sessions per user role. Refusing to invest 30+ hours of training per finance person is the #1 cause of post-go-live chaos.
Pick a clean date (typically 1st of a quarter). Cutover all opening balances + open items (orders, POs, GRN, invoices). Run Tally and new ERP in parallel for 30 days. Reconcile daily. Cut Tally off on day 31.
Real-world edge cases surface. Implementation partner stays on retainer for fixes. Report library expands. By end of stabilisation, month-end close should drop from 11 days to 4-5 days. By end of year 1, to 2-3 days.
The CFO (or finance head) cannot be a passive observer in an ERP migration. They must own: the chart of accounts design, master data cleanup, the parallel-run reconciliation, sign-off on key reports. Outsourcing all of this to the implementation partner is the most common (and most expensive) mistake. The partner builds what they were told to build; if the brief is wrong, the system is wrong.
What changes the day after go-live (when done right)
- Single source of truth. No more "which Tally has the right number for August?"
- Branch P&L in 1 click, not 3 days.
- Inventory across locations in real time; no more reconciliation Excel.
- Approval workflow audit trail; every approval is a system event with timestamp.
- Integrations native: bank feeds, GST upload, e-way bills, e-invoices — all in-system.
- Forecasting + scenario modelling available without rebuilding the data model.
- Auditor visit drops from 6 weeks to 2-3 weeks by year 2 of ERP.
The funny historical wrinkle
Tally is uniquely Indian. Created in 1986 in Bengaluru by Bharat Goenka, it's been the default Indian SME accounting software for nearly four decades. The product's strength — staying focused on simple bookkeeping + GST + statutory compliance — is also its boundary. Indian businesses growing past the SME boundary historically had to jump to SAP / Oracle (heavy, enterprise-grade) — there was no middle ground. The arrival of D365 Business Central + SAP Business One + Zoho around 2015-2020 finally created a real "mid-market ERP" tier in India. The Tally-to-BC jump is the standard scale-up move for ₹50-500cr businesses today.
Quick answers
You can but you shouldn't. Two systems = two truths = endless reconciliation. Use parallel run for 30 days to validate; then cut Tally. Keep Tally read-only for historical reference for 1-2 years for audit purposes, then archive.
NetSuite is excellent — strong multi-entity, multi-currency, cloud-native. Pricing typically a bit higher than BC for similar functionality. Best for India-HQ businesses with significant overseas operations. Fewer Indian implementation partners than BC / SAP B1.
Zoho Books + Zoho One (the full suite) covers ~70% of BC's functionality at ~25% of the cost. Strong for service businesses, small product businesses. Weak on complex manufacturing, multi-warehouse inventory at scale, deep approval workflows. Good middle option if BC feels overkill.
S/4HANA is enterprise-grade SAP. Typical TCO 5-10x of BC. Right for ₹500cr+ businesses with complex global operations. Wrong for an ₹85cr Indian business; the gap between your needs and S/4HANA is too wide.
Look for: Microsoft / SAP-certified, 5+ live customer references in your industry / scale, India-resident team, fixed-price implementation option (avoid "T&M with no cap"), willingness to hand over admin rights at end (don't get locked in). Talk to their 3 most recent customers before signing.
When you might want help
Three situations: (1) Assessing whether you've outgrown Tally — independent diagnostic, 2-week engagement, you keep the report. (2) ERP vendor selection — RFP, reference checks, fixed-fee scoping. (3) Implementation partner selection / oversight — we don't implement; we make sure the partner you hire delivers.
Wondering if it's time?
Independent ERP assessment + vendor RFP + implementation oversight. Fixed scope. No software-product affiliations.
"MeshCo" and the pricing ranges are composite illustrations. Actual ERP implementation cost depends heavily on scope, customisation, and choice of partner.