Main Concept Services Audit & Reporting SAF-T Connector Migration to Odoo Transfer Pricing Other Services Industries Contacts UA
Service 03

Migration from 1C / BAS to Odoo

Transition from Russian software to a modern ERP platform — with focus on accounting methodology, correct data migration, and compliance with reporting requirements from day one.

About 1C/BAS to Odoo Migration

LUCAS helps companies migrate from 1C/BAS to Odoo without losing accounting logic, historical data or control over financial processes. We start not with programming but with an analysis of accounting methodology, business processes, integrations and data structure — so the new ERP works correctly for finance, accounting, sales, warehouse, manufacturing and management reporting from day one.

What it is Odoo is a modular ERP platform that consolidates finance, warehouse, sales, purchasing, manufacturing, CRM, HR and other business processes in a single system.
How it differs from 1C/BAS Odoo has a modular architecture, a modern web interface and a broad ecosystem of apps and integrations, but requires proper configuration for Ukrainian accounting, tax and reporting requirements.
What migration involves Documenting current processes in 1C/BAS, defining required Odoo modules, designing accounting logic, preparing data for migration, configuring the system, testing operations and training users.
What data is migrated Typically migrated: master data, counterparties, inventory items, balances, open transactions, settlement history, warehouse data and other information needed to start working in Odoo.
Who it suits Companies looking to move away from 1C/BAS, centralise business processes, reduce dependence on a legacy system and adopt a flexible ERP platform for future growth.
Key risk The main risk is losing accounting logic between finance team requirements and technical implementation. This is why Discovery is essential: process, data, integration, reporting, customisation, timeline and budget analysis before development begins.

Transition from 1C/BAS to Odoo without losing accounting logic

Our "auditor + developer" tandems eliminate misunderstandings between finance teams and programmers — and save up to 40% of implementation cost compared to a standard ERP project.
Legal Context · 2026

1C/BAS creates increasing legal and compliance risks

Restrictions on the use of defined software products apply to government bodies, state institutions, state enterprises, and certain critical infrastructure facilities under Cabinet Resolution №1335 and lists of authorized bodies. For the private sector — restrictions through NSDC sanctions lists.

Draft law №13505 provides for tightened restrictions on the use of software products associated with the aggressor state, including financial penalties of up to 2% of annual turnover for violations. The status of the draft law and effective date should be verified at the time of decision-making.

  • Public sector — restrictions on defined products (Cabinet Resolution №1335)
  • Private sector — restrictions through NSDC sanctions lists
  • Draft law №13505 — fines up to 2% of annual turnover
  • Banks increasingly flag companies on 1C as higher risk
Odoo globally · #4 ERP

Global ERP market mainstream

Odoo is one of the world's most widely used open-source ERP/CRM platforms, growing faster than the market. According to Odoo public data, the platform is used by millions of users in many countries: 175 countries, 15 million users. Clients include Toyota, Nokia, Nestlé, Airbus, Decathlon, Danone.

One subscription covers 30+ modules: accounting, CRM and sales, warehouse and logistics, manufacturing, projects, HR management.

  • One of the world's most widely used open-source ERP platforms
  • 175 countries, 15 million users
  • 30+ modules in one subscription
  • Modern interface and mobile apps
TCO · Total Cost of Ownership

70–80% lower cost than SAP or MS Dynamics

Odoo has a transparent licensing model. Compared to large enterprise ERPs, total cost of ownership is typically significantly lower, but actual results depend on the scale and complexity of processes.

With Odoo you are not locked into vendor dependency — the solution is not tied to a single vendor. Thousands of ready-made connectors and a huge developer community allow automating new processes without expensive custom development.

  • Transparent licensing model
  • Lower total cost of ownership
  • No vendor lock-in
  • Thousands of ready-made connectors and customizations
Finance-first · Methodology

Benefits of implementation with LUCAS

We don't need to be explained what depreciation is, how double-entry works, or what the "first event" principle means. LUCAS builds system architecture around accounting logic — this makes Odoo easier to use and reduces error risks after go-live.

The project starts not with a technical specification, but with an analysis of accounting methodology: how accounting is maintained, what controls are required, what reporting is generated.

  • Finance-first discovery — accounting methodology analysis
  • Chart of accounts and analytics configuration
  • Responsibility centers and control procedures
  • Process and control adaptation to your needs
Auditor + Developer

Fast implementation saves budgets

Misunderstandings between finance teams and developers are the main source of delays and cost overruns in any ERP project. Every hour of developer work costs money, including time spent understanding requirements and business logic.

Our own "auditor + developer" working tandems understand each other perfectly. This saves 30–40% of implementation cost.

  • In-house "auditor + developer" tandems
  • Less time lost on requirement alignment
  • 30–40% implementation cost savings
2–6 months · 6 stages

Structured transition without accounting continuity risk

Depending on scope, the process takes 2 to 6 months and goes through six stages: business process analysis, accounting data architecture development, customization to business requirements, data migration from 1C, testing, go-live.

Parallel accounting can be maintained until results are confirmed — without risk of data loss or accounting gaps. Team training and transition to support are included in the standard process.

  • Process and accounting logic analysis
  • Data architecture and Odoo configuration
  • Data migration, testing and go-live
  • Parallel accounting during the control period
FAQ

What you should know.

The cost depends on company size, number of users, customization scope, integrations, and data migration. Odoo license is paid separately per user according to current Odoo pricing.
Balances, open transactions, and reference data are transferred. Parallel accounting is maintained until correctness is confirmed.
Continuity is ensured through a phased transition: first, critical processes, balances, and open transactions are identified, then data is transferred to Odoo and reconciled. Until results are confirmed, parallel accounting in 1C/BAS and Odoo may be maintained. The actual go-live only occurs after testing key scenarios and aligning results with the client team.
Typical adaptations for Ukrainian bookkeeping and tax accounting have already been developed for Odoo, covering most needs. Any additional settings and customizations can be implemented — the scope of development depends on the company's processes.
Odoo has an open architecture, transparent licensing model, and typically lower total cost of ownership compared to large enterprise ERPs. Thanks to ready-made modules and flexible customization, implementation can often be faster and cheaper, but actual results depend on the scale of processes.
For most of our clients, the monthly Odoo cost is €17.90 per user for the first year and €22.40 for subsequent years. All business modules are available within the Odoo subscription with no extra charges.
Yes. Training is required for accounting, managers, warehouse, sales, and other roles that will work in Odoo. A training course typically lasts up to 2 weeks.
Discovery is a short pre-project phase where we analyze business processes, accounting logic, data structure, integrations, and user expectations. Its purpose is to define the actual scope of Odoo implementation before development begins. The Discovery output gives the client a description of the target architecture, list of required modules, customization assessment, data migration approach, integration perimeter, and preliminary timeline and budget estimate. This reduces the risk of project misjudgment, unnecessary development, and cost overruns during implementation.
Yes, you can start with the accounting module and gradually add warehouse, sales, purchasing, manufacturing, or CRM. But before starting it is important to design the target architecture so that the first phase does not create constraints for future scaling.
Correctness is verified through reconciliation of the balance sheet, trial balances, counterparty balances, inventory, warehouses, banks and cash, as well as through testing of typical transactions. LUCAS conducts data reconciliation and control scenarios before go-live.

Time to plan the migration from 1C?

Order a Discovery from LUCAS — we will study your business processes, assess the migration scope, cost and timeline.