1C to Odoo Migration in Ukraine: What Foreign Companies, NGOs and Investors Need to Know in 2026

If you’re running operations in Ukraine — or advising someone who is — you’ve almost certainly encountered 1C. It’s the Soviet-era accounting and ERP software that dominated post-Soviet business for three decades. Your local team probably still uses it. Your Ukrainian accountant almost definitely does.

Here’s the situation in 2026: 1C is now on Ukraine’s official banned software list. The window to migrate quietly is open. And if you’re looking for an Odoo implementation partner in the region, the market has matured significantly since 2022.

This article gives you the market context, the legal framework, a clear technical comparison, and a practical migration roadmap — written for people who understand ERP but may not know how Ukrainian enterprise software works.

The Regulatory Situation: What the 1C Ban Actually Means

Ukraine’s government has spent the past two years building a formal legal framework around software of Russian origin. The key documents:

The registry, published by the State Service of Special Communications on January 8, 2026, covers 1C, BAS, Bitrix24, and dozens of other Russian-origin products. According to DOU, 1C products occupy a prominent position among the 39 entries in the first registry release.

What This Means for Foreign-Operated Entities

For a foreign company with a Ukrainian subsidiary, the practical risks are three:

Banking friction. Ukrainian banks are required to flag transactions and accounts connected to sanctioned software usage. The legal theory is that paying for or maintaining sanctioned software may constitute violation of the sanctions regime. In practice, this means account monitoring and potential freezes — not theoretical, already happening to some companies.

Government contract exclusions. If your Ukrainian entity bids on public procurement, or works with a prime contractor that does, using banned software is grounds for disqualification. This applies to NGOs working with state agencies and international donors with procurement rules tied to Ukrainian law.

Integration blockers. Ukrainian state registries and tax systems increasingly refuse connections from systems on the banned list. Companies still on 1C are finding that tax reporting integrations, e-invoicing, and banking APIs are breaking — not because the software stopped working, but because the ecosystem is moving away from it.

The complete ban takes effect January 1, 2030. The current period is officially described as the window for “urgent decommissioning measures.”

Understanding the 1C Ecosystem: A Briefing for Non-Ukrainian Teams

Before getting into alternatives, it helps to understand what 1C actually is — because “accounting software” undersells it significantly.

1C:Enterprise is a development platform as much as it is a product. Ukrainian businesses — especially those with more than 20 employees — typically run heavily customized configurations built on top of 1C. The platform handles accounting, inventory, payroll, production planning, CRM, and point-of-sale in a single (albeit fragmented) environment.

This is why migration is complex. You’re not just swapping one accounting tool for another. You’re replacing an entire operational backbone that a company’s processes, staff habits, and integrations have grown around over 10–20 years.

BAS (Business Automation Software) is the Ukrainian fork of 1C, developed post-2014 as a nominally independent alternative. In practice, it shares the same architecture, the same developer ecosystem, and the same security vulnerabilities. It’s also on the banned list.

The important thing to understand: the 1C developer ecosystem in Ukraine is collapsing. Junior developers don’t learn a platform tied to a sanctioned Russian company. Senior 1C developers are retraining or have emigrated. Companies that were keeping 1C alive through freelance patches are finding those patches increasingly unreliable — every legislative change (new VAT rates, new payroll rules, new reporting formats) requires manual code changes that nobody is officially maintaining.

Why Odoo Wins in the Ukrainian Market

Odoo isn’t the only ERP operating in Ukraine — SAP and Microsoft Dynamics are present, primarily in enterprise segments. But for the SMB and mid-market space that makes up the vast majority of Ukrainian businesses, Odoo has emerged as the dominant migration target, for reasons that are primarily practical rather than ideological.

Architecture Comparison

PostgreSQL eliminates dependency on Microsoft licensing costs. Python means you can hire from a global talent pool instead of a shrinking niche market. The modular architecture means you can implement incrementally — start with accounting and inventory, add manufacturing and HR later — rather than committing to a full cutover on day one.

Ukrainian Localization: The Part That Matters for Compliance

The most common concern from international teams is whether Odoo actually handles Ukrainian accounting requirements. According to Diia.Business, the answer as of 2026 is yes — comprehensively.

The Ukrainian localization package covers:

• Chart of accounts and trial balance (ОСВ) — the standard Ukrainian account structure, formatted exactly as Ukrainian accountants expect it
• VAT (ПДВ) — first-event recognition, automatic tax invoice generation, all current rates (20%, 7%, 14%, 0%), and VAT-exempt operations
• PRRO (electronic cash registers) — native integration with Checkbox and Vchasno.Kasa, with direct data transmission to the State Tax Service
• Regulatory reporting — XML export for M.E.Doc, Sota, or the Tax Authority’s electronic filing portal
• Banking synchronization — native API integration with Privatbank and Monobank for automated bank reconciliation
• Payroll — full compliance with Ukrainian labor law: unified social contribution (ЄСВ), personal income tax (ПДФО), military levy (Військовий збір), automated payslips and time tracking

This is not a workaround or a third-party plugin situation. These are maintained, certified modules from Ukrainian Odoo partners with established track records.

Security: The Argument That Closes the Conversation

For any foreign company with data governance obligations — GDPR, donor reporting requirements, investor due diligence — the security argument is straightforward.

