Method and device for migrating data on cross-system interface view

Abstract

The invention provides a data migration method and device on a cross-system interface view. The method comprises the following steps: receiving a migration instruction input to an interface view of a source system by a user, and determining a first field needing to be migrated and a second field related to the first field on the interface view of the source system based on the migration instruction; determining identification codes of the first field and the second field, and respectively determining a third field and a fourth field on the interface view of the target system based on the identification codes of the first field and the second field; reading data of the first field and the second field from the source system through the source script; and respectively inserting the data of the first field and the second field into a third field and a fourth field in the target system by utilizing the target interface. By adopting the technical means, the problem that data migration on a cross-system interface view cannot be carried out in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the technical field of data migration, and in particular to a method and device for data migration on a cross-system interface view. Background Art

[0002] Existing cross-system data migration technologies are all for the data itself, which belongs to the migration at the system data layer. There is currently no method for migration at the system interface layer. This is because of the following reasons: the system interface layer does not focus on the data itself, but only on the data name; the system interface is set in advance, and migration at the system interface layer will inevitably involve changes in the layout of the system interface; the same data on different system interfaces may use different names (fields), so the existing cross-system data migration technology cannot be directly used for data migration on the interface view across systems. Summary of the invention

[0003] In view of this, an embodiment of the present application provides a method, device, electronic device and computer-readable storage medium for migrating data on a cross-system interface view to solve the problem that data migration on a cross-system interface view cannot be performed in the prior art.

[0004] According to a first aspect of an embodiment of the present application, a method for migrating data on an interface view across systems is provided, comprising: receiving a migration instruction input by a user into an interface view of a source system, and determining a first field and a second field related to the first field on the interface view of the source system that need to be migrated based on the migration instruction; determining identification codes of the first field and the second field, and determining a third field and a fourth field on the interface view of the target system based on the identification codes of the first field and the second field, respectively; reading data of the first field and the second field from the source system through a source script; and inserting the data of the first field and the second field into the third field and the fourth field in the target system, respectively, using a target interface.

[0005] According to a second aspect of an embodiment of the present application, a data migration device on a cross-system interface view is provided, comprising: a receiving module, configured to receive a migration instruction input by a user into the interface view of a source system, and determine a first field and a second field related to the first field on the interface view of the source system that need to be migrated based on the migration instruction; a determining module, configured to determine identification codes of the first field and the second field, and determine a third field and a fourth field on the interface view of the target system based on the identification codes of the first field and the second field, respectively; a reading module, configured to read data of the first field and the second field from the source system through a source script; and an inserting module, configured to use a target interface to insert the data of the first field and the second field into the third field and the fourth field in the target system, respectively.

[0006] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0007] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0008] Compared with the prior art, the embodiments of the present application have the following beneficial effects: receiving a migration instruction input by a user into the interface view of the source system, determining the first field on the interface view of the source system that needs to be migrated and the second field related to the first field based on the migration instruction; determining the identification codes of the first field and the second field, and determining the third field and the fourth field on the interface view of the target system based on the identification codes of the first field and the second field; reading the data of the first field and the second field from the source system through a source script; and inserting the data of the first field and the second field into the third field and the fourth field in the target system respectively using the target interface. The above technical means can be used to solve the problem in the prior art that data migration on a cross-system interface view cannot be performed, and then a method for data migration on a cross-system interface view is provided to avoid technicians manually entering or modifying data on the interface view, thereby improving efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0010] Figure 1 It is a flowchart of a data migration method on a cross-system interface view provided by an embodiment of the present application;

[0011] Figure 2 It is a flowchart of another data migration method on a cross-system interface view provided in an embodiment of the present application;

[0012] Figure 3 It is a structural schematic diagram of a data migration device on a cross-system interface view provided by an embodiment of the present application;

[0013] Figure 4 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0014] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0015] A method and device for data migration on a cross-system interface view according to an embodiment of the present application will be described in detail below with reference to the accompanying drawings.

