Year-End Results: Replacing Foreign Software Stacks With Russian Platforms

Major Facilities Complete the Transition

Over the past year, several large industrial projects and nuclear sites fully migrated critical subsystems to domestic solutions. This involved comprehensive migration of databases, gateways, and integration modules. End users continued to work in familiar interfaces, avoiding disruptions to day-to-day operations.

These transitions followed a pre-tested methodology: compatibility checks, development of adapters, data migration in test environments, and phased switchover to production systems.

What Changed Inside Control Systems

The changes focused on replacing core technological components, including storage systems, server-based database management systems, and integration platforms. The automated process control system retained its operational logic, regulations, and scenarios, but now runs on domestic cores and certified modules.

From a technical standpoint, this was achieved through proxy layers and adapters that translated legacy requests into a new API. The result of this painstaking work was full compatibility without losses in performance or reliability.

Operational and Maintenance Impact

Migration to Russian technologies reduced operational risks. Dependence on foreign licences and remote vendor support declined, while local teams gained access to core components and could implement fixes and updates more rapidly. Incident response times improved, and system downtime was reduced.

To accelerate the development and deployment of such products in industry, industrial competence centres have been established, as I would like to remind you. They brought together major customers and software developers to turn in-demand initiatives into reality, including with state support. Many of the corporate software products I mentioned are precisely the result of these efforts. They have also led to the emergence of other applied solutions, for example, baggage tracking systems, operational transport management systems for Russian Railways, aviation service platforms, and much more

Mikhail Mishustin

Chairman of the Government of the Russian Federation

The economic impact was reflected in lower maintenance and support costs. Local suppliers began competing for service contracts, reducing total cost of ownership and stimulating the domestic software market. Some facilities also reported productivity gains after optimisation for the new database platforms.

Regulation, Standards, and Workforce Development

The experience of 2025 demonstrated that technical migration alone is insufficient without a unified regulatory framework. New requirements were introduced for component certification and data exchange procedures. To ensure sustainable migration, sector-wide working groups were established to align exchange standards and validation methodologies.

Workforce development proved equally critical. Retraining programmes for engineers and administrators were launched, alongside courses on domestic database systems and cybersecurity. Without these measures, scaling the transition would not have been possible.

Outlook for 2026 and Sector Significance

In 2026, large-scale replication of proven practices is expected, including migration of secondary sites, rollout of standardised migration templates, and the creation of competence centres. This should make transitions faster and less costly for mid-sized enterprises.

By 2025, software import substitution had moved beyond declarations into practical implementation. A technological foundation has been established that underpins the resilience of critical systems and the ability to export finished solutions. Maintaining momentum, advancing standards, and continuing specialist training will now be essential to ensure the new platform operates reliably and delivers a lasting competitive advantage.