A data migration method, apparatus, device and readable storage medium

Abstract

The present application discloses a data migration method, apparatus, device and readable storage medium, which are applied to the field of data migration. The method includes: obtaining and determining the migration order of each merchant in the old system according to the business volume of each merchant in the old system; migrating the data of each merchant in the old system to the new system according to the migration order; when there are multiple solution integrations during the migration of each merchant from the old system to the new system, splitting the data in the multiple solutions into modules; taking the same modules in the different solutions after splitting as common modules and the different modules as separate modules; merging the data in the common modules that meet the merging conditions to obtain merged data; migrating the data of the separate modules, the merged data and the unmerged data in the common modules from the old system to the new system. The present application can reduce the data migration risk; and can also be completed when the data migration involves multiple solutions.

Description

Technical Field

[0001] This application relates to the field of data migration, and particularly to a data migration method, apparatus, device, and readable storage medium. Background Art

[0002] When the system undergoes a disruptive upgrade and completely abandons the old system and uses the new system, it is necessary to migrate the data of the old system to the new system. The traditional data migration method is to directly migrate all the data in the old system to the new system. Then, when the new system is not stable enough or there are problems with the new system, the data will be disordered or even lost. Therefore, the traditional data migration method has a high risk.

[0003] Moreover, when the system is upgraded, it also involves the merger of cross-solutions. For example, before, the same merchant used two systems for retail and mall, and after the system upgrade, the new system can include the functions of retail and mall. At this time, it is necessary to integrate the data of the two systems. For example, for package data and user data, the same customer (with the same mobile phone number) should have two user data in the previous two systems, and then when migrated to the new system, they will be merged into one user data.

[0004] Therefore, the traditional data migration method has a relatively high risk and does not support the data fusion of cross-solutions. Summary of the Invention

[0005] In view of this, the purpose of this application is to provide a data migration method, apparatus, device, and readable storage medium, which solves the problems of high risk in data migration and non-support for cross-solution data fusion in the prior art.

[0006] To solve the above technical problems, this application provides a data migration method, including:

[0007] Obtain the business volume of each merchant in the old system, and sort each merchant from small to large according to the business volume to obtain the migration order of each merchant in the old system;

[0008] Migrate the data of each merchant in the old system to the new system according to the migration order;

[0009] When there is a fusion of multiple solutions during the migration of each merchant from the old system to the new system, all the data in the multiple solutions are module-split;

[0010] Take the same modules in different solutions after splitting as common modules;

[0011] Merge the data in the common modules that meet the merging conditions to obtain the merged data;

[0012] Take the different modules in the different solutions after splitting as separate modules;

[0013] Migrate the data of the separate modules, the merged data and the unmerged data in the common module from the old system to the new system.

[0014] Optionally, after taking the different modules in the different solutions after splitting as separate modules, it further includes:

[0015] Take the modules with mutual dependencies as a module group;

[0016] Correspondingly, the migrating the data of the separate modules, the merged data and the unmerged data in the common module from the old system to the new system includes:

[0017] Migrate the data of the separate modules, the merged data and the unmerged data in the common module from the old system to the new system according to the dependencies existing in the module group.

[0018] Optionally, the migrating the data of the separate modules, the merged data and the unmerged data in the common module from the old system to the new system includes:

[0019] Perform a full-scale migration of the data of the separate modules in the old system, the merged data and the unmerged data in the common module to the new system; when performing the full-scale migration, the old system is in a normal use state;

[0020] After the full-scale migration is completed, perform an incremental migration of the data of the separate modules in the old system, the merged data and the unmerged data in the common module to the new system; when performing the incremental migration, both the new system and the old system are in a stopped service state.

[0021] Optionally, after the migrating the data of the separate modules, the merged data and the unmerged data in the common module from the old system to the new system, it further includes:

[0022] Obtain the data in the old system before migration and the new system after migration, and perform data verification;

[0023] When the data verification fails, send the failure information to the terminal.

