Perform migration acceptance testing

You can validate the success of your cloud migration by comparing the baselines of your on-premise applications against the baselines of your migrated cloud applications.

As you complete each milestone in your cloud migration, compare the baselines of your applications against their previous baselines. For the final acceptance test at the end of your migrations, compare the on-premise baselines against the final migrated cloud baselines.

Follow these steps to determine if your migration was successful or if you still have some work to do before it is complete:

AcceptanceTestingChart_preview.png

1. Gather existing on-premise baselines

New Relic recommends creating application baselines before continuing this procedure.

As part of creating application baselines, you identified application components to move to the cloud, deployed New Relic, and recorded baselines for your applications based on existing on-premise deployment. You can reuse the same table that you created in the application baseline tutorial for your on-premise baselines:

Example of a baseline before cloud migration

Component Name

Response time

Availability (SLA)

Apdex

Service 1

1.5 secs

80%

70%

Service 2

0.7 secs

73%

68%

2. Compare baselines after you migrate

Establish milestones as you progress with your cloud migration by reviewing baselines for applications, databases, and other application tiers. After you migrate an application to the cloud, repeat the same steps that you used to create an on-premise baseline until you have migrated all components to the cloud (applications, web services, databases, message queues). You can mark application baselines based on time (for example, bi-weekly) or based on the full migration of each application tier.

Build on your on-premise baseline table to compare results after each migration milestone:

Example of a baseline after cloud migration

Component Name

Response time

Availability (SLA)

Apdex

Service 1

0.9 secs

96.8%

95%

Service 2

0.6 secs

90%

92%

You can see the most benefit from the Availability metric by monitoring it over a long period of time. However, as you move closer to completing your migration, this metric should get closer and closer to 100%.

3. Create dashboards to track migration results

Use New Relic Insights widgets to track each of your business key performance indicator (KPI) so that you can measure the success of your cloud migration.

This Insights dashboard illustrates the maturity of your application’s performance over a period of time based on deployment milestones:

AcceptanceTestingDashboard_preview.png
Insights > dashboard: View your application's performance based on deployment milestones.

At the end of your migration, you can display this information in Insights to show a clear comparison between your on-premise environment and your migrated cloud environment.

4. Uncover issues

New Relic provides performance metrics, but it also provides errors and unhandled exceptions associated with your applications. It is important to keep an eye on errors and exceptions so you can verify if they occur before, during, or after your migration. Refer to Identify issues and roadblocks for more detail regarding the detection of errors or possible issues with your application's architecture, scale, or performance.

Expert tip for ensuring a successful migration

Continue to compare baselines until you have successfully migrated all components of your application to the cloud. The goal is to have your cloud-based application baselines perform as well as, or better than, their on-premise baselines. You may not be able to draw 1:1 comparisons between your cloud-based components and their on-premise counterparts, but you will be able to compare established cloud migration milestones throughout your migration to make sure it is successful.

For more help

Explore the New Relic Platform.

Recommendations for learning more: