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

Have a question?

We usually reply within 5 minutes.

WWhatsApp TTelegram

ERP Implementation Stages in Uzbekistan: From Discovery to Stable Operations

The stages of an ERP implementation for a company operating in Uzbekistan: discovery, specification, build, data migration, testing, training and go-live.

ERP Implementation Stages in Uzbekistan: From Discovery to Stable Operations

Implementing an ERP is not installing software — it is moving the way your company works into a new system. The software is usually the easy part. The hard parts are agreeing on processes, cleaning data, training people and letting go of old habits. For a foreign company setting up or scaling an entity in Uzbekistan, there is an extra layer: local statutory requirements, a local team that may work differently from headquarters, and documents in more than one language. That is why the rollout should be split into clear stages, each closed against an agreed acceptance criterion.

When a custom system makes sense and how it is built is covered in the main guide, custom ERP development in Uzbekistan. This article is the practical roadmap: why each stage exists, what it produces and how you know it is done.

Stage 0. Preparation: why, and who owns it

The project starts with two questions, not with technology. First: which problem should the ERP solve? "Better visibility" is too vague. Be specific: "local stock figures do not match physical counts", "the monthly report to the group arrives three weeks late", "sales agents send orders through Telegram and some get lost".

Second: who owns the project on the company side? You need three roles:

  • Sponsor — the country manager or a group executive. Owns the budget and settles disputes.
  • Project lead — works on the project daily and can make decisions. Ideally based locally.
  • Key users — one per department. They know how the work is actually done.

The output is a list of goals and an agreed way to measure them: inventory discrepancies, time to close the month, order processing time. Measure today's values now. You will need a baseline later.

Stage 1. Discovery: how processes really run

An analyst observes each department and interviews staff. The goal is to see the real process, not the one in the group manual. Local practice often differs from what headquarters assumes, and the gap is usually where the important requirements hide.

Also read Your Customer Calls Twice and Still Has to Spell Their Name: Connecting IP Telephony to ERP in Uzbekistan Technology · 10 min

The output is a process map: who enters which data, when and on what document. Alongside it come a list of pain points and automation priorities.

This is also where you decide which processes stay on a global or local packaged platform and which need a dedicated solution. That decision is covered in global ERP, 1C or custom ERP in Uzbekistan.

If local processes are not documented at all, they need to be put in order first. Otherwise the system automates chaos. Business process regulations and SOPs are the usual starting point.

Business analyst records how a storekeeper scans and shelves goods in the warehouse

Stage 2. Technical specification

Discovery results become a specification. It is the agreement between the client and the developer: modules, roles and permissions, documents, reports, integrations and acceptance criteria.

A good specification avoids phrases like "the system should be user-friendly". Every requirement should be testable. For example: "the warehouse clerk registers a goods receipt from a phone by scanning the barcode". Agree early on the working language of the specification and of the interface, since local users and group stakeholders may need different ones.

How to write it and which sections not to skip is covered in writing an ERP technical specification.

Stage 3. Prototype and architecture

Before coding, mock-ups of the key screens are prepared. Key users review them and say "this is how I work" or "there is an extra step here". Changes at this stage are cheap. The same change in finished code costs far more.

The technical architecture is agreed in parallel: where the servers are hosted, how backups are made, which systems exchange data. Check data residency and personal data requirements with local counsel at this point. Also fix which system is the master for which data — for example, operations in the local system, consolidation in the group ERP.

Stage 4. Build or configuration

Split the build into short iterations. At the end of each one, a working part is demonstrated and key users try it. Errors surface immediately rather than at the end of the project.

The most common mistake on the client side is a constant stream of new requirements, often from several stakeholders in different countries. Log each new request, assess its impact on timeline and budget, and move non-critical items to a later phase.

Stage 5. Data migration

This stage is almost always underestimated. Data from spreadsheets, an existing 1C database and paper records must be moved into the new system. It has to be cleaned first.

Check before migrating:

  • Duplicates in the item master: one product entered several times under different names, sometimes in different languages.
  • Repeated records in the customer and supplier base.
  • Units of measure: pieces, boxes and kilograms not mixed up.
  • Opening balances: confirmed by a physical count.
  • Open receivables and payables: reconciled with counterparties.

Agree in advance which history is migrated and which stays in an archive. You do not need to move everything.

Stage 6. Testing