[0024] Optionally, after the when the data verification fails, send the failure information to the terminal, it further includes:

[0025] Migrate the data that failed to migrate again.

[0026] Optionally, migrating the data of each merchant in the old system to the new system according to the migration order includes:

[0027] Obtaining the merchant ID of each merchant;

[0028] Reading the data of each merchant in the old system according to the migration order and the merchant ID;

[0029] Writing the data to the corresponding position in the shared table of the new system according to the migration order and the merchant ID.

[0030] Optionally, before obtaining the business volume of each merchant in the old system, it further includes:

[0031] Setting a login interface; the login interface is used to manage user permissions;

[0032] Obtaining the permissions of the currently logged-in user through the login interface;

[0033] When the logged-in user has the permission to perform data migration, obtaining the migration task set by the logged-in user to perform data migration according to the migration task; the migration task includes migrating merchants, migration solutions, and migration time.

[0034] This application also provides a data migration device, including:

[0035] A business volume acquisition and sorting module, configured to acquire the business volume of each merchant in the old system, and sort each merchant from small to large according to the business volume to obtain the migration order of each merchant in the old system;

[0036] A first migration module, configured to migrate the data of each merchant in the old system to the new system according to the migration order;

[0037] A splitting module, configured to split all the data in the multiple solutions when there is a fusion of multiple solutions during the process of migrating each merchant from the old system to the new system;

[0038] A common module determination module, configured to use the same modules in different solutions after splitting as common modules;

[0039] A data fusion module, configured to merge the data in the common modules that meet the merging conditions to obtain merged data;

[0040] A separate module determination module, configured to use the different modules in different solutions after splitting as separate modules;

[0041] A second migration module, configured to migrate the data of the separate module, the merged data and unmerged data in the common module from the old system to the new system.

[0042] This application also provides a data migration device, including:

[0043] A memory, configured to store a computer program;

[0044] A processor, configured to implement the steps of the above data migration method when executing the computer program.

[0045] This application also provides a readable storage medium, on which a computer program is stored, and the computer program implements the steps of the above data migration method when executed by a processor.

[0046] It can be seen that in this application, by first sorting the migration order according to the business volume of each merchant on the system, migrating the merchants with small business volume first to reduce risks; if there is a cross-solution integration during the migration of merchants, then splitting the data of each solution into modules, and merging and migrating the data that can be merged in the common module, it is ensured that when the system upgrade involves multiple solutions, the system upgrade can also be completed. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the following will briefly introduce the drawings required to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of this application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained according to the provided drawings.

[0048] Figure 1 It is a flowchart of a data migration method provided by an embodiment of this application;

[0049] Figure 2 It is an example diagram of the data merging process in a cross-solution common module provided by an embodiment of this application;

[0050] Figure 3 It is an example diagram of a module-dependency acyclic directed graph provided by an embodiment of this application;

[0051] Figure 4 It is an example diagram of the data migration process provided by an embodiment of this application;

[0052] Figure 5 It is an example diagram of the solution integration process provided by an embodiment of this application;

[0053] Figure 6Schematic diagram of a data migration device provided by an embodiment of the present application;

[0054] Figure 7 Schematic diagram of a data migration device provided by an embodiment of the present application. Detailed implementation manners

[0055] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Apparently, the described embodiments are only some of the embodiments of the present application, rather than all of them. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0056] Please refer to Figure 1 , Figure 1 Flowchart of a data migration method provided by an embodiment of the present application. The method may include:

[0057] S101: Obtain the business volumes of each merchant in the old system, and sort each merchant from small to large according to the business volume to obtain the migration order of each merchant in the old system.

