February 22, 2026
ERP for medium-sized businesses in Ukraine: how to choose and not regret it
There is a simple principle described by Eliyahu Goldratt in his book The Goal: a system can only move as fast as its bottleneck. For most medium-sized businesses, this bottleneck is information—or rather, the lack of it at the critical moment. A CEO does not know the actual inventory balance. A financier calculates profit with a one-week delay. A manager promises a client delivery dates that production simply cannot meet. No one in the company sees the big picture because every department operates within its own siloed spreadsheet.
An ERP system is the solution to eliminating this bottleneck. It connects all processes—finance, inventory, production, sales, HR, and procurement—into a single, unified stream. When implemented correctly, it finally allows a company to make decisions based on real-time data.
What is an ERP and How Does It Differ from CRM and Accounting Software?
An ERP (Enterprise Resource Planning) system is designed to manage a company’s core business processes. However, behind this dry definition lies a very concrete concept: a centralized database where all departments view the exact same reality in real time.
The moment the warehouse receives a shipment of goods, the finance department instantly sees the change in assets. The moment a manager closes a sale, production sees a new task, and accounting tracks the cash flow. There is no manual data transfer between systems, and no need to double-check with neighboring departments.
When discussing the architectural layers of a typical ERP system, it classically consists of three: operational (daily transactions: sales, inventory, production), tactical (planning and control: budgets, KPIs, reporting), and strategic (analytics for managerial decisions). It is this exact vertical structure that distinguishes an ERP from simple accounting programs, which only operate at the operational level.
ERP vs. CRM vs. BAS
These three acronyms are frequently confused or used interchangeably, yet they address fundamentally different business challenges.
| System | What closes | Typical user |
|---|---|---|
| CRM | Customer relationship management: leads, deals, sales funnel, communication | Sales and Marketing Department |
| BAS | Accounting and tax accounting, payroll, primary documents | Accounting |
| ERP system | All enterprise resources in a single system: finances, warehouse, production, supply, HR, sales | The entire business from the operations manager to the manager |
So, what exactly is the difference between ERP and CRM? Essentially, it is the difference between a part and the whole. A CRM manages customer relationships, whereas an ERP manages the entire enterprise, and a CRM can be just one of the modules within it. BAS (formerly 1C) is primarily a business accounting system tailored to regulatory requirements: calculating VAT correctly, logging transactions, and preparing reports for the tax authorities. An ERP goes far beyond mere accounting: it helps plan production, control inventory, and analyze profitability across each specific product or client.
When a Business Truly Needs an ERP
The need for an ERP system typically builds up over time. Here are the most common warning signs that usually prompt companies to seriously consider implementation:
- Data from different departments does not match: The sales department shows one revenue figure, the finance team reports another, and the owner sees a third.
- Reporting is done manually: To generate a managerial P&L statement, someone has to gather Excel files from five different people and spend hours consolidating them.
- The warehouse feels like a black hole: Inventory levels are just rough estimates, and stock discrepancies are only discovered once a quarter during physical inventory counts.
- Production plans are disconnected from procurement: Materials are either over-purchased just to be safe, or they run out at the exact moment they are needed most.
- Scaling has stalled: The company wants to launch a new business line or open a new location, but the current day-to-day operations are already on the verge of breaking.
- The headcount has surpassed 50 employees: Day-to-day operations are starting to consume more time than strategic planning.
If at least three of these points sound familiar, the company has already outgrown its current setup and is ready for an ERP implementation. In Ukraine, however, there are specific nuances to consider when choosing a solution.
The ERP Market in Ukraine in 2026: What Has Changed
Prior to 2022, the ERP market in Ukraine was quite predictable: most mid-sized companies either stuck with BAS or approached international platforms with caution due to high costs and complexity. Today, the picture is completely different.
Moving Away from 1C: What Are the Alternatives?
Following February 24, 2022, the majority of Ukrainian companies using 1C products developed by Russian entities faced a straightforward choice: either find a 1C alternative or stay on a system that is no longer updated or supported, while carrying significant reputational risk. Some companies were forced to make this move in an emergency rush, while others began preparing before it became critical.
Today, the main alternatives to 1C in Ukraine fall into a few clear categories:
-
BAS (Business Automation Software): A localized system built on a familiar framework but managed by domestic developers. For companies that prioritize traditional workflow logic and local support, this offers the least painful transition.
-
International ERP Platforms (SAP, Microsoft Dynamics, Odoo): These options come with greater functionality and a larger budget, but they offer significantly broader capabilities for scaling.
-
Custom Solutions: Tailor-made development built from scratch for a specific business when no off-the-shelf software meets all its unique needs.
An important nuance here: replacing 1C is not always a direct, like-for-like migration. Many companies seized the moment to rethink their entire system architecture, choosing to upgrade immediately to a full-scale ERP rather than settling for a simple accounting program. This is precisely why ERP implementation in Ukraine has accelerated significantly over the past two years.
Cloud vs. On-Premise ERPs
Another critical choice that has become even more urgent since 2022 is where the data and servers are physically located.
| Cloud ERP | Local ERP (on-premise) | |
|---|---|---|
| Startup cost | Lower (subscription) | Premium (license + server) |
| Cost for 3–5 years | May be higher due to subscription | Lower with long-term use |
| Data security | Depends on the provider | Full control |
| Renewal | Automatic | Manual, resource-intensive |
| Accessibility | From anywhere in the world | Requires access to a local network or VPN |
| Suitable for | Businesses that are growing or have multiple locations | Manufacturing enterprises with rigid |
In wartime conditions, cloud solutions have gained an additional compelling argument: they are entirely independent of a physical office or local servers. If a business relocates, distributes its operations across multiple cities, or has part of its team working from abroad, a cloud ERP system continues to operate seamlessly without any additional setup.
Top ERP Solutions for the Ukrainian Market
Choosing an ERP solution is always a balance between functionality, cost, and how well the system aligns with the actual processes of a specific business. Below is an honest overview of the five options most frequently considered by Ukrainian mid-sized companies in 2026.
SAP Business One
SAP is arguably the most recognizable brand in the ERP world. Business One is their version tailored for mid-sized businesses; while streamlined compared to their flagship SAP S/4HANA, it remains a fully-fledged, enterprise-grade ERP system.
- Best suited for: Manufacturing and distribution companies with a turnover starting from $5 million that are ready to invest in a serious implementation process.
- Pros: Deep functionality within a unified system; an extensive network of integration partners; a strong position in the international business environment.
- Cons: High cost of licenses and implementation; the timeline from project kickoff to go-live typically takes 6 to 12 months.
Microsoft Dynamics 365
A cloud-based ecosystem where ERP and CRM operate as separate yet fully integrated modules. For companies already utilizing the Microsoft 365 environment, integration is practically seamless.
- Best suited for: Service companies, distributors, and retail businesses where data analytics takes priority over heavy manufacturing planning.
- Pros: Flexible modular architecture; Business Central serves as a more affordable version tailored for smaller companies.
- Cons: Adaptation to Ukrainian legislation requires additional development work from the implementation partner; the ongoing subscription model can become more costly in the long run.
Odoo (Open-Source)
An open-source ERP system with a lower barrier to entry compared to SAP or Microsoft, offering a wide selection of modules ranging from accounting to e-commerce.
- Best suited for: Companies that want flexibility without a massive budget and are willing to invest time into system configuration.
- Pros: Open-source code; an active community of Ukrainian implementation partners; lower licensing costs.
- Cons: The quality of implementation depends heavily on the chosen partner; full-scale functionality is available only in the paid Enterprise version.
BAS ERP (Ukrainian Development)
A platform developed by the “Center of Innovation Technologies,” offering the least disruptive transition for those who previously used 1C, along with full compliance with Ukrainian legislation.
- Best suited for: Manufacturing and trading enterprises that prioritize local support and familiar workflow logic. It serves as the optimal 1C alternative without requiring drastic operational changes.
- Pros: Full compliance with Ukrainian legislation; an extensive network of integration partners; lower overall cost.
- Cons: Less flexible customization; weaker capabilities for international reporting standards.
Custom ERP by IWIS
Sometimes a company’s business model is so specific—featuring unique manufacturing logic, non-standard pricing schemes, or a complex multi-segment structure—that trying to force a turnkey ERP system onto these processes means either rewriting the system or rewriting the business. Neither option is appealing.
This is exactly where IWIS – Development & Business Automation steps in. They build custom ERP solutions from scratch, tailored to a specific process architecture, leaving out redundant modules without compromising on the functionality the business actually needs.
- Best suited for: Companies with complex or non-standard processes where excessive customization of an out-of-the-box solution ultimately costs more than full-scale custom development.
- Pros: The system is built around actual business processes, offering full control over the architecture and product development.
- Cons: Longer time to market; requires a high-quality audit of business processes before development begins.
ERP Selection Criteria for Your Business
Choosing an ERP system is a long-term commitment that will stay with the company for at least 5–7 years. Here are several key criteria worth evaluating before signing any contract.
Company Size and Industry
Different ERP solutions are engineered for specific business scales and types. Attempting to deploy a heavy enterprise-grade solution for a company of 30 people is just as futile as expecting a lightweight platform to handle complex discrete manufacturing.
The general selection logic based on company size is as follows:
| Number of employees | Recommended direction |
|---|---|
| 20-50 | BAS ERP, Odoo Community, or custom solution |
| 50-200 | Odoo Enterprise, BAS ERP, Microsoft Dynamics 365 Business Central |
| 200+ | SAP Business One, Microsoft Dynamics 365 F&O, custom ERP |
Manufacturing, distribution, and services have fundamentally different module requirements, making industry focus a more critical criterion than company size alone. Before selecting a platform, it is essential to honestly answer one question: what are the five most complex and critical processes in the company? Then, verify precisely how each system handles them.
Budget and 3-Year TCO
Looking solely at licensing costs is one of the most common pitfalls. The real cost is revealed through the Total Cost of Ownership (TCO) over 3–5 years, which includes licenses, implementation, integrations, support, and the internal team’s time spent participating in the project.
A cloud-based solution may seem cheaper in the first year, but after three years, the subscription fees can exceed the cost of an on-premise license. And vice versa.
Integration with Existing Systems
No business starts from scratch; there is usually an existing CRM, accounting software, website, or warehouse system already in place. The main question for every vendor should be: which integrations come standard out of the box, and which require custom development? This is where hidden costs most frequently lurk. Business process automation delivers real value only when systems truly communicate with each other, rather than being linked together by manual Excel exports.
How Much ERP Implementation Costs in Ukraine
Asking “how much does an ERP cost?” is a lot like asking “how much does a renovation cost?” Naturally, everything depends on the square footage, materials, complexity, and who is doing the work.
The cost structure of an ERP implementation typically breaks down as follows:
| Expense item | What's included |
|---|---|
| Licenses / subscription | Platform access, number of users |
| Implementation | Process analysis, configuration, data migration, testing |
| Integrations | Connection to CRM, website, warehouse, other systems |
| Teaching | Team onboarding, writing instructions |
| Support and development | Updates, improvements, technical support |
Based on the 2026 licensing guidelines:
- SAP Business One: cloud subscription from $95 to $250 per user per month, or a one-time license from $1,350 to $3,500 per user plus annual maintenance of 18-20% of the cost of the licenses.
- Odoo Enterprise: from $31 per user per month when paid annually (Standard plan). Custom plan with advanced features – from $47 per month.
- Microsoft Dynamics 365 Business Central. Public prices start at $70 per user per month for Essentials and $100 for Premium.
The cost of the ERP implementation itself constitutes a separate budget line. Real-world implementation costs for SAP Business One vary from $8,000 for straightforward projects to over $50,000 for complex, industry-specific deployments. For Odoo, the figures are typically lower, though they still depend heavily on the number of custom updates and the volume of data migration.
For a mid-sized Ukrainian business, the total kickoff budget (licenses + implementation) usually starts at $15,000, depending on the platform and project complexity. Post-go-live support and optimization typically require an additional 15–25% of the initial implementation cost annually.
Common Pitfalls in ERP Implementation
Here is a sober fact: according to various industry estimates, 55% to 75% of ERP projects fail to meet their established goals. This happens because projects are routinely launched with the same well-documented mistakes.
-
Pitfall 1: Implementing an ERP without a process audit. If a company has chaotic logistics, an unstructured sales funnel, and no clear KPIs, an ERP will not magically fix things on its own. It simply automates what is already there. If the current state is chaos, the output will just be automated chaos.
-
Pitfall 2: Underestimating team resistance. An ERP alters how people work on a daily basis. If the team does not understand why it is necessary and does not actively participate in the implementation, they will passively sabotage the system: entering data inaccurately, bypassing workflows, and retreating back to Excel.
-
Pitfall 3: Overly broad scope at launch. The larger the scope of the initial phase, the higher the risks, the longer the cycle to go-live, and the harder it is to maintain team focus. It is far better to launch core modules quickly, secure an initial win, and scale up gradually.
-
Pitfall 4: Selecting a system based solely on license pricing. The license fee is only a fraction of the cost, and sometimes the smaller one. If a system is cheap but requires expensive customization for every workflow—or lacks local support partners—the final TCO can end up significantly higher than a “more expensive” solution backed by a robust ecosystem.
-
Pitfall 5: Ignoring data quality and lacking an internal owner. Migrating outdated, duplicated, or incorrect data into a new system means working with a dirty database from day one. Furthermore, no contractor, regardless of their expertise, can save a project if the client side lacks a dedicated owner who understands the processes, holds authority within the team, and is genuinely immersed in the implementation.
Step-by-Step Implementation Plan: From Audit to Go-Live
An ERP implementation is a manageable, structured process with distinct phases. Here is what it looks like:
-
Step 1: Business Process Audit (2–4 weeks) Core workflows are mapped out, and bottlenecks or points where information is lost or duplicated are identified.
-
Step 2: Platform and Partner Selection (2–3 weeks) Requirements are formulated based on the audit, and available solutions are compared. When choosing a partner, it is crucial to verify real case studies and domain expertise in your specific industry.
-
Step 3: Solution Design (3–6 weeks) A detailed technical specification is drafted, covering modules, integrations, user roles, and data migration strategies. This is the most critical phase for budget control, as modifications made after development kicks off are always more expensive.
-
Step 4: Configuration and Development (6–16 weeks) The system is tailored to the established requirements, custom modules are developed, and integrations with external services are executed.
-
Step 5: Testing and Training (2–4 weeks) The team tests real-world operational scenarios. Training serves as a comprehensive onboarding process.
-
Step 6: Data Migration and Go-Live Data is migrated, cleaned, and verified. It is best to schedule the launch outside of peak seasonal activity, as the initial weeks following go-live always require heightened attention.
-
Step 7: Support and Optimization The ERP must evolve alongside the business through new modules, additional integrations, and configuration reviews. All of this should be planned well in advance.
For small businesses, deploying cloud-based solutions can take anywhere from 1 to 3 months. For mid-sized enterprises, a full-scale migration to an ERP averages 6 to 12 months. Large-scale enterprise projects typically require a year or more.
Free Business Process Audit by IWIS
Choosing an ERP system without understanding your own workflows is like ordering a custom kitchen without taking measurements: it looks beautiful in the catalog, but it might simply not fit.
The IWIS team provides a free business process audit for mid-sized companies considering an ERP implementation. Based on the audit results, you will receive:
- a map of key processes with identified bottlenecks;
- a recommendation on the type of ERP solution for your size and industry;
- an approximate estimate of the budget and deadlines;
- An honest assessment of whether you need a full-fledged ERP system or if a simpler solution would suffice.
Not sure where to start? Begin with our audit—it is free and provides a clear understanding of the direction to take moving forward.
Other posts
Interesting materials for you
April 24, 2026
February 5, 2026