[0016] Figure 1 It is a flowchart of a data migration method on a cross-system interface view provided in an embodiment of the present application. Figure 1 The data migration method on the cross-system interface view can be executed by a computer or a server, or software on the computer or the server. Figure 1 As shown, the data migration method on the cross-system interface view includes:

[0017] S101, receiving a migration instruction input by a user on an interface view of a source system, and determining a first field and a second field related to the first field on the interface view of the source system that need to be migrated based on the migration instruction;

[0018] S102, determining identification codes of the first field and the second field, and determining a third field and a fourth field on the interface view of the target system based on the identification codes of the first field and the second field respectively;

[0019] S103, reading data of the first field and the second field from the source system through a source script;

[0020] S104, using the target interface to insert the data of the first field and the second field into the third field and the fourth field of the target system respectively.

[0021] The migration instruction may describe the field to be migrated, or the field's information, or the information related to the field, or the information related to the field's information. The first field to be migrated on the interface view of the source system is determined based on the migration instruction. The field related to the first field is used as the second field.

[0022] For example, the embodiment of the present application is for the migration of work order data. The fields of the work order data include the work order number, work order status, creation time, work order type, creator, creation time, creation location, handler, finisher, dispatcher, etc. For example, if the first field is the work order number, the second field can be determined by calculating the similarity with the work order number, or directly taking the other fields of the work order to which the first field belongs as the second field, and then the entire work order is migrated. Because different systems may have different fields for describing the same data, for example, the work order number of the source system may be the work order number in the target system, and the creator of the source system may be the initiator in the target system, etc. The embodiment of the present application matches the fields that have a mapping relationship between the source system and the target system through identification codes.

[0023] Taking the example of the work order number in the source system corresponding to the work order number in the target system, when performing data migration, the data of the work order number field is read through the source script, and the data of the work order number field is inserted into the work order number field in the target system using the target interface. The source script is a script file written for the source system and is used to read data from the source system. The target interface is an interface set on the target system and is used to insert embedded data into the corresponding field. The method of generating the source script and the target interface is a common method and will not be repeated here.

[0024] According to the technical solution provided by the embodiment of the present application, a migration instruction input by a user into the interface view of the source system is received, and a first field on the interface view of the source system that needs to be migrated and a second field related to the first field are determined based on the migration instruction; identification codes of the first field and the second field are determined, and the third field and the fourth field on the interface view of the target system are determined based on the identification codes of the first field and the second field; data of the first field and the second field are read from the source system through a source script; and the data of the first field and the second field are inserted into the third field and the fourth field in the target system respectively using the target interface. The above-mentioned technical means can solve the problem in the prior art that data migration on a cross-system interface view cannot be performed, and then a method for data migration on a cross-system interface view is provided to avoid technicians manually entering or modifying data on the interface view, thereby improving efficiency.

[0025] In an optional embodiment, data of the first field and the second field are read from the source system through a source script, wherein the data of the field read carries an identification code of the field; the corresponding field in the target system is determined according to the identification code carried by each piece of data, and the data is inserted into the corresponding field in the target system using the target interface.

[0026] Figure 2 FIG. 1 is a flow chart of another method for data migration on a cross-system interface view provided in an embodiment of the present application. Figure 2 As shown, the method includes:

[0027] S201, reading data of a first field from a source system through a source script;

[0028] S202, inserting the data of the first field into the third field in the target system using the target interface;

[0029] S203, when there are multiple second fields, each second field corresponds to a fourth field, and the following loop is executed:

[0030] S204, determining whether i is greater than N, where i is the sequence number of the second field and the fourth field, and N is the number of the second field or the fourth field;

[0031] S205, when i is greater than N, it is determined that the data to be migrated for the migration instruction is completed, and the loop ends;

[0032] S206, when i is not greater than N, reading the data of the i-th second field from the source system through the source script;

