Deep Vision

Open-Source ERP: Odoo Helps Tajik Businesses Avoid Vendor Lock-In

A company that picks a closed ERP can end up dependent on one vendor for prices, servers and the right to change anything. How open-source Odoo reduces that risk and what it gives companies in Tajikistan.

Published: 6 min read
Open-Source ERP: Odoo Helps Tajik Businesses Avoid Vendor Lock-In

Tajikistan's economy has been growing fast. According to the World Bank, growth reached 8.2% in the first half of 2026. On the President's initiative, 2025–2030 were declared the Years of Developing the Digital Economy and Innovation, and an artificial intelligence strategy to 2040 has been adopted. At this pace, a company choosing an ERP should think not only about today's needs but about where it will be in ten years.

One question is often overlooked: who will actually own the system? What happens if licence prices rise, the vendor leaves the market, or the relationship with the implementer breaks down? This article is about that problem, known as vendor lock-in, and how open-source Odoo addresses it.

What vendor lock-in is and how it happens

Vendor lock-in is a situation where a company cannot leave its software supplier. It rarely happens overnight. It builds up gradually:

  • Closed data formats. Reports, inventory and customer data are stored in a form only that program can read. Export exists, but it is incomplete.
  • Only the vendor can change anything. When a business process changes, only one company can make the adjustment, and it sets the price.
  • No choice of hosting. The system runs only in the vendor's cloud or, the opposite, only on an old local server with no path to the cloud.
  • Prices rise one way. After five years of data have been entered, leaving costs more than paying the higher licence.

In the region this is common: a company stays on software installed in the 2010s that no longer gets updates, because the developer left or the vendor moved to another market.

What open source changes

Odoo comes in two forms. Odoo Community is fully open source under the LGPL v3 licence, with its source code public on GitHub (github.com/odoo/odoo). Odoo Enterprise is a set of additional modules built on top of Community and sold by subscription; its code is also available to subscribers and written in Python.

In practice this means:

  1. Your data lives in your database. Odoo runs on PostgreSQL, a widely used, open and well-documented database. You can take all of your data at any time.
  2. You choose where it runs. Odoo Online (cloud), Odoo.sh (managed platform) or your own server (on-premise), and you can move between them later.
  3. You can change partners. Thousands of Odoo partners and independent developers work in many countries. If even Deep Vision were not the right fit (we work hard so that this does not happen), the project can be handed to another partner because the code and technology are standard.
  4. Changes are made in a mainstream language. Odoo modules are written in Python and XML. Python is one of the most popular programming languages in the world, so specialists are easy to find.
  5. Regular releases. Odoo ships a new version every year (Odoo 17 in 2023, Odoo 18 in 2024, Odoo 19 in 2025), so the system does not age out.

Closed ERP vs Odoo: a practical comparison

This comparison is about approaches, not specific brands:

  • Access to data: closed systems often allow it only through the interface; Odoo gives direct PostgreSQL access and an API.
  • Code: hidden in closed systems; public in Odoo Community and available to subscribers in Enterprise.
  • Implementer: often one regional dealer for a closed system; any certified Odoo partner or your own IT team for Odoo.
  • Hosting: decided by the vendor in a closed system; cloud, Odoo.sh or your own server with Odoo.
  • Cost of leaving: high for a closed system; low for Odoo because data and code are open.

Why this matters for companies in Tajikistan

Digital sovereignty. As the state builds a digital economy, companies want to decide for themselves where their data is stored. Odoo can run on your own server in Tajikistan or in a data centre of your choice.

A growing local talent pool. IT education in Tajikistan is developing. Open technology lets local developers learn and support the system. With a closed system, the knowledge stays with the vendor.

Flexibility. A Tajik company's report formats, internal processes or industry specifics may not exist in off-the-shelf software. In an open system they are added as modules without breaking the core.

Cost control. Odoo is priced by the number of users, and you do not pay for modules you do not need. At one Deep Vision client (a company with more than 100 employees), licence costs fell from $30,000 to $11,000 a year. Details: Reducing ERP licence costs.

Uzbekistan's experience: localisation was possible because the code is open

When Uzbek businesses began adopting Odoo widely, one barrier remained: the system was not in Uzbek. Because Odoo is open source and its translation platform (translate.odoo.com) is open to everyone, the Deep Vision team was able to translate Odoo into Uzbek themselves. In the Odoo 19 source code, Deep Vision is credited in most Uzbek language files.

With a closed system, that work would happen only if the vendor wanted it. With open source, a local team can do what its own market needs. The same path is open for Tajikistan.

Example: a wholesale company

This is an illustrative example, not a measured client result. Imagine a wholesale company in Khujand that has used closed accounting software for eight years. The vendor raised prices, asked for additional licences for a new branch and could not integrate online orders. When the company moves to Odoo:

  • legacy data (customers, products, stock balances, receivables) is migrated through Excel;
  • 2–3 modules go live first: sales, inventory and accounting (more on this in Phased ERP rollout);
  • a new branch just needs new users, not a new server;
  • a B2B portal and an online store are connected with Odoo's standard modules.

Mavrid, an FMCG company in Tajikistan, also moved from an outdated legacy system to Odoo. Deep Vision connected its scales to the database (labels print, prices update instantly), integrated POS, price-check terminals and warehouse goods-receiving devices, and built a single dashboard for management.

Is open source secure?

Many executives ask, "If the code is open, hackers can see it too, right?" In practice open source strengthens security: vulnerabilities are seen by thousands of developers worldwide and fixed quickly. Linux, PostgreSQL and Python, some of the world's most critical infrastructure, are open source. Security depends not on hiding code but on correct configuration: access rights, backups, updates and encryption. Deep Vision sets these up on every project.

What you get with Deep Vision

  • Odoo Gold Partner. Per odoo.com/partners (as of November 2026), the only Gold-tier Odoo partner in Central Asia.
  • A documented project. All settings and custom modules are documented, so you are never locked in to us either.
  • Projects in Russian. Central Asian projects are run in Russian.
  • IFRS-based reporting. All our Odoo clients get reports on an IFRS basis, adapted to national requirements.
  • Odoo AI. Almost all our clients have Odoo AI connected for financial analysis, forecasting and sales analysis.

If you are choosing an ERP, read 15 reasons or leave a request.

Frequently asked questions

Is Odoo free?

Odoo Community is free and open source. Odoo Enterprise is a subscription priced per user. Implementation, configuration and training are separate services.

If we stop working with Deep Vision, will the system keep running?

Yes. The system, the data and the code stay with you. Another Odoo partner or your own IT team can continue the work.

Can data be stored in Tajikistan?

Yes. Odoo can be installed on your own server or in a data centre you choose. A cloud option is also available.

Can we migrate data from our old software?

Yes. Customers, products, stock balances and open receivables are usually migrated via Excel or direct import. The scope of historical transactions is agreed in the project.

Isn't upgrading open-source software difficult?

Upgrades are planned work. Standard modules are upgraded and custom modules are adapted to the new version. That is why we keep custom code minimal and documented.

Sources

  • Odoo source code and LGPL v3 licence: github.com/odoo/odoo
  • Odoo partner directory: odoo.com/partners (November 2026)
  • World Bank, Tajikistan Economic Update, 2026
  • Khovar: 2025–2030 declared Years of Developing the Digital Economy and Innovation
  • PostgreSQL documentation: postgresql.org