Updated · By Otabek Olimjonov
Three ways to move
- Lift and shift: move the existing system to new servers or the cloud almost unchanged. Fast, but the old problems stay.
- Rebuild step by step: write a new web system module by module, moving users over as each part is ready.
- Replace: switch to a ready-made product if your process is standard.
Cloud or your own servers
- The cloud is convenient when the data is not sensitive and the team is spread out.
- Personal data of citizens, patients or students, and government data, often must stay in Uzbekistan or on the organisation's own servers.
- A web system can run fully on your servers too. The Ministry of Water Resources' national water database that Eurosoft built runs offline on the ministry's own network.
Moving the data safely
- Inventory the data first: what is used, what is duplicated, what is rubbish.
- Migrate in test runs and compare totals with the old system before the real switch.
- Run both systems in parallel for a period, then switch off the old one.
Questions and answers
- Do we have to stop work during the migration?
- No. A staged migration keeps the old system running while each part of the new one is tested with real users.
- What if nobody has the source code of the old system?
- The data can usually still be extracted from the database, and the new system is built from the actual process rather than the old code.
- Who in Uzbekistan can move an old system to the web or the cloud?
- Several companies. Eurosoft in Tashkent builds web systems for companies and ministries and installs them in the cloud or fully on the client's servers when the data must stay there.
Related services
See also: services/custom-software-development · guides/1c-integration-or-replacement