[0033] S207, inserting the data of the i-th second field into the i-th fourth field in the target system by using the target interface;

[0034] S208, update i with the value of i plus 1.

[0035] There are N second fields in total. When i is N+1, it indicates that all the data in the second fields have been migrated and the loop ends. Otherwise, the data in the i-th second field is migrated to the i-th fourth field in the target system, and the i-th second field corresponds to the i-th fourth field.

[0036] Furthermore, before using the target interface to insert the data of the first field and the second field into the third field and the fourth field in the target system respectively, the method also includes: determining the positional relationship between the first field and the second field on the interface view of the source system; and adjusting the position of the fourth field on the interface view of the target system based on the positional relationship and the position of the third field on the interface view of the target system.

[0037] Because the migration of data on the interface view should also consider the position of the data on the interface view, in order to maintain the layout of the first field and the second field on the interface view of the source system, the position of the third field on the interface view of the target system and the position of the fourth field on the interface view of the target system should satisfy the position relationship, so the position of the fourth field is adjusted.

[0038] Furthermore, before using the target interface to insert the data of the first field and the second field into the third field and the fourth field in the target system respectively, the method also includes: when there are multiple second fields, each second field corresponds to a fourth field; determining the position relationship between the first field and each second field and the position relationship between each field and other second fields on the interface view of the source system; based on the position of the third field on the interface view of the target system, the position relationship between the first field and each second field, and the position relationship between each field and other second fields, adjust the position of each fourth field on the interface view of the target system.

[0039] For example, if there are three second fields, the first second field is located below the first field on the source system interface view, the second second field is located below the first second field, and the third second field is located below the second second field. The second field and the fourth field correspond in order, so on the target system interface view, from top to bottom, they are the third field, the first fourth field, the second fourth field, and the third fourth field.

[0040] Furthermore, after determining the identification codes of the first field and the second field, and respectively determining the third field and the fourth field on the interface view of the target system based on the identification codes of the first field and the second field, the method also includes: when there are multiple second fields, each second field corresponds to a fourth field; dividing all second fields into multiple batches, wherein each batch contains multiple second fields; performing the following operations on each batch in sequence according to the order of each batch: reading the data of each second field in the batch from the source system through the source script; and inserting the data of each second field in the batch into the fourth field corresponding to each second field in the batch in the target system using the target interface.

[0041] When there are too many fields to be migrated, all second fields can be divided into multiple batches, and correspondingly all fourth fields can be divided into multiple batches, and the data of each second field in a batch is migrated to the fourth field corresponding to each second field in the target system.

[0042] Furthermore, before determining the identification codes of the first field and the second field and respectively determining the third field and the fourth field on the interface view of the target system based on the identification codes of the first field and the second field, the method also includes: generating identification codes for each field in the source system; determining the fields in the target system corresponding to each field in the source system; and using the identification codes of each field in the source system as the identification codes of the corresponding fields in the target system.

[0043] Furthermore, after reading the data of the first field and the second field from the source system through the source script, the method also includes: determining the source format of the data stored in the source system and the target format of the data stored in the target system; converting the data of the first field and the second field into the target format; and using the target interface to insert the converted data of the first field and the second field into the third field and the fourth field in the target system respectively.

[0044] The source format is the format in which data is stored in the source system, and the target format is the format in which data is stored in the target system. For example, the source system is a MySQL system, and the target system is a Redis system. If the source format is MySQL and the target format is Redis, then the data of the first field and the second field need to be converted to Redis format data. The above technical means can be used to achieve data migration between systems with different formats.

[0045] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present application, which will not be described one by one here.

[0046] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0047] Figure 3 Schematic diagram of a data migration device on a cross-system interface view provided by an embodiment of the present application. Figure 3 As shown, the data migration device on the cross-system interface view includes:

