Skip to main content
Free 20-minute marketing audit
Limited spots available

Have a question?

We usually reply within 5 minutes.

WWhatsApp TTelegram

ERP and CRM Integration in Uzbekistan: Data Flows, Methods and a Launch Checklist

How to integrate ERP and CRM for a business in Uzbekistan: signs you need it, a data flow map, integration methods, common pitfalls and a test checklist.

ERP and CRM Integration in Uzbekistan: Data Flows, Methods and a Launch Checklist

Short answer: ERP and CRM integration is an automatic link between the system your sales team works in and the system that runs accounting, inventory and finance. Sales managers see stock and prices without leaving the CRM, and orders reach the warehouse without being retyped. An integration starts not with code but with a map: for each type of data you decide which system owns it, which way it flows and when it updates. Then you choose how to connect the systems and test the link against real scenarios. For a foreign company in Uzbekistan this often means connecting a global CRM to a locally maintained accounting system, which makes the map even more important.

CRM and ERP: who is responsible for what

The CRM is the sales team's workplace. Leads, customers, deals, calls and message threads live there. Its question is: "Who wants to buy, and where are we with them?"

The ERP is the company's system of record. It holds products, stock, prices, documents, payments and cost of goods. Its question is: "What do we have, what does it cost and where is the money?"

Problems appear where these two worlds meet. A deal closes in the CRM, but the goods leave a warehouse tracked in the ERP. A customer is created in the CRM, but their outstanding balance is calculated in the ERP. If the systems are not connected, the bridge between them is a sales manager, a spreadsheet and phone calls.

Some companies handle both jobs in one system; the article on custom ERP development covers when that makes sense. Many businesses, however, already have a sales team comfortable in its CRM while accounting runs elsewhere. Then the two need a proper connection. The CRM side itself, meaning how leads are received and processed, is covered in the article on lead handling and CRM. This article is about the link between the two systems.

Eight signs you need an integration

How many of these do you hear in your company?

Also read The Rate Moved, and Now Your Prices Differ in Three Places: Price List Management in an ERP Technology · 10 min
  • ☐ "Let me call the warehouse and check if it is in stock."
  • ☐ A sales manager retypes orders from the CRM into the accounting system.
  • ☐ The price in the CRM differs from the price in accounting.
  • ☐ Two managers promise the same item to two different customers.
  • ☐ A manager sells on credit again without knowing the customer still owes money.
  • ☐ At month end, CRM sales and booked revenue do not match.
  • ☐ Customer details are recorded differently in the two systems.
  • ☐ Management cannot say which advertising actually brought in revenue.

More than three means manual copying is already costing time and money. Every re-entry is a chance for error. Every phone call is minutes the customer spends waiting.

The integration map: which data flows where

The core rule of integration: each type of data has one owning system. Data is created and changed there, and the other system receives a copy. If both systems may freely edit the same data, soon nobody can tell which version is correct.

Below is a typical map for a wholesale or retail company. Adapt it to your own business:

  • Lead and deal — Owning system: CRM; Direction: CRM only; When it updates: —
  • Customer record — Owning system: CRM (new customer), ERP (legal and billing details); Direction: Two-way, by field; When it updates: On change
  • Product catalogue — Owning system: ERP; Direction: ERP → CRM; When it updates: On change
  • Prices and price groups — Owning system: ERP; Direction: ERP → CRM; When it updates: On change
  • Stock levels — Owning system: ERP; Direction: ERP → CRM; When it updates: Every few minutes or on request
  • Order — Owning system: CRM; Direction: CRM → ERP; When it updates: When the deal reaches the agreed stage
  • Order status (picked, shipped) — Owning system: ERP; Direction: ERP → CRM; When it updates: On status change
  • Payment and balance — Owning system: ERP; Direction: ERP → CRM; When it updates: When payment arrives

Two items deserve attention. The first is the customer record. It is the hardest object because both systems use it. Split the fields: contact details in the CRM, legal details and credit limit in the ERP. The second is stock. The stock a sales manager sees must be close to real time, otherwise promised goods turn out not to be on the shelf. How to organise stock accounting itself is covered in the article on warehouse inventory automation.

Storekeeper scans a carton while a sales manager on the phone waits for stock confirmation

Integration methods: which one fits when

  • API request — How it works: One system asks the other for data when needed; Best for: Showing stock or prices; Limitation: Many requests add load on both systems
  • Webhook (event notification) — How it works: A system notifies the other as soon as something changes; Best for: Deal stage, order status, payment; Limitation: If a message is lost, a retry mechanism is needed
  • Middleware (queue or integration service) — How it works: Data passes through a separate service that validates and retries; Best for: Many objects and systems; Limitation: One more component to monitor
  • File exchange — How it works: Periodic export and import of files; Best for: No API, or data changes rarely; Limitation: Long delays; errors are noticed late

