Short answer: Migrating from 1C to Odoo means moving your products (SKUs), customers and suppliers, stock and receivable/payable balances, open documents and chart of accounts into Odoo, and rebuilding your processes in one system. A typical project takes 2–6 months, and standard Sales and Inventory can be live in 6–8 weeks. The safest approach is to migrate clean opening balances rather than your full history, and to keep the parallel-run period short.
Many companies in Uzbekistan have run on 1C for years. Accounting lives in one database, the warehouse sometimes in another, sales in Excel and Telegram, and there is often no CRM at all. That works while the business is small. As it grows, the patchwork starts to slow everyone down, which is why searches like "odoo 1c" and "1C to Odoo migration" keep rising.
This is not a feature comparison; we cover that in Odoo vs 1C. This guide is about execution: once you have decided to switch, how do you migrate without chaos or data loss?
Why are companies moving from 1C to Odoo?
The main reason is to run every department in one system and work from a browser or phone anywhere. 1C is strong at statutory accounting and tax reporting, but when a company needs sales, CRM, manufacturing and inventory in one view, it usually looks for a broader ERP.
The reasons we hear most often:
- One system instead of several. In Odoo, sales, purchasing, inventory, CRM, manufacturing, accounting and HR share one database. A salesperson confirms an order, the warehouse sees it immediately, and the journal entries are created automatically.
- Web and mobile access. Odoo runs in the browser, with no desktop clients or remote desktops to maintain. Branches, warehouses and field agents can work from a phone.
- Less dependence on a single developer. In many companies the 1C configuration has been modified for years by one person and never documented. When that person leaves, maintenance becomes a real problem. Odoo is an open-source, modular platform with a large global developer community.
- A clear licensing model. Odoo pricing depends on the number of users and apps, and the Community edition is free.
- Integrations. Online stores, marketplaces, IP telephony, banks and other services connect through a modern API.
To be fair: 1C is not a bad system, and for many companies it does its job well. The real question is whether the tool still fits the size and needs of your business today.
When should you not migrate from 1C to Odoo?
If you only need accounting and tax reporting and your processes work well in 1C, there is no need to rush. A migration is a project, and it takes time, budget and your team's attention.
Consider postponing if:
- The problem is the process, not the software. If inventory control is chaotic, a new system will not fix it on its own. Sort out the process first.
- Leadership is not committed. If the ERP project is treated as "an IT task", staff will quickly drift back to old habits.
- A reporting deadline is close. Big changes right before year-end reporting or a tax audit add unnecessary risk.
- The company is very small. A team of two or three may be fine with a simpler tool.
What data should you migrate from 1C to Odoo?
In short: master data (products, customers, suppliers), balances as of the cut-over date and open documents always move; the full transaction history usually does not. History stays in 1C as a read-only archive or is loaded into Odoo in summarised form.
- Products / SKUs, units of measure, categories — Migrate?: Yes, always; Notes: Remove duplicates and obsolete items first
- Customers and suppliers — Migrate?: Yes; Notes: With tax ID (TIN), bank details and contacts
- Prices and pricelists — Migrate?: Yes; Notes: Discount rules are rebuilt in Odoo
- Stock on hand — Migrate?: Yes, at cut-over date; Notes: Most reliable right after a physical count
- Receivables and payables — Migrate?: Yes, at cut-over date; Notes: Broken down per partner
- Open documents (unpaid invoices, undelivered orders) — Migrate?: Yes; Notes: Otherwise live processes break
- Chart of accounts and GL balances — Migrate?: Yes; Notes: Mapped to national accounting standards
- Fixed assets — Migrate?: Usually yes; Notes: With net book value and depreciation
- Years of transaction history — Migrate?: Usually no; Notes: Keep 1C as an archive or load summaries
Choosing a history strategy
You have three options:
- Balances only. Fastest and cheapest. You load the position as of the cut-over date, and 1C stays available in read-only mode.
- Balances plus recent history. For example, current-year sales for analytics, loaded by month or at document level.
- Full history. Rarely worth it: slow, expensive and error-prone.
For most companies, option one or two is the right call.
How does a 1C to Odoo migration work, step by step?
A migration follows five core stages: diagnostics, configuration, integrations, data migration and staff training, followed by post-launch support. For the general approach, see our Odoo ERP implementation guide.
- Business diagnostics and process analysis. We map what is done in 1C today, which reports people actually use and which customisations are genuinely needed. The output is a map of your future processes in Odoo.
- Configuration and customisation. Apps, company structure, warehouses, pricing policy and user rights. Custom development only where standard features truly fall short.
- Integrations. Bank, online store, telephony, e-invoicing operator and other systems. If 1C stays for a while, the data exchange with it is set up too.
- Data migration. Export from 1C, clean-up, mapping to Odoo's structure, test load, reconciliation and the final load. At least one trial migration is essential.
- Staff training. Separate sessions per role: sales, warehouse, accounting, management. Short guides and practice on real data.
- Go-live and support. Expect plenty of questions and small fixes in the first weeks; that is normal.
Do you need a parallel run?
Yes, but keep it short and rule-based. Usually for 2–4 weeks the core operations run in Odoo while 1C is used for reconciliation and statutory reports. A long parallel run wears people out with double entry and creates the question "which number is right?". Decide in advance which documents are created only in Odoo from which date.
Can 1C and Odoo work together?
Yes. A common setup is to move operations (sales, inventory, CRM, manufacturing) to Odoo while statutory accounting and tax reporting stay in 1C for a period. The two systems exchange documents and master data through an integration.
This makes sense when:
- the accounting team is deeply used to 1C and their switch is planned for later;
- moving the books mid-year is too risky;
- the company wants to fix operational efficiency first.
The downside is maintaining two systems and monitoring the exchange. That is why we usually recommend it as a temporary stage: for example, accounting also moves fully to Odoo at the start of the next financial year.
How long does a 1C to Odoo migration take?
On average 2–6 months. Standard Sales and Inventory can be live in 6–8 weeks; manufacturing, complex integrations and a full accounting migration extend the timeline.
- Sales + Inventory, balances migrated — Typical timeline: 6–8 weeks
- Sales, Inventory, Purchasing, CRM + accounting — Typical timeline: 3–4 months
- Manufacturing, multiple branches, integrations — Typical timeline: 4–6 months
The biggest factors are the quality of your 1C data, how fast decisions are made and the amount of customisation. For budgeting, read Odoo ERP pricing in Uzbekistan.
What are the risks, and how do you reduce them?
The main risks are dirty data, staff resistance and vague requirements. All of them are manageable if you plan for them up front. We list the common pitfalls in 7 ERP implementation mistakes.
- Duplicate products and partners — How to reduce it: Clean up before migration; one SKU naming rule
- Balances don't match — How to reduce it: Stock count at cut-over; partner balance confirmations
- "Make it work exactly like 1C" — How to reduce it: Rethink the process; drop unnecessary customisations
- Staff don't use the new system — How to reduce it: Role-based training, internal champions, management follow-up
- Parallel run drags on — How to reduce it: A fixed cut-over date and clear rules
- Gap in tax reporting — How to reduce it: Switch at the start of a reporting period; test localisation early
What is specific to migrating from 1C in Uzbekistan?
In Uzbekistan the key issue is tax and accounting compliance. When Odoo is localised, invoices, VAT (QQS) rates and reports are configured for local rules.
Things to watch:
- Chart of accounts. Accounts from 1C are mapped to a chart of accounts based on Uzbekistan's national accounting standards (NAS). This is the most delicate part of the migration, so do it together with your chief accountant.
- VAT. Tax rates and tax types are set up in Odoo in advance so that tax is calculated automatically on every document. More in Odoo VAT and tax localisation in Uzbekistan.
- Electronic invoices. E-invoicing is widely used in Uzbekistan. Before go-live, decide how documents will flow from Odoo to your e-invoicing operator.
- The 1C legacy. Many accountants have used 1C for years. Involve them from day one and budget extra time for their training.
- Reporting period. Moving the books at the start of a quarter or year avoids breaks in your reports.
1C to Odoo migration checklist
- 1 — Task: Migration goals and KPIs defined; Owner: Management
- 2 — Task: List of 1C processes and reports compiled; Owner: Project team
- 3 — Task: History strategy chosen (balances / recent history); Owner: Management + accounting
- 4 — Task: Products and partners cleaned up; Owner: Department leads
- 5 — Task: Chart of accounts mapping approved; Owner: Chief accountant
- 6 — Task: Trial migration run and verified; Owner: Implementation partner
- 7 — Task: Cut-over date and parallel-run rules set; Owner: Management
- 8 — Task: Stock count and balance confirmations done; Owner: Warehouse + accounting
- 9 — Task: Staff trained by role; Owner: Implementation partner
- 10 — Task: 1C switched to archive mode; Owner: IT
How Deep Vision helps you move from 1C to Odoo
Deep Vision is an Odoo Gold Partner based in Tashkent. Our team has 7 certified Odoo specialists, and 26 of our client projects are listed in the official Odoo partner directory. The company's founder and CEO is Amon Olimov.
We work with wholesale and retail, manufacturing, construction and service businesses. Optika.uz runs sales, inventory and accounting in one system; Timsoll manages more than 7,000 SKUs in Odoo (read the Timsoll story); and RockBeton brought production, inventory and reporting together in a single system.
On a 1C migration project, we:
- analyse your 1C processes and decide what really needs to move;
- configure Odoo for Uzbekistan: invoices, VAT and reporting;
- build a temporary integration with 1C if needed;
- clean your data and run the trial and final migrations;
- train your staff and support the system after go-live.
See our Odoo implementation service for details. To discuss your project, fill in the free brief or call +998 77 093 00 07. We reply within 24 hours.
Frequently asked questions
How long does a 1C to Odoo migration take?
On average 2–6 months. Standard Sales and Inventory can go live in 6–8 weeks. Manufacturing, integrations and a full accounting migration extend the timeline.
Do I need to migrate my entire 1C history?
Usually not. Most companies migrate master data, balances at the cut-over date and open documents, and keep 1C as a read-only archive. If needed, current-year data can be loaded in summarised form for analytics.
Can 1C and Odoo run at the same time?
Yes. Sales, inventory and CRM can run in Odoo while accounting temporarily stays in 1C, with the two systems exchanging data through an integration. We usually recommend this only as a transitional stage.
Does Odoo meet Uzbekistan's tax requirements?
Yes, once it is localised. Invoices, VAT rates and reports are configured for local rules, and the chart of accounts is mapped to national accounting standards.
How long should the parallel run last?
Two to four weeks is usually enough. Set a clear cut-over date and define which documents are created in which system. A long parallel run exhausts staff and muddles the numbers.
What should we prepare before migrating?
Remove duplicates from your product and partner lists, do a physical stock count and confirm balances with partners. Also list the reports your team actually uses in 1C.
How much does it cost to move from 1C to Odoo?
It depends on the number of users, apps, integrations and the volume of data to migrate. We give an exact estimate after diagnostics; you can start by filling in the free brief on deepvision.uz.
Conclusion
Moving from 1C to Odoo is not just a technical transfer; it is a chance to modernise how your company works. Success rests on three things: clean data, a firm cut-over date and well-trained people. Don't try to move your whole history. Start with balances and open documents, and switch accounting at a convenient reporting boundary.
Planning a migration? Book a free consultation or call +998 77 093 00 07, and we will build a realistic migration plan for your 1C database together.