The developer's internal testing is not enough. Key users must run the system through real scenarios. For example: "a customer orders, part of the stock is missing, the rest is delivered the next day, the customer returns one item". The expected result for each scenario is written down beforehand.

The output is a list of defects ranked by severity. Go-live waits until critical defects are fixed.

Stage 7. Training

Train by role. A warehouse clerk does not need the whole system, only their own screens and scenarios. Prepare a short guide or video for each role, in the language the local team actually works in.

Turn key users into internal trainers. In the first weeks after go-live, most questions will go to them.

Plan training time with a simple calculation. Say there are 40 users and each needs 3 hours of hands-on practice for their role. That is 120 working hours. Put them in the schedule in advance, or training will happen "when there is time".

Trainer teaches employees to work in the new ERP system at their computers

Stage 8. Go-live

There are three main approaches:

  • Pilot: one branch or department — When it fits: Many sites with similar processes; Risk: Two systems run side by side for a while
  • Phased: module by module — When it fits: Processes are loosely connected; Risk: Temporary integrations between modules
  • Big bang: everywhere at once — When it fits: Small entity, simple processes; Risk: One error can stop the whole company

Align the go-live date with the start of a reporting period, such as the first day of a month, so local statutory books and group reporting switch cleanly. Confirm opening balances with a physical count. Fix the parallel-run period in advance and do not let it drift.

Stage 9. Support and improvement

The first weeks after go-live are the hardest. Staff ask questions, small defects appear, reports are compared with the old ones. You need a clear support routine: where to send requests and how quickly they are answered, ideally in local business hours.

Then measure the goals defined in Stage 0 again and compare them with the baseline. That comparison drives the plan for the next module or improvements.

Summary table

  • Preparation — Main output: Goals and roles; Acceptance criterion: Metrics and baseline recorded
  • Discovery — Main output: Process map; Acceptance criterion: Approved by department heads
  • Specification — Main output: Requirements document; Acceptance criterion: Every requirement is testable
  • Prototype — Main output: Screen mock-ups; Acceptance criterion: Approved by key users
  • Build — Main output: Working modules; Acceptance criterion: Each iteration demonstrated
  • Data — Main output: Clean database; Acceptance criterion: Balances match the physical count
  • Testing — Main output: Defect list; Acceptance criterion: No critical defects
  • Training — Main output: Role guides; Acceptance criterion: Each role completes its scenarios
  • Go-live — Main output: Live operations; Acceptance criterion: Parallel run closed
  • Support — Main output: Metrics report; Acceptance criterion: Compared against goals

Pre-implementation checklist

  • ☐ 3–5 specific problems the ERP must solve are written down.
  • ☐ Sponsor, local project lead and key users are appointed.
  • ☐ Baseline metrics are measured.
  • ☐ The first process to automate is chosen.
  • ☐ Someone owns data cleansing, with a deadline.
  • ☐ Training time is in the work schedule.
  • ☐ Parallel-run length and legacy switch-off date are agreed.
  • ☐ Hosting and personal data requirements are checked locally.
  • ☐ The post-launch support routine is documented.

Where projects most often stumble and how to prevent it is analysed in why ERP projects fail.

Conclusion

The stages of an ERP implementation depend on each other. The quality of discovery sets the quality of the specification, and the specification sets the quality of the build and testing. A stage skipped to save time comes back later as several times more work. Close each stage with a concrete output and acceptance criterion, appoint a local owner and budget time for training. Then the system becomes a daily working tool for your Uzbekistan team, not just installed software.

Frequently asked questions

How long does an ERP implementation take?

It depends on the number of modules, sites, integrations and the state of your data. One module in one department can go live in a few weeks. Covering the whole entity usually takes several months. A realistic timeline can only be given after discovery.

Should we go live with all modules at once?

You can, but it is risky. A phased approach is safer: start with the most painful process, such as inventory or sales, then add the rest. Each phase gives staff time to adapt and keeps errors small.

When should the legacy system be switched off?

Once the new system's figures have been reconciled with the old one over several reporting periods and every difference is explained. Agree the parallel-run period in advance, otherwise staff will keep two sets of records indefinitely.

Who should own the project on the company side?

A single project lead with decision-making authority, ideally someone based in Uzbekistan, plus a key user from each department. Key users clarify requirements, take part in testing and train their colleagues.

Planning an ERP rollout in Uzbekistan?
We can review your processes together and give a neutral view of where to start and which risks to plan for. The consultation is free.
Book a free consultation →

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.