[0058] The execution subject of this embodiment is a terminal. This embodiment does not limit the type of the terminal, as long as it can complete the operation of data migration. For example, it may be a general-purpose terminal; or it may also be a dedicated terminal. The old system and the new system in this embodiment are for system upgrade, that is, upgrading the old system to obtain the new system. The system in this embodiment is based on the use of each merchant. For example, it may be a SAAS system (Software-as-a-Service), and the SAAS platform provider uniformly deploys the application software on its own server. Customers can order the required application software services from the manufacturer through the Internet according to their actual work needs, pay the manufacturer according to the amount and duration of the ordered services, and obtain the services provided by the SAAS platform provider through the Internet.

[0059] Further, in order to better provide a more secure upgrade experience for the merchants using the system, before obtaining the business volumes of each merchant in the old system, the following steps may further be included:

[0060] Step 61: Set up a login interface; the login interface is used to manage user permissions;

[0061] Step 62: Obtain the permissions of the currently logged-in user through the login interface;

[0062] Step 63: When the logged-in user has the permission for data migration, obtain the migration tasks set by the logged-in user to perform data migration according to the migration tasks; the migration tasks include migrating merchants, migrating solutions, and migration time.

[0063] A login interface is set on the terminal to manage the permissions of the logged-in user. Only when the logged-in user has the permission for data migration settings can they set migration tasks. The migration tasks can specifically include migrating merchants, migrating solutions, and the migration time. Obtain the business volume of the merchants to be migrated in the migration tasks, determine the migration order of the merchants to be migrated according to the business volume, and perform data migration in the migration order to complete the system upgrade of the merchants.

[0064] S102: Migrate the data of each merchant in the old system to the new system in the migration order.

[0065] Sort the merchants, upgrade the merchants with small business volume on the system first, and then upgrade the merchants with large business volume on the system. Upgrading the merchants in order is to reduce the upgrade risk. Because if all the merchants on the system are migrated to the new system at one time according to the traditional method, when the new system is unstable, the data security of all merchants cannot be guaranteed. In this embodiment, the migration is carried out in order. First, let the small merchants be upgraded. If the small merchants are upgraded normally, then the large merchants can be upgraded.

[0066] S103: When there is a fusion of multiple solutions during the process of migrating each merchant from the old system to the new system, split all the data in the multiple solutions into modules.

[0067] If the SAAS system is upgraded, usually a set of SAAS services will provide multiple solutions. If the SAAS system encounters a situation where two solutions in the old system are merged into one solution in the new system during the upgrade. For example: Using retail and mall for the same merchant are two solutions, then after the system upgrade, one solution in the new system can include the functions of retail and mall. At this time, data fusion is required. For example, package data, user data. The same customer (with the same mobile phone number) should have two user data in the previous two solutions, then it will be fused into one user data when migrated to the new system.

[0068] A solution is composed of multiple independent modules. Some of these independent modules are basic and common modules used by multiple solutions, and there are also some modules unique to a solution. Reasonable module splitting will be carried out before migration.

[0069] S104: Use the same modules in different solutions after splitting as common modules;

[0070] S105: Merge the data in the common module that meets the merging conditions to obtain the merged data;

[0071] S106: Treat the different modules in different solutions after splitting as separate modules;

[0072] Steps S104 to S106 perform module splitting on different solutions, taking the same modules in different solutions as common modules. For example, the recombination of independent modules split from two solutions, such as the user module and the package module, and these overlapping modules are common modules. If the data in the common module meets the data merging conditions, data merging can be performed; treat the different modules in different solutions as separate modules, that is, the modules unique to each solution. This embodiment does not limit the merging conditions. For example, for user merging, the mobile phone number or ID number can be used as the merging condition. You can refer to Figure 2 for the understanding of merging data, Figure 2 This is an example diagram of the data merging process in the cross-solution common module provided by the embodiment of the present application.

[0073] S107: Migrate the data of the separate modules, the merged data and the unmerged data in the common module from the old system to the new system.

[0074] Migrate the data in each module. Further, considering the relevance between modules, after treating the different modules in different solutions after splitting as separate modules, the following steps may also be included, specifically including:

[0075] Treat the modules with mutual dependency relationships as a module group;