[0048] The receiving module 301 is configured to receive a migration instruction input by a user into an interface view of a source system, and determine a first field and a second field related to the first field on the interface view of the source system that need to be migrated based on the migration instruction;

[0049] The determination module 302 is configured to determine the identification codes of the first field and the second field, and determine the third field and the fourth field on the interface view of the target system based on the identification codes of the first field and the second field respectively;

[0050] A reading module 303 is configured to read data of the first field and the second field from a source system through a source script;

[0051] The inserting module 304 is configured to use the target interface to insert the data of the first field and the second field into the third field and the fourth field in the target system respectively.

[0052] The migration instruction may describe the field to be migrated, or the field's information, or the information related to the field, or the information related to the field's information. The first field to be migrated on the interface view of the source system is determined based on the migration instruction. The field related to the first field is used as the second field.

[0053] For example, the embodiment of the present application is for the migration of work order data. The fields of the work order data include the work order number, work order status, creation time, work order type, creator, creation time, creation location, handler, finisher, dispatcher, etc. For example, if the first field is the work order number, the second field can be determined by calculating the similarity with the work order number, or directly taking the other fields of the work order to which the first field belongs as the second field, and then the entire work order is migrated. Because different systems may have different fields for describing the same data, for example, the work order number of the source system may be the work order number in the target system, and the creator of the source system may be the initiator in the target system, etc. The embodiment of the present application matches the fields that have a mapping relationship between the source system and the target system through identification codes.

[0054] Taking the example of the work order number in the source system corresponding to the work order number in the target system, when performing data migration, the data of the work order number field is read through the source script, and the data of the work order number field is inserted into the work order number field in the target system using the target interface. The source script is a script file written for the source system and is used to read data from the source system. The target interface is an interface set on the target system and is used to insert embedded data into the corresponding field. The method of generating the source script and the target interface is a common method and will not be repeated here.

[0055] According to the technical solution provided by the embodiment of the present application, a migration instruction input by a user into the interface view of the source system is received, and a first field on the interface view of the source system that needs to be migrated and a second field related to the first field are determined based on the migration instruction; identification codes of the first field and the second field are determined, and the third field and the fourth field on the interface view of the target system are determined based on the identification codes of the first field and the second field; data of the first field and the second field are read from the source system through a source script; and the data of the first field and the second field are inserted into the third field and the fourth field in the target system respectively using the target interface. The above-mentioned technical means can solve the problem in the prior art that data migration on a cross-system interface view cannot be performed, and then a method for data migration on a cross-system interface view is provided to avoid technicians manually entering or modifying data on the interface view, thereby improving efficiency.

[0056] In some optional embodiments, the determination module 302 is also configured to read data of the first field and the second field from the source system through a source script, wherein the data of the read field will carry an identification code of the field; determine the corresponding field in the target system according to the identification code carried by each piece of data, and insert the data into the corresponding field in the target system using the target interface.

[0057] In some optional embodiments, the determination module 302 is also configured to read the data of the first field from the source system through the source script; insert the data of the first field into the third field in the target system using the target interface; when there are multiple second fields, each second field corresponds to a fourth field, and execute the following loop: determine whether i is greater than N, where i is the sequence number of the second field and the fourth field, and N is the number of second fields or fourth fields; when i is greater than N, determine the data that needs to be migrated to complete the migration instruction, and end the loop; when i is not greater than N, read the data of the i-th second field from the source system through the source script; use the target interface to insert the data of the i-th second field into the i-th fourth field in the target system; update i with the value of i plus 1.

[0058] There are N second fields in total. When i is N+1, it indicates that all the data in the second fields have been migrated and the loop ends. Otherwise, the data in the i-th second field is migrated to the i-th fourth field in the target system, and the i-th second field corresponds to the i-th fourth field.

[0059] In some optional embodiments, the insertion module 304 is also configured to determine the positional relationship between the first field and the second field on the interface view of the source system; and adjust the position of the fourth field on the interface view of the target system based on the positional relationship and the position of the third field on the interface view of the target system.

