Moving from 1С/BAS to Odoo

Move from 1С/BAS to Odoo in stages: customers, products, prices, stock and open debts go across, and the business keeps working while both systems run side by side

Many companies want to leave 1С/BAS: it is on the official prohibited software list, and the team has long wanted sales, warehouse and accounting in one modern system. The fear is always the same — the move will stop shipments and lose years of history. We move you to Odoo in stages: first we look at what is really in your 1С/BAS, clean out duplicates, make a trial load, and let both systems run in parallel until the figures match. Only then is 1С/BAS switched off. Below: what exactly we carry over, how the move goes and which capabilities of Odoo we rely on.

Request an integration System page: 1С/BAS →System page: Odoo →

What we move

1С/BAS → OdooCounterparties from 1С/BAS — companies and individuals with tax code, addresses, contact people and bank details — become contacts in Odoo; duplicates are merged before the load.
1С/BAS → OdooThe item catalogue with units, groups, barcodes and the price types you really use becomes Odoo products and price lists.
1С/BAS → OdooStock balances by warehouse on the switch-over date are loaded as opening quantities, so the warehouse in Odoo starts from the same numbers.
1С/BAS → OdooUnpaid customer invoices and debts to suppliers on the same date move as open balances, so nobody loses track of who owes whom.
1С/BAS → OdooCustomer orders that are not yet shipped are moved to Odoo, so they are finished there rather than in 1С/BAS.
1С/BAS → OdooSales history by client and product for the period you choose is carried over as reference, so the salesperson sees what the client bought before.

How the move goes

First we check that your Odoo plan allows outside data exchange, and set up a separate exchange user with its own access key instead of a person's password.
We look at what is really in your 1С/BAS: which catalogues and documents are in use, what is outdated, where data is kept in unusual places; together we decide what moves to Odoo and what stays in the archive.
Before the move we clean the data: merge duplicate counterparties and items, fix tax codes and units, and mark old records the new system does not need.
We make a trial load into a test copy of Odoo, and your people check customers, products and balances on familiar examples before anything touches the working system.
For the transition both systems run in parallel: new work is done in Odoo, and 1С/BAS stays at hand as a reference, so shipments and payments do not stop.
We reconcile together with your accountant: balances, debts and stock in Odoo against 1С/BAS on the same date; every difference is explained before the next step.
Only after the reconciliation is 1С/BAS switched off for daily work; its database is kept as an archive for audits and old questions.

Automation scenarios

One client, several cards

Before the same client sits in 1С/BAS under several spellings, and his debt is split between the cards.

After duplicates are merged before the move, and in Odoo the client has one card with the whole debt.

Afraid to switch

Before the move is postponed again and again, because nobody knows how the warehouse will ship on the day of the switch.

After balances are loaded on an agreed date, both systems run side by side, and shipping goes on as usual.

History left behind

Before in the new system the salesperson cannot see what the client bought last season and asks the accountant to dig into 1С/BAS.

After the client's past sales are in Odoo next to his card, and nobody needs to open 1С/BAS.

Who still owes

Before after a move nobody is sure which invoices were paid before it, and reminders go to clients who have already paid.

After open debts are moved on one date and reconciled with the accountant, so reminders go only to those who really owe.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

BAS products are on Ukraine's official list of prohibited software (Cabinet resolution №1335 of 22.10.2025, based on Presidential Decree №601/2024 of 02.09.2024). The direct ban applies to the state sector, critical infrastructure and systems processing state information resources.
Source: impactalaw.com ↗ checked 2026-09-25
According to the same documentation, the platform automatically builds a REST interface using the OData protocol, through which outside systems can read, change, create and delete data over HTTP.
Source: its.bas-soft.eu ↗ checked 2026-09-25
Almost all Odoo data and features are reachable from outside for connecting or analysis; part of that is available over XML-RPC from a variety of programming languages.
Source: www.odoo.com ↗ checked 2026-09-25
Outside data access is only available on custom-priced plans — it isn't available on the entry-level single-app plan or on the standard plan.
Source: www.odoo.com ↗ checked 2026-09-25
Since version 14.0, Odoo supports access keys that can replace a password in scripts, while the account's regular sign-in stays the same.
Source: www.odoo.com ↗ checked 2026-09-25

Limits

The limits come from both systems. Outside data exchange with Odoo is only available on plans with individual pricing — not on the entry-level single-app plan or the standard plan — so we check your plan first; a cloud account also needs a separately set password or access key. Not everything in 1С/BAS has a place in Odoo: documents and reports specific to your configuration are kept in the archive or rebuilt in Odoo, and we agree which at the audit. 1С/BAS is on the official prohibited software list: we do not take projects for state bodies, critical infrastructure or systems with state data, and with private businesses we discuss the risk openly.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Is it legal to stay on 1С/BAS?

1С/BAS is on the official prohibited software list. The direct ban covers the state sector, critical infrastructure and systems with state data. For a private business it is formally allowed but considered a risk — check with your lawyer.

Will work stop during the move?

No. For the transition both systems run in parallel: new documents go into Odoo, and 1С/BAS stays as a reference until the reconciliation shows the same figures. 1С/BAS is switched off only after that.

What happens to the history and the archive?

The history you need every day — what each client bought, who owes what — moves to Odoo. The full 1С/BAS database is kept as an archive, so an old document can still be found for an audit or a dispute.

Does our Odoo plan matter?

Yes. Outside data exchange in Odoo is only available on plans with individual pricing, so we check the plan before anything else. If yours does not allow it, we discuss the options with you before any work starts.