[0076] Correspondingly, step S107 may specifically include:

[0077] Migrate the data of the separate modules, the merged data and the unmerged data in the common module from the old system to the new system according to the dependency relationships existing in the module group.

[0078] Each solution is composed of multiple modules, and there are also mutual dependencies between modules. Only after the migration of the dependent modules is completed can the migration of the subsequent modules be carried out. The principle of dependency is data or service dependency. For example, the shopping cart module must depend on the commodity module, and the points module must depend on the member module, that is, the commodity module needs to be migrated first, and then the shopping cart module; the member module needs to be migrated first, and then the points module.

[0079] For example Figure 3 as shown, Figure 3 This is an example diagram of an acyclic directed module dependency provided by the embodiment of the present application.

[0080] Further, in order to reduce the impact of system upgrade on merchants, migrating the data of the separate modules, the merged data and the unmerged data in the common module from the old system to the new system may include the following steps:

[0081] Step 31: Perform a full migration of the data of the separate modules in the old system, the merged data and the unmerged data in the common module to the new system; when performing the full migration, the old system is in a normal use state;

[0082] Step 32: After the full migration is completed, perform an incremental migration of the data of the separate modules in the old system, the merged data and the unmerged data in the common module to the new system; when performing the incremental migration, both the new system and the old system are in a shutdown state.

[0083] First, perform a full migration of the data. When performing the full migration, merchants can use the old system normally. After the full migration is completed, perform an incremental migration of the data to migrate the incremental data generated during the full migration process. When performing the incremental migration, both the new system and the old system are in a shutdown state, that is, they cannot be used. In this way, the impact time on merchants is only the time occupied by the migration of a small amount of incremental data.

[0084] Further, in order to ensure the accuracy of data migration, after migrating the data of the separate modules, the merged data and the unmerged data in the common module from the old system to the new system as described above, the following steps may further be included:

[0085] Obtain the data in the old system before migration and the data in the new system after migration, and perform data verification;

[0086] When the data verification fails, send the failure information to the terminal.

[0087] Obtain the old data before migrating the data to the old system and obtain the new data after migrating to the new system, and perform data verification on the old data and the new data to check whether there are any omissions, losses or errors in the data migration.

[0088] Further, in order to ensure that there are no omissions and losses in data migration, after sending the failure information to the terminal when the data verification fails as described above, the following steps may further be included:

[0089] Migrate the data that failed to migrate again.

[0090] Further, in order to ensure the orderliness of data migration and save data storage costs, migrating the data of each merchant in the old system to the new system according to the migration sequence as described above may include the following steps:

[0091] Obtain the merchant ID of each merchant;

[0092] Read the data of each merchant in the old system according to the migration order and merchant ID;

[0093] Write the data to the corresponding position in the shared table of the new system according to the migration order and merchant ID.

[0094] During the data migration process, it is necessary to isolate the data. There are many ways to isolate the data of multiple merchants. For example, a. Independent database mode, b. Shared database and independent table mode, c. Shared table mode. Then, the greater the independent granularity, the higher the cost, but the higher the security, and the less impact on each other among merchants. In the shared table mode, each merchant has a unique ID (identity number), and the data is isolated through this merchant ID.

[0095] Apply the data migration method provided by the embodiment of the present application. By obtaining the business volume of each merchant in the old system and sorting each merchant from small to large according to the business volume, the migration order of each merchant in the old system is obtained; migrate the data of each merchant in the old system to the new system according to the migration order; when there is a fusion of multiple solutions during the process of migrating each merchant from the old system to the new system, then split all the data in the multiple solutions into modules; regard the same modules in the split different solutions as common modules; merge the data that meets the merging conditions in the common modules to obtain the merged data; regard the different modules in the split different solutions as separate modules; migrate the data of the separate modules, the merged data and the unmerged data in the common modules from the old system to the new system. This method first sorts the migration order according to the business volume of each merchant on the system, and first migrates the merchants with small business volume to reduce the risk; if there is a cross-solution fusion during the migration of the merchants, then split the data of each solution into modules, and merge and migrate the data that can be merged in the common modules to ensure that when the system upgrade involves multiple solutions, the system upgrade can also be completed. Moreover, obtain the user login permission to ensure the security of data migration; and, in order to ensure the logic of the modules with dependencies during the migration process, set up a module group and sort the migration; and, adopt the incremental migration and full-scale migration methods for data migration to reduce the impact on merchants; and, save the data storage cost and avoid data disorder in data migration, and migrate to the shared table according to the merchant ID.