1C has had no official security updates since sanctions cut off the Ukrainian market in 2024–2025. Vulnerabilities discovered by researchers remain unpatched permanently. The system was not architected with multi-factor authentication. Data transmission protocols are outdated and well-documented attack vectors.

More significantly: SBU and Cyberpolice guidance explicitly flags that Russian-developed software may contain remote access mechanisms originally installed for “technical support” purposes. In a wartime context, this is treated as a live intelligence risk, not a theoretical one.

Odoo’s codebase is open, hosted on GitHub, audited externally, and maintained on a global security patch cycle. For any entity that needs to demonstrate data security to headquarters, auditors, or donors, the choice is not complicated.

The Replacement Map: Top Banned Systems and Their Odoo Equivalents

For teams inheriting a Ukrainian operation and trying to understand what they’re working with:

Industry note for manufacturing: We’ve run implementations for jewelry production (precious metals tracking, serial numbers, batch control) and complex component manufacturing. If you’re inheriting a Ukrainian factory, the vertical coverage is there.

The Migration Roadmap: How It Works Without Stopping Operations

The standard concern from international management teams is business continuity. The answer is the MVP model — 4–8 weeks of parallel operation, not a hard cutover.

Step 0: Deployment Model

Three options, depending on your entity’s IT governance requirements:

• Odoo Online — SaaS, no server management. Appropriate for most SMB operations.
• Odoo.sh — Odoo’s own cloud platform, more configuration control. Common for mid-market.
• On-premise — Full server control. Relevant for industrial operations with strict data residency requirements or classified government contracts.

Step 1: Audit and Cleanup

Before migration, map what’s actually in the 1C configuration — custom modules, integrations, non-standard reports. This is also when you identify the “digital clutter” accumulated over years: duplicate records, outdated customer databases, obsolete product lists. Migration is the right moment to clean.

Step 2: Data Mapping and Preparation

Transfer of reference data, account balances, open documents. Determines what migrates automatically and what requires manual review.

Step 3: MVP in 4–8 Weeks

Core modules live — Sales, Inventory, Accounting — while 1C remains operational as a fallback. The team begins working in Odoo. Issues surface and get resolved before the old system goes dark.

Step 4: Scale After Stabilization

Marketing automation, e-commerce, HR modules come online. Full 1C decommission. For e-commerce and retail operations, see our implementation experience.

Step 5: Team Enablement

Ukrainian accounting teams typically reach operational confidence in 2–3 weeks of active use — not months. The interface learning curve is real but short.

Full implementation methodology is documented on our Odoo Implementation Services page.

Economics: What Migration Costs and What It Returns

Project Cost Ranges (2026)

Certified Odoo specialist rates in Ukraine run at 1,500–1,800 UAH/hour ($38–43/hour), which is competitive against Western European rates for the same expertise.

Subscription vs. Hidden 1C Costs

Odoo Enterprise subscription: approximately €12–18 per user per month, inclusive of all version updates and security patches.

The real 1C cost in 2026 is harder to calculate: licenses, ITS maintenance subscription, freelancer fees for each legislative update, risk exposure from sanctions, and the growing cost of banking and integration workarounds. The subscription model wins on transparency alone.

ROI: Where the 150–200% Figure Comes From

Based on analytics from 2026 implementations, ROI for Ukrainian SMB migrations reaches 150–200% within two years. The sources:

• Elimination of manual processes (automated bank reconciliation, PRRO, reporting)
• Removal of 1C maintenance and patching costs
• Avoidance of sanction-related fines and account blocks
• Productivity gains after team adaptation

For small businesses, we’ve structured a dedicated package with fixed pricing and compressed timelines.

For Odoo Partners: Working in Ukraine

A specific note for international Odoo partners exploring the region.

The Ukrainian Odoo market has grown significantly since 2022 — driven exactly by the migration wave from 1C. The local partner ecosystem has developed expertise in Ukrainian-specific requirements that most Western partners haven’t needed to build: Ukrainian chart of accounts, PRRO integration, specific payroll legislation, M.E.Doc reporting. This is deep, tested, production-grade knowledge.

If you’re receiving inquiries from Ukrainian clients or companies with Ukrainian operations that fall outside your team’s geographic or regulatory comfort zone, subcontracting and collaboration arrangements are a practical option. We’ve worked in this model with partners in the EU and North America.

For NGOs and international organizations: healthcare and wellness implementations follow their own track — see our health sector experience.

The Bottom Line

Ukraine’s 1C era is over — legally, technically, and in terms of the talent market. For foreign companies with Ukrainian operations, the question is no longer whether to migrate, but how to do it without disrupting the business.

The regulatory window is 2026. Companies migrating now do it on their own terms: proper audit, clean data preparation, genuine team training. Companies that wait until 2029 will do it under pressure from banks and government contractors.

By our estimate, the share of SMBs still on sanctioned software will fall below 20% by end of 2026 — driven not by awareness campaigns, but by banking pressure and procurement requirements. That transition will happen regardless. The only variable is whether your Ukrainian operation is ahead of it or behind it.

If you’re running operations in Ukraine, advising a company that does, or evaluating the market — we’re available for a no-obligation conversation.

By Dmytro Romaniuk

CEO & Founder

10 mins read | May 07, 2026

• 
• 
•