Just-in-time data migration in a live system

1. A method for just-in-time data migration in a live system, the method comprising:

indicating, by a computer, changes in a subscription that include structure, syntax, semantic, and identifier changes in data corresponding to the subscription to a new target system, wherein the computer is communicatively coupled with a client device and with the new target system;

receiving, by the computer, from the client device, a request to run a subscription operation on the new target system, the subscription operation corresponding to the subscription on the new target system;

determining, by the computer, whether the subscription operation requires related subscription data from a legacy system;

responsive to the computer determining that the subscription operation requires the related subscription data from the legacy system, transforming, by the computer, the related subscription data required for the subscription operation just-in-time to support just-in-time migration of the related subscription data required for the subscription operation from the legacy system to the new target system;

running, by the computer, the subscription operation on the new target system generating a new identifier for the subscription while referencing the related subscription data being migrated just-in-time from the legacy system; and

performing, by the computer, a no-operation task on the new target system to trigger migration of other subscription data that was not required for the requested subscription operation from the legacy system after the subscription operation is complete on the new target system by running the no-operation task within defined throttling limits and in batches to minimize system load, increase system performance, and reduce overall system stress caused by en masse data migration.

2. The method of claim 1 further comprising:

responsive to the computer determining that the subscription operation does not need any related subscription data from the legacy system, running, by the computer, the subscription operation on the new target system generating a new subscription identifier while identifying that legacy system data is unnecessary.

3. The method of claim 1 further comprising:

setting, by the computer, a data migration flag to true for migrating the related subscription data from the legacy system to the new target system; and

migrating, by the computer, just-in-time the related subscription data from the legacy system to the new target system.

4. The method of claim 3 , wherein the computer only migrates that portion of subscription data corresponding to the subscription operation on the subscription only when that particular portion of subscription data is needed and not before.

5. The method of claim 1 further comprising:

instructing, by the computer, the legacy system to remove an old identifier corresponding to the subscription from the legacy system; and

instructing, by the computer, the new target system to generate the new identifier for the subscription.

6. The method of claim 1 further comprising:

instructing, by the computer, the new target system to update a subscription offering endpoint hosting the subscription with the new identifier corresponding to the subscription.

7. The method of claim 6 further comprising:

instructing, by the computer, the subscription offering endpoint to perform the subscription operation on the subscription using the new identifier corresponding to the subscription.

8. The method of claim 1 , wherein the legacy system is a legacy notification system, and wherein the new target system is an open standards-based notification system, and wherein the legacy notification system utilizes custom protocols to communicate with a subscription offering endpoint, and wherein the open standards-based notification system utilizes open standard protocols to communicate with the subscription offering endpoint.

9. The method of claim 1 , wherein the new identifier for the subscription is a cloud resource name that uniquely identifies the subscription, and wherein the new target system generates the cloud resource name from a concatenation of segments that identify the subscription, a location of the subscription, and a service the subscription belongs to.

10. A computer program product for just-in-time data migration in a live system, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a computer to cause the computer to perform a method comprising:

indicating, by the computer, changes in a subscription that include structure, syntax, semantic, and identifier changes in data corresponding to the subscription to a new target system;

receiving, by the computer, a request to run an operation corresponding to the subscription on the new target system from a client device user;

determining, by the computer, whether the operation needs related subscription data from a legacy system;

responsive to the computer determining that the operation does need the related subscription data from the legacy system, transforming, by the computer, the related subscription data for the operation just-in-time to support just-in-time migration of the related subscription data from the legacy system to the new target system;

running, by the computer, the operation on the new target system generating a new identifier for the subscription while referencing the related subscription data being migrated just-in-time from the legacy system; and

performing, by the computer, a no-operation task on the new target system to trigger migration of other subscription data from the legacy system after the operation is complete by running the no-operation task within defined throttling limits and in batches to minimize system load, increase system performance, and reduce overall system stress caused by en masse data migration.

11. The computer program product of claim 10 further comprising:

responsive to the computer determining that the operation does not need any related subscription data from the legacy system, running, by the computer, the operation on the new target system generating a new subscription identifier while identifying that legacy system data is unnecessary.

12. The computer program product of claim 10 further comprising:

setting, by the computer, a data migration flag to true for migrating the related subscription data from the legacy system to the new target system; and

migrating, by the computer, just-in-time the related subscription data from the legacy system to the new target system.

13. The computer program product of claim 12 , wherein the computer only migrates that portion of subscription data corresponding to the operation on the subscription only when that particular portion of subscription data is needed and not before.

14. The computer program product of claim 10 further comprising:

instructing, by the computer, the legacy system to remove an old identifier corresponding to the subscription from the legacy system; and

instructing, by the computer, the new target system to generate the new identifier for the subscription.

15. The computer program product of claim 10 further comprising:

instructing, by the computer, the new target system to update a subscription offering endpoint hosting the subscription with the new identifier corresponding to the subscription.

16. The computer program product of claim 15 further comprising:

instructing, by the computer, the subscription offering endpoint to perform the operation on the subscription using the new identifier corresponding to the subscription.

17. A computer system for just-in-time data migration in a live system, the computer system comprising:

a bus system;

a storage device connected to the bus system, wherein the storage device stores program instructions; and

a processor connected to the bus system, wherein the processor is communicatively coupled with a client device and with a new target system, and wherein the processor executes the program instructions to:

indicate changes in a subscription that include structure, syntax, semantic, and identifier changes in data corresponding to the subscription to the new target system;

receive, from the client device, a request to run a subscription operation on the new target system, the subscription operation corresponding to the subscription on the new target system;

determine whether the subscription operation requires related subscription data from a legacy system;

transform the related subscription data required for the subscription operation just-in-time to support just-in-time migration of the related subscription data required for the subscription operation from the legacy system to the new target system in response to determining that the subscription operation requires the related subscription data from the legacy system;

run the subscription operation on the new target system generating a new identifier for the subscription while referencing the related subscription data being migrated just-in-time from the legacy system; and

perform a no-operation task on the new target system to trigger migration of other subscription data that was not required for the requested subscription operation from the legacy system after the subscription operation is complete on the new target system by running the no-operation task within defined throttling limits and in batches to minimize system load, increase system performance, and reduce overall system stress caused by en masse data migration.

18. The computer system of claim 17 , wherein the processor further executes the program instructions to:

run the subscription operation on the new target system generating a new subscription identifier while identifying that legacy system data is unnecessary.

19. The computer system of claim 17 , wherein the processor further executes the program instructions to:

set a data migration flag to true for migrating the related subscription data from the legacy system to the new target system; and

migrate just-in-time the related subscription data from the legacy system to the new target system.

20. The computer system of claim 19 , wherein the processor only migrates that portion of subscription data corresponding to the subscription operation on the subscription only when that particular portion of subscription data is needed and not before.