[0096] For the convenience of understanding this application, please refer specifically to Figure 4 , Figure 4The flowchart example of a data migration method provided by an embodiment of this application may specifically include: When the user clicks on the migration plan configured on the login interface to trigger, the scheduling of the first phase starts for full - volume migration. The data of the old system is pulled in a full - volume rolling manner for data translation, and then the new interface is called or directly connected to the DB for data migration (new data), and migration records or exception logs are generated. When the user clicks on the configured second - phase outage migration on the login interface, the scheduling of the second phase starts for incremental migration. The data in the old system from the end moment of the first phase to the current moment is pulled in an incremental rolling manner for data translation, and the new interface is called or directly connected to the DB for data migration (both addition, deletion, and modification are possible), and migration records or daily logs are recorded. After both phases are completed, data verification is performed to check whether the data in the old system is consistent with the data in the new system. Figure 5 The flowchart example of a solution integration provided by an embodiment of this application. Specifically, it includes: Migration tasks are created for Solution 1 and Solution 2 respectively. For the common modules and unique modules in Solution 1, full - volume migration is performed. When performing full - volume migration on the common module in Solution 2, it is judged whether there is data that meets the merging conditions in the module. If so, merging is performed, and full - volume migration is carried out for the unique module in Solution 2. For the common modules and unique modules in Solution 1, outage migration (incremental migration) is performed. When performing outage migration on the common module in Solution 2, it is judged whether there is data that meets the merging conditions in the module. If so, merging is performed, and outage migration is carried out for the unique module in Solution 2. After the migration is completed, migration verification is performed.

[0097] For better understanding, the following examples can be specifically referred to:

[0098] Solution 1 is the enterprise WeChat assistant; Solution 2 is the mall;

[0099] 1. Split the mall solution modules: modules such as framework, promotion, merchant, coupon code, material, search platform, integral balance, shopping cart, member marketing, payment finance, UC, etc.

[0100] 2. Split the enterprise WeChat assistant solution modules: modules such as framework, material, WeChat customer service, UC, payment finance, CDP, enterprise WeChat, etc.

[0101] 3. Configure module dependencies. The first - level module is the framework, the second - level is UC and material, the third - level is other modules, and the last - level is payment finance.

[0102] 4. Create migration tasks for the mall and enterprise WeChat assistant solutions respectively according to the merchant ID.

[0103] 5. Execute according to the execution order: Click the full migration of the mall tasks → Click the full migration of the enterprise WeChat assistant tasks → Click the suspension migration of the mall tasks → Click the suspension migration of the enterprise WeChat assistant tasks → Click the successful migration of the mall tasks and perform data verification → Click the successful migration of the enterprise WeChat assistant tasks and perform data verification.

[0104] 6. The entire data fusion is completed.

[0105] Next, the data migration device provided in the embodiments of the present application will be introduced. The data migration device described below can be correspondingly referred to the data migration method described above.

[0106] Specifically, please refer to Figure 6 , Figure 6 , which is a schematic structural diagram of a data migration device provided in the embodiments of the present application, and may include:

[0107] A business volume acquisition and sorting module 100, configured to acquire the business volumes of each merchant in the old system, and sort each merchant from small to large according to the business volume to obtain the migration order of each merchant in the old system;

[0108] A first migration module 200, configured to migrate the data of each merchant in the old system to the new system according to the migration order;