[0060] Because the migration of data on the interface view should also consider the position of the data on the interface view, in order to maintain the layout of the first field and the second field on the interface view of the source system, the position of the third field on the interface view of the target system and the position of the fourth field on the interface view of the target system should satisfy the position relationship, so the position of the fourth field is adjusted.

[0061] In some optional embodiments, the insertion module 304 is also configured to, when there are multiple second fields, each second field corresponds to a fourth field; determine the positional relationship between the first field and each second field and the positional relationship between each field and other second fields on the interface view of the source system; and adjust the position of each fourth field on the interface view of the target system based on the position of the third field on the interface view of the target system, the positional relationship between the first field and each second field, and the positional relationship between each field and other second fields.

[0062] For example, if there are three second fields, the first second field is located below the first field on the source system interface view, the second second field is located below the first second field, and the third second field is located below the second second field. The second field and the fourth field correspond in order, so on the target system interface view, from top to bottom, they are the third field, the first fourth field, the second fourth field, and the third fourth field.

[0063] In some optional embodiments, the insertion module 304 is also configured to, when there are multiple second fields, each second field corresponds to a fourth field; divide all second fields into multiple batches, wherein each batch contains multiple second fields; and perform the following operations on each batch in sequence according to the order of each batch: read the data of each second field in the batch from the source system through the source script; and insert the data of each second field in the batch into the fourth field corresponding to each second field in the batch in the target system using the target interface.

[0064] When there are too many fields to be migrated, all second fields can be divided into multiple batches, and correspondingly all fourth fields can be divided into multiple batches, and the data of each second field in a batch is migrated to the fourth field corresponding to each second field in the target system.

[0065] In some optional embodiments, the determination module 302 is further configured to generate an identification code for each field in the source system; determine the field in the target system corresponding to each field in the source system; and use the identification code of each field in the source system as the identification code of the corresponding field in the target system.

[0066] In some optional embodiments, the insertion module 304 is also configured to determine the source format of the data stored in the source system and the target format of the data stored in the target system; convert the data of the first field and the second field into the target format; and use the target interface to insert the converted data of the first field and the second field into the third field and the fourth field in the target system respectively.

[0067] The source format is the format in which data is stored in the source system, and the target format is the format in which data is stored in the target system. For example, the source system is a MySQL system, and the target system is a Redis system. If the source format is MySQL and the target format is Redis, then the data of the first field and the second field need to be converted to Redis format data. The above technical means can be used to achieve data migration between systems with different formats.

[0068] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0069] Figure 4 Schematic diagram of an electronic device 4 provided in an embodiment of the present application. Figure 4 As shown, the electronic device 4 of this embodiment includes: a processor 401, a memory 402, and a computer program 403 stored in the memory 402 and executable on the processor 401. When the processor 401 executes the computer program 403, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor 401 executes the computer program 403, the functions of the modules / units in the above-mentioned device embodiments are implemented.

[0070] The electronic device 4 may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device. The electronic device 4 may include, but is not limited to, a processor 401 and a memory 402. Those skilled in the art will appreciate that Figure 4 The electronic device 4 is merely an example and does not limit the electronic device 4 , and may include more or less components than those shown in the figure, or different components.

[0071] The processor 401 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0072] The memory 402 may be an internal storage unit of the electronic device 4, for example, a hard disk or memory of the electronic device 4. The memory 402 may also be an external storage device of the electronic device 4, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 4. The memory 402 may also include both an internal storage unit and an external storage device of the electronic device 4. The memory 402 is used to store computer programs and other programs and data required by the electronic device.

[0073] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0074] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, and the computer program code may be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electric carrier signals and telecommunication signals.

[0075] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A data migration method on a cross-system interface view, characterized in that: include: receiving a migration instruction input by a user into an interface view of a source system, and determining a first field and a second field related to the first field on the interface view of the source system that need to be migrated based on the migration instruction; Determine identification codes of the first field and the second field, and determine a third field and a fourth field on the interface view of the target system based on the identification codes of the first field and the second field respectively; Reading data of the first field and the second field from the source system through a source script; The data of the first field and the second field are respectively inserted into the third field and the fourth field in the target system using a target interface.

2. The method according to claim 1, characterized in that After determining the identification codes of the first field and the second field, and determining the third field and the fourth field on the interface view of the target system based on the identification codes of the first field and the second field, respectively, the method further includes: Reading data of the first field from the source system through the source script; Using the target interface, inserting the data of the first field into a third field in the target system; When there are multiple second fields, each second field corresponds to a fourth field, and the following loop is executed: Determine whether i is greater than N, where i is the sequence number of the second field and the fourth field, and N is the number of the second field or the fourth field; When i is greater than N, it is determined that the data required to be migrated for the migration instruction is completed, and the loop ends; When i is not greater than N, reading data of the i-th second field from the source system through the source script; Using the target interface, inserting the data of the i-th second field into the i-th fourth field in the target system; Update i with the value of i plus 1.

3. The method according to claim 1, characterized in that: Before inserting the data of the first field and the second field into the third field and the fourth field of the target system respectively using the target interface, the method further includes: Determine a positional relationship between the first field and the second field on an interface view of the source system; The position of the fourth field on the interface view of the target system is adjusted based on the position relationship and the position of the third field on the interface view of the target system.

4. The method according to claim 1, characterized in that Before inserting the data of the first field and the second field into the third field and the fourth field of the target system respectively using the target interface, the method further includes: When there are multiple second fields, each second field corresponds to a fourth field; Determine the positional relationship between the first field and each second field and the positional relationship between each field and other second fields on the interface view of the source system; The positions of the fourth fields on the interface view of the target system are adjusted based on the position of the third field on the interface view of the target system, the positional relationship between the first field and each second field, and the positional relationship between each field and other second fields.

5. The method according to claim 1, characterized in that: After determining the identification codes of the first field and the second field, and determining the third field and the fourth field on the interface view of the target system based on the identification codes of the first field and the second field, respectively, the method further includes: When there are multiple second fields, each second field corresponds to a fourth field; Dividing all second fields into a plurality of batches, wherein each batch contains a plurality of second fields; Perform the following operations on each batch in the order of each batch: Reading data of each second field in the batch from the source system through the source script; The target interface is used to insert the data of each second field in the batch into the fourth field corresponding to each second field in the batch in the target system.

6. The method according to claim 1, characterized in that Before determining the identification codes of the first field and the second field, and respectively determining the third field and the fourth field on the interface view of the target system based on the identification codes of the first field and the second field, the method further includes: Generate identification codes for each field in the source system; Determine the fields in the target system corresponding to each field in the source system; The identification code of each field in the source system is used as the identification code of the corresponding field in the target system.

7. The method according to claim 1, characterized in that After reading the data of the first field and the second field from the source system through a source script, the method further includes: Determining a source format of data stored in the source system and a target format of data stored in the target system; converting the data of the first field and the second field into the target format; The target interface is used to insert the converted data of the first field and the second field into the third field and the fourth field of the target system respectively.

8. A data migration device on a cross-system interface view, characterized in that: include: A receiving module, configured to receive a migration instruction input by a user into an interface view of a source system, and determine a first field and a second field related to the first field on the interface view of the source system that need to be migrated based on the migration instruction; a determination module configured to determine identification codes of the first field and the second field, and to determine a third field and a fourth field on the interface view of the target system based on the identification codes of the first field and the second field; A reading module, configured to read data of the first field and the second field from the source system through a source script; The insertion module is configured to use a target interface to insert the data of the first field and the second field into the third field and the fourth field in the target system respectively.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images