The methods of data transfer from Oracle to PostgreSQL environment are considered, taking into account the step-by-step organization of actions and deter-mining the sequence of migration. The main directions for the transformation of the structure of databases, data formats and executed objects are highlighted. New methods and programs for converting the structure and formats in automatic mode are proposed. The methods of transformation of stored procedures and triggers written in procedural languages, which are PL/SQL and PL/PGSQL, are defined. For cases of possible ambiguous translation, programs have been developed that form hints that facilitate manual operation. The task of managing transactions inside stored functions in PostgreSQL is difficult. If such transactions are possible for Oracle, then in the PostgreSQL environment, it is necessary to organize them only in external code. They are usually published on computers that work directly with the database server. In this case, the division of the original function into several functions is used, each of which is responsible for its own transaction block. Each such function is called from external code. The issues of changing software on nodes directly connected (interfaced) with the database server and the issues of minimizing stops during migration are considered, which makes it possible to carry out migration for geographically distributed and round-the-clock functioning objects. Examples of changes in the speed of execution of requests before and after migration for various types of systems are given.