[0109] A splitting module 300, configured to, when there is a fusion of multiple solutions during the process of migrating each merchant from the old system to the new system, split all the data in the multiple solutions into modules;

[0110] A common module determination module 400, configured to use the same modules in different solutions after splitting as common modules;

[0111] A data fusion module 500, configured to merge the data in the common modules that meet the merging conditions to obtain merged data;

[0112] A separate module determination module 600, configured to use the different modules in different solutions after splitting as separate modules;

[0113] A second migration module 700, configured to migrate the data of the separate modules, the merged data and the unmerged data in the common modules from the old system to the new system.

[0114] Based on the above embodiments, the data migration device may further include:

[0115] A module group module, configured to, after using the different modules in different solutions after splitting as separate modules, use the modules that have a dependency relationship with each other as a module group;

[0116] The second migration module 700 is specifically configured to: migrate the data of the individual modules, the merged data and the unmerged data in the common module from the old system to the new system according to the dependencies existing in the module group.

[0117] Based on the above embodiment, the second migration module 700 may include:

[0118] A full - volume migration unit, configured to perform a full - volume migration of the data of the individual modules, the merged data and the unmerged data in the common module in the old system to the new system; when performing the full - volume migration, the old system is in a normal use state;

[0119] An incremental migration unit, configured to, after the full - volume migration is completed, perform an incremental migration of the data of the individual modules, the merged data and the unmerged data in the common module in the old system to the new system; when performing the incremental migration, both the new system and the old system are in a shut - down state.

[0120] Based on the above embodiment, the data migration device may further include:

[0121] A data verification module, configured to, after migrating the data of the individual modules, the merged data and the unmerged data in the common module from the old system to the new system, obtain the data in the old system before migration and the data in the new system after migration, and perform data verification;

[0122] A failure information sending module, configured to, when the data verification fails, send the failure information to the terminal.

[0123] Based on the above embodiment, the data migration device may further include:

[0124] A re - migration module, configured to, after sending the failure information to the terminal when the data verification fails, re - migrate the data with migration failures.

[0125] Based on the above embodiment, the first migration module 200 may include:

[0126] A merchant ID acquisition unit, configured to acquire the merchant IDs of the respective merchants;

[0127] A data reading unit, configured to read the data of each merchant in the old system according to the migration order and the merchant ID;

[0128] A data writing unit, configured to write the data to the corresponding position in the new system shared table according to the migration order and the merchant ID.

[0129] Based on the above embodiments, the data migration device may further include:

[0130] A login interface setting module, configured to set a login interface before obtaining the business volumes of various merchants in the old system; the login interface is used to manage user permissions;

[0131] A permission acquisition module, configured to obtain the permissions of the currently logged-in user through the login interface;

[0132] An execution module, configured to, when the logged-in user has the permission to migrate data, obtain the migration tasks set by the logged-in user, and perform data migration according to the migration tasks; the migration tasks include migrating merchants, migration solutions, and migration times.

[0133] Applying the data migration device provided by the embodiments of the present application, through the traffic acquisition and sorting module 100, which is configured to obtain the business volumes of various merchants in the old system, and sort the various merchants from small to large according to the business volumes to obtain the migration order of the various merchants in the old system; the first migration module 200 is configured to migrate the data of the various merchants in the old system to the new system according to the migration order; the splitting module 300 is configured to, when there is a fusion of multiple solutions during the migration of the various merchants from the old system to the new system, split all the data in the multiple solutions into modules; the common module determination module 400 is configured to use the same modules in different solutions after splitting as common modules; the data fusion module 500 is configured to merge the data in the common modules that meet the merging conditions to obtain the merged data; the separate module determination module 600 is configured to use the different modules in different solutions after splitting as separate modules; the second migration module 700 is configured to migrate the data of the separate modules, the merged data and the unmerged data in the common modules from the old system to the new system. This device first sorts the migration order according to the business volumes of the various merchants on the system, and first migrates the merchants with small business volumes to reduce risks; if there is a cross-solution fusion during the migration of the merchants, then split the data of each solution into modules, and merge and migrate the data that can be merged in the common modules, ensuring that the system upgrade can be completed even when the system upgrade involves multiple solutions. Moreover, obtain the user login permission to ensure the security of data migration; and, in order to ensure the logic of the modules with dependencies during the migration process, set a module group and sort for migration; and, adopt the methods of incremental migration and full-scale migration for data migration to reduce the impact on merchants; and, save data storage costs and avoid data disorders during data migration, and migrate to the shared table according to the merchant ID.

[0134] The data migration device provided by the embodiments of the present application will be introduced below. The data migration device described below can be correspondingly referred to the data migration method described above.

[0135] Please refer to Figure 7 , Figure 7 , which is a schematic structural diagram of a data migration device provided by the embodiments of the present application, may include:

[0136] A memory 10 for storing computer programs;

[0137] A processor 20 for executing the computer program to implement the above data migration method.

[0138] The memory 10, the processor 20, and the communication interface 31 complete mutual communication through the communication bus 32.

[0139] In the embodiments of the present application, the memory 10 is used to store one or more programs. The program may include program codes, and the program codes include computer operation instructions. In the embodiments of the present application, the memory 10 may store programs for implementing the following functions:

[0140] Obtain the business volumes of each merchant in the old system, and sort each merchant from small to large according to the business volume to obtain the migration order of each merchant in the old system;

[0141] Migrate the data of each merchant in the old system to the new system according to the migration order;

[0142] When there is a fusion of multiple solutions during the process of each merchant migrating from the old system to the new system, all the data in the multiple solutions will be module-split;

[0143] Take the same modules in the split different solutions as common modules;

[0144] Merge the data in the common modules that meet the merging conditions to obtain the merged data;

[0145] Take the different modules in the split different solutions as separate modules;

[0146] Migrate the data of the separate modules, the merged data and the unmerged data in the common modules from the old system to the new system.

[0147] In a possible implementation manner, the memory 10 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system and application programs required for at least one function, etc.; the data storage area may store the data created during the use process.

[0148] In addition, the memory 10 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A part of the memory may also include NVRAM. The memory stores an operating system and operation instructions, executable modules, or data structures, or subsets thereof, or extended sets thereof, where the operation instructions may include various operation instructions for implementing various operations. The operating system may include various system programs for implementing various basic tasks and processing hardware-based tasks.

[0149] The processor 20 may be a central processing unit (CPU), an application-specific integrated circuit, a digital signal processor, a field programmable gate array, or other programmable logic devices. The processor 20 may be a microprocessor or any conventional processor, etc. The processor 20 may call the program stored in the memory 10.

[0150] The communication interface 31 may be an interface of a communication module for connecting to other devices or systems.

[0151] Of course, it should be noted that Figure 7 the structure shown does not constitute a limitation on the data migration device in the embodiments of the present application. In actual applications, the data migration device may include more or fewer components than Figure 7 those shown, or combine certain components.

[0152] Next, the readable storage medium provided by the embodiments of the present application will be introduced. The readable storage medium described below can be correspondingly referred to the data migration method described above.

[0153] The present application also provides a readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above data migration method are implemented.

[0154] The computer-readable storage medium may include various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc.

[0155] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same or similar parts among the various embodiments can be referred to each other. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple. For the relevant parts, reference can be made to the description in the method part.

[0156] Those skilled in the art may further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in the form of hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0157] Finally, it should also be noted that in this document, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or elements inherent to such process, method, article or device.

[0158] The above has introduced in detail a data migration method, apparatus, device and readable storage medium provided by this application. Specific examples are used in this document to elaborate on the principle and implementation manner of this application. The description of the above embodiments is only used to help understand the method and its core idea of this application; at the same time, for those of ordinary skill in the art, according to the idea of this application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to this application.

Claims

