| CPC G06F 16/2425 (2019.01) [G06F 16/214 (2019.01); G06F 16/2365 (2019.01); G06F 16/252 (2019.01); G06N 5/04 (2013.01)] | 20 Claims |

|
1. An automated migration system configured to discover and track a migration of legacy networked resources within a computer network environment, the automated migration system comprising:
a migration database defining one or more migration schema formats each corresponding to a given migration type;
a migration server comprising one or more processors and communicatively coupled to the migration database and to a computer network comprising a plurality of online network resources; and
a network resource discovery application (app) comprising computing instructions configured to be implemented on the one or more processors of the migration server and having access to one or more executable predefined migration queries stored on the migration server, each of the executable predefined migration queries customized for the migration database by defining a migration schema format and a corresponding migration type,
wherein the migration database defines a first migration schema format corresponding to a first migration type and a second migration schema format corresponding to a second migration type, wherein the first migration schema format defines a first format of data required for migration of a first legacy networked resource identified by the first migration type, and wherein in the second migration schema format defines a second format of data required for migration of a second legacy networked resource identified by the second migration type,
the computing instructions of the network resource discovery app configured, when executed on the one or more processors of the migration server and during an active migration session, to:
execute a first executable predefined migration query comprising an executable discovery script customized based on the first migration type and configured to discover network resources specific to the first migration type, wherein the executable predefined migration query with its executable discovery script is selected from the one or more executable predefined migration queries based on both (1) the first migration type and (2) the corresponding first migration schema format of the first migration type, the executable discovery script configured to discover a first set of network dependencies of the first legacy networked resource accessible on the computer network, the first legacy networked resource defining a resource type corresponding to the first migration type and the first executable predefined migration query,
execute a second executable predefined migration query comprising an executable discovery script customized based on the second migration type and configured to discover network resources specific to the second migration type, wherein the executable predefined migration query with its executable discovery script is selected from the one or more executable predefined migration queries based on both (1) the second migration type and (2) the corresponding second migration schema format of the first migration type, the executable discovery script configured to discover a second set of network dependencies of the second legacy networked resource accessible on the computer network, the second legacy networked resource defining a resource type corresponding to the second migration type and the second executable predefined migration query,
load, during the active migration session, first dependency data representative of the first discovered set of network dependencies into the migration database according to the first migration schema format,
load, during the active migration session, second dependency data representative of the second discovered set of network dependencies into the migration database according to the second migration schema format, and
predict, during the active migration session, a migration plan for a target migration network resource to be implemented on the computer network at a future time, the target migration network resource requiring access to the first dependency data and the second dependency data at the future time.
|