Once a Sri Lankan SME decides it needs an ERP (we made the case for why ERP is the right call in 2025 separately), the question becomes which one. The market presents this as a complicated technical decision — it isn’t. The four real options most local businesses end up shortlisting are SAP Business One, Microsoft Dynamics 365, ERPNext, and the “upgraded” Tally / Zoho path. Each is right for a specific kind of business. Picking based on the demo rather than the fit is the single most expensive mistake we see in this market.
The four real contenders
SAP Business One
Enterprise-grade, well-localised through regional partners, excellent for multi-entity groups with complex consolidation needs. Total cost of ownership for a 50-user deployment typically lands between LKR 15M and LKR 30M in year one. Right for groups in the LKR 5B+ turnover range that need IFRS-grade financial reporting out of the box. Overkill, and often a budget disaster, below that.
Microsoft Dynamics 365
Comparable to SAP B1 in price and capability, with a stronger cloud-native story and tighter Microsoft 365 integration. The local consultant pool is thinner than SAP’s but growing. Best fit for businesses already deep in the Microsoft ecosystem — or with international parent companies that mandate it.
ERPNext
Open-source, no licence cost, very flexible. The sweet spot for Sri Lankan SMEs with turnover between LKR 200M and LKR 5B and teams between 20 and 250. Localisation for VAT, WHT, SSCL, APIT, EPF/ETF is mature. Implementations typically run LKR 3M to LKR 12M depending on scope — a fraction of SAP or Dynamics for businesses in this range.
Upgraded Tally / Zoho Books
Not really ERPs — they’re accounting platforms with bolt-on modules. Fine for businesses with simple single-location operations and turnover below LKR 200M. If you have multiple warehouses, manufacturing, or multi-currency, you will outgrow them and need to migrate again. Worth knowing upfront.
The four questions that actually decide it
Before any vendor demo, write down honest answers to these:
- What’s your turnover band and growth trajectory? Pick a system that comfortably fits where you’ll be in three years, not just today.
- How many distinct workflows do you actually run? A single-location retail shop and a multi-factory apparel exporter have nothing in common operationally. The system needs to match the second one’s complexity, not the first’s.
- What’s your IT maturity? If you don’t have an internal IT lead, an open-source platform like ERPNext requires a long-term implementation partner. SAP and Dynamics force partner reliance by design.
- What can the business actually absorb in change this year? ERP go-lives fail when the team can’t keep up, not when the software is wrong. Phased rollouts always outperform big-bang ones in our experience.
Three mistakes we see repeatedly in Sri Lanka
- Buying based on the demo. Every vendor demo shows a clean dataset and pre-built workflows. Your business isn’t clean. Insist on a proof-of-concept using your actual data and your three most awkward processes before signing.
- Skipping the pilot phase. Going live across all departments at once is the most common cause of implementation failure we see. A four-week pilot on one business unit catches 80% of issues at 10% of the disruption.
- Underestimating the change management. The software is the easy part. Getting the warehouse team to scan instead of write, the finance team to post instead of journal, the sales team to log instead of remember — that’s where projects succeed or fail.
A related decision that comes up early in this conversation is whether to buy a standard platform or build something custom on top. We walked through that question in choosing between off-the-shelf and custom software.
If you’d like a candid view on which of these is actually right for your business, we’re happy to walk through your situation. We implement all four platforms and have no preference — we just want you on the one that fits. Get in touch when you’d like to talk.