Most modern CRMs offer an API and webhooks. For example, the amoCRM (Kommo) developer documentation has a dedicated section on webhooks. Every system has its own limits, though: request quotas, which fields can be transferred, access rights. Check the official documentation of your specific systems before planning the link.

A common setup in Uzbekistan is sales in amoCRM or Bitrix24 and accounting in 1C. The 1C:Enterprise platform offers HTTP services and an automatic REST (OData) interface for connecting external systems. Neither works out of the box: the interface has to be published on a web server, the right objects exposed and the specific configuration taken into account. Estimate the work on the 1C side separately from the CRM side.

In practice, methods are combined. Stock and prices use API requests or scheduled sync. Orders and payments use webhooks with retries. As data volume grows, middleware pays for itself.

Common problems and how to solve them

Duplicate customers. One customer is "Akmal aka" in the CRM and "Akmal Karimov LLC" in the ERP. The fix is a single identifier: the taxpayer identification number (STIR) for companies, and a phone number in one consistent format for individuals. Clean up both databases before integrating.

Duplicate sends. After a connection drop, one order lands in the ERP twice. The fix is a unique number for every order; the ERP refuses a second order with the same number.

Stock reservation. Two managers sell the last ten units at the same moment. The fix is to reserve goods in the ERP when an order is confirmed, with an expiry time on the reservation.

Silent failures. The integration stops working and nobody notices. A week later it turns out forty orders never reached the warehouse. The fix is an error log, an automatic alert to a named owner and a daily reconciliation report.

Mismatched statuses. What does "Closed" in the CRM mean to the ERP: paid or shipped? The fix is a status table, agreed in writing, mapping each CRM stage to an ERP event.

Accountant circles a mismatched invoice line and shows it to the sales manager

Building the integration in seven steps

  1. Document the current process. Who does what, and where, from closing a deal to receiving payment. Mark every point of manual copying.
  2. Draw the map. Use the table above: object, owning system, direction, timing.
  3. Agree on identifiers and statuses. Which key links customers, products and orders, and how statuses correspond.
  4. Write a specification. For each flow: fields, rules and what happens on error. The article on writing an ERP technical specification explains how.
  5. Clean the data. Merge duplicates and standardise formats. Integrating dirty data automates the errors too.
  6. Launch in stages. Start with one flow, for example orders from CRM to ERP. Once it runs reliably, add the next.
  7. Monitor and assign an owner. The integration needs a named owner who watches the error log and approves changes.

These steps may be part of a larger project, in which case they are planned alongside the ERP implementation stages.

Pre-launch test checklist

  • ☐ A deal with a new customer closes: the customer and order appear in the ERP exactly once.
  • ☐ A deal with an existing customer: no new duplicate is created.
  • ☐ An order is created during a connection outage: it arrives exactly once after recovery.
  • ☐ A price changes in the ERP: the CRM updates within the agreed time.
  • ☐ Stock drops to zero: the sales manager sees it in the CRM.
  • ☐ An order is cancelled: the reservation in the ERP is released.
  • ☐ A partial payment arrives: the balance in the CRM is correct.
  • ☐ A return is processed: amounts match in both systems.
  • ☐ Deliberately invalid data is sent: the error is logged and the owner is alerted.
  • ☐ The daily reconciliation report shows no differences.

Test each item in a staging environment with data close to real. For the first two weeks after launch, also review the daily reconciliation by hand.

Bottom line

ERP and CRM integration looks like a technical task, but it rests on management decisions. Which system owns which data, how customers are identified, what each status means: all of this is agreed before the first line of code. Start with the map, launch one flow, make errors visible and work through the full test checklist. Then sales managers see stock, prices and balances in one place while talking to customers, and management can follow the path from deal to cash without gaps.

Frequently asked questions

Is it better to run ERP and CRM in one system or two?

Both approaches work. One system removes the integration problem but may be less convenient for the sales team. Two systems let each fit its job, but the link between them has to be built and monitored. The choice depends on how complex your sales process is and which systems are already in place.

How long does an integration take?

It depends on scope. Sending two or three objects one way, such as customers and orders, can take a few weeks. Two-way sync of prices, stock, payments and returns can take several months. The specification and the amount of testing set the timeline.

Can we use a ready-made connector?

Sometimes, especially for standard objects. But an off-the-shelf connector does not know your statuses, discount rules or how you identify customers. Check it against the same data map and test checklist you would use for a custom integration.

Can the CRM sync with a local Uzbek accounting system?

Usually yes, if the local system exposes an API or a reliable file exchange. Confirm early which documents must stay in the local accounting system for tax and e-invoicing purposes, and design the data map so those records have one clear owner.

Want sales and accounting in Uzbekistan to run as one flow?
Let's look at your current CRM and accounting setup, see which data is still copied by hand, and calmly plan the integration map and the stages of work.
Discuss your integration →

Let's work out where to start

Free consultation with a DORA specialist

Message on Telegram

Let's discuss your project

Leave your number and a specialist will get in touch.

Send a request via Telegram

Your details are used only to contact you.