Since 2022, moving off 1C has stopped being a question of “whether” — for many Ukrainian companies it's a question of “when.” 1C is software of Russian origin, and using it carries reputational, legal and security risks. Microsoft's Business Central is one of the most common replacements. Let's compare honestly, without the marketing.
The main difference isn't in features
Both systems cover accounting, warehouse, sales and finance. The key difference is elsewhere: in Ukraine 1C has effectively been left without official support or a future, while Business Central is a global Microsoft cloud platform with regular updates and support in the EU.
Comparison by criteria
Support and future
1C: official support in Ukraine has been wound down; updates and development are in question. Business Central: a global vendor, releases twice a year, support through a partner network.
Data and security
1C: traditionally on-premise, security is on your side. Business Central: Microsoft Azure cloud with EU data centres, security certifications and backups by default.
Integrations
1C: integrations with modern services often need separate solutions. Business Central: native links to Excel, Outlook, Teams, Power BI and open APIs.
Total cost of ownership
1C: licence plus server, updates and administration. Business Central: per-user subscription with infrastructure included — a predictable monthly cost.
Objectively: if your business already runs on 1C with settled processes, the main argument to switch isn't features — it's the risk of staying on software with no support or future in Ukraine.
Total cost over three years
The comparison people usually run is the licence fee, and on that measure 1C wins easily — much of it is already paid for. Over three years the picture inverts, because the costs that matter are not the ones on an invoice.
| Cost | 1C | Business Central |
|---|---|---|
| Licence | Largely sunk; support contract if still available | $80–110 per user per month, predictable |
| Updates | A project each time, priced per developer-day | Included, twice yearly, automatic |
| Legislative changes | Custom work, and only if someone is still maintaining it | Delivered through the partner localisation |
| Specialists | Shrinking market, rising hourly rates | Broad partner network, replaceable |
| Infrastructure | Servers, backups, disaster recovery on you | Included in the subscription |
| Key-person exposure | Often one person knows the configuration | Standard platform, documented |
The last row is the one that tends to decide it. A configuration only one person understands is not a software cost — it is an operational risk that sits on the balance sheet without ever being measured.
Where 1C is still the sensible choice
Not every company should move, and pretending otherwise wastes everyone's time.
- The entity is being wound down or sold within a year. A new ERP on a business you are exiting is money spent on someone else's system.
- Very small and entirely domestic. A handful of users, one location, no foreign owners, no external reporting obligations, updates still arriving. The pressure is not there.
- You cannot spare the attention right now. A migration needs several weeks of someone senior. Doing it badly is worse than doing it later, and rushing is how projects fail.
What does not qualify as a reason to stay: "we are used to it." That is a real cost of change, but it is not an argument about the system.
If the company reports into a foreign group
This changes the calculation entirely, and it is worth separating out because the drivers are different.
For a subsidiary inside an international group, the problem with 1C is not features. It is that the parent cannot read it. Interfaces and documentation are in Russian or Ukrainian, auditors cannot open the system, and consolidated figures rest on one local accountant nobody at head office can independently verify.
Business Central sets interface language per user against a single database, so the local team keeps working in Ukrainian while group finance reads identical records in English. For groups, that is usually the whole argument. The full version is in your Ukrainian subsidiary runs 1C.
The question to ask any vendor
Business Central does not ship with Ukrainian statutory accounting. VAT, tax invoices and the ЄРПН registry come from a partner localisation — and the same is true of every other international ERP, so this is not a mark against it.
What matters is that the question gets asked properly. Not "do you have a Ukrainian localisation," which everyone answers yes to, but:
- Who develops and maintains it, and how many years has it been in the market?
- How quickly was it updated after the last change in tax law — with an example?
- What happens to it if we change partner?
- Is maintenance included, or billed separately when legislation changes?
The answers separate vendors far more reliably than any feature comparison.
What to do with this
If the decision is made, the sequence that saves the most money is data cleaning first — it is the largest cost driver and the one you can start without a contract. The steps are in the preparation checklist, the numbers are in what a migration costs, and the project as a whole is set out on the migration page.
What to weigh before switching
- Data migration. Moving master data and balances out of 1C is a separate but manageable stage.
- Team training. The interface differs, so budget time for adaptation.
- Process specifics. Custom 1C tweaks don't transfer automatically — they need rethinking for Business Central.
The most reliable way to decide is to start with a process audit. It shows what from your 1C maps onto standard Business Central and what needs a separate solution. More on the process itself is in our piece on the cost of migrating from 1C.