1. A data migration method, characterized in that, Including: Obtain the business volume of each merchant in the old system, and sort each merchant from small to large according to the business volume to obtain the migration order of each merchant in the old system; Migrate the data of each merchant in the old system to the new system according to the migration order; When there is a fusion of multiple solutions during the process of migrating each merchant from the old system to the new system, then split all the data in the multiple solutions into modules; Regard the same modules in different solutions after splitting as common modules; Merge the data in the common modules that meet the merging conditions to obtain the merged data; Regard the different modules in different solutions after splitting as separate modules; Migrate the data of the separate modules, the merged data and the unmerged data in the common modules from the old system to the new system.

2. The data migration method according to claim 1, wherein After regarding the different modules in different solutions after splitting as separate modules, it further includes: Regard the modules that have dependencies on each other as a module group; Correspondingly, the migrating the data of the separate modules, the merged data and the unmerged data in the common modules from the old system to the new system includes: Migrate the data of the separate modules, the merged data and the unmerged data in the common modules from the old system to the new system according to the dependencies existing in the module group.

3. The data migration method according to claim 1, wherein The migrating the data of the separate modules, the merged data and the unmerged data in the common modules from the old system to the new system includes: Perform a full-scale migration of the data of the separate modules, the merged data and the unmerged data in the common modules in the old system to the new system; when performing the full-scale migration, the old system is in a normal use state; After the full-scale migration is completed, then perform an incremental migration of the data of the separate modules, the merged data and the unmerged data in the common modules in the old system to the new system; when performing the incremental migration, the new system and the old system are in a shutdown state.

4. The data migration method according to claim 1, wherein After migrating the data of the separate modules, the merged data and the unmerged data in the common modules from the old system to the new system, it further includes: Obtain the data in the old system before migration and the data in the new system after migration, and perform data verification; When the data verification fails, then send the failure information to the terminal.

5. The data migration method according to claim 4, wherein After the step of when the data verification fails, then send the failure information to the terminal, it further includes: Migrate the data that failed to migrate again.

6. The data migration method according to claim 1, wherein The migrating the data of each merchant in the old system to the new system according to the migration order includes: Obtain the merchant ID of each merchant; Read the data of each merchant in the old system according to the migration order and the merchant ID; Write the data to the corresponding position in the shared table of the new system according to the migration order and the merchant ID.

7. The data migration method according to claim 1, characterized in that, Before obtaining the business volume of each merchant in the old system, it further includes: Set up a login interface; the login interface is used to manage user permissions; Obtain the permissions of the currently logged-in user through the login interface; When the logged-in user has the permission for data migration, obtain the migration tasks set by the logged-in user to perform data migration according to the migration tasks; the migration tasks include migrating merchants, migration solutions, and migration time.

8. A data migration device, characterized in that, It includes: A business volume acquisition and sorting module, which is used to obtain the business volume of each merchant in the old system and sort each merchant from small to large according to the business volume to obtain the migration order of each merchant in the old system; A first migration module, which is used to migrate the data of each merchant in the old system to the new system according to the migration order; A splitting module, which is used to split all the data in the multiple solutions when there is a fusion of multiple solutions during the migration of each merchant from the old system to the new system; A common module determination module, which is used to regard the same modules in different solutions after splitting as common modules; A data fusion module, which is used to merge the data that meets the merging conditions in the common modules to obtain the merged data; A separate module determination module, which is used to regard the different modules in different solutions after splitting as separate modules; A second migration module, which is used to migrate the data of the separate modules, the merged data and the unmerged data in the common modules from the old system to the new system.

9. A data migration device, characterized in that, It includes: A memory, which is used to store computer programs; A processor, which is used to implement the steps of the data migration method according to any one of claims 1 to 7 when executing the computer program.

10. A readable storage medium, characterized in that, A computer program is stored on the readable storage medium, and when the computer program is executed by a processor, it implements the steps of the data migration method according to any one of claims 1 to 7.

Images