Scalable data migration to the cloud

A computer implemented method comprising:

• receiving, by a processor, a request to initiate a migration of data;
• receiving, by the processor, data identified in the request to initiate a migration from a first database;
• generating, by the processor, a file-out of the data by converting the data from a proprietary schema into a commonly understood schema;
• migrating, by the processor, a first portion of the file-out to a cloud provider;
• asynchronously migrating, by the processor, a second portion of the file-out to the cloud provider, wherein the first portion of the file-out and the second portion of the file-out are migrated independently without interrupting ongoing operations of the first database;
• validating, by the processor, the migration of the first portion of the file-out to determine whether the migration of the first portion of the file-out was successful;
• validating the migration of the second portion of the file-out to determine whether the migration of the second portion of the file-out was successful;
• and
• in response to validating the migrations, generating, by the processor, a first migration response indicating whether the migration of the first portion of the file-out was successful and a second migration response indicating whether the migration of the second portion of the file-out was successful.

A non-transitory computer-readable medium comprising instructions that are executable by a processor for causing the processor to:

• receive, from a user interface (UI) application, a request to initiate a migration of data;
• receive, from a first database, data identified in the request to initiate a migration from a first database;
• generate a file-out of the data by converting the data from a proprietary schema into a commonly understood schema;
• migrate a first portion of the file-out to a cloud provider;
• asynchronously migrate a second portion of the file-out to the cloud provider, wherein the first portion of the file-out and the second portion of the file-out are migrated independently without interrupting ongoing operations of the first database;
• validate the migration of the first portion of the file-out to determine whether the migration of the first portion of the file-out was successful;
• validate the migration of the second portion of the file-out to determine whether the migration of the second portion of the file-out was successful;
• and
• in response to validating the migrations, generate a first migration response indicating whether the migration of the first portion of the file-out was successful and a second migration response indicating whether the migration of the second portion of the file-out was successful.