illustration of cloud migrationNot everyone may readily admit it, but you know everyone’s thinking it: migrating to the cloud is freakin’ scary.

When you consider all that can go wrong—problems with data and application migration, a lack of “cloud trained” personnel, difficulty maintaining and documenting what is hosted where—it’s no wonder some companies are moving cautiously instead of going all-in to the cloud at full speed ahead. But the truth of the matter is, as long as you’re mentally prepared for all the changes that’ll come with the transition to the cloud, you should be able to allay most of those fears.

This post, excerpted from the article “Adopting the Cloud Mindset,” examines a couple of new performance concepts to help you get started. For more examples of how you should be rethinking application performance when migrating to the cloud, read the full article.

Need-to-know #1: Server performance will no longer be an indicator of an app’s health

Historically, many operations teams assumed that if the server was functional, then the app must be as well. This is why monitoring was focused solely on servers and infrastructure. But when you move to the cloud, you no longer control the infrastructure, so instead of wanting to know how the servers are performing, you’re going to want to know if your cloud service is meeting the needs of your application. So your first big change with the cloud is that your IT team’s focus will need to shift toward how your app is performing, rather than how the infrastructure is performing.

Need-to-know #2: Applications will live all over the place

If you’re thinking about migrating to the cloud, there’s a good chance you’ll head down the path of a hybrid cloud model, one in which you can leverage both public cloud services while continuing to use your existing private (on-premises) resources. When this happens, however, application components can end up living in various places, and it becomes difficult to get visibility into your entire environment.

Certain tools may be able to monitor the performance of your apps on-premises but not apps in the cloud, and vice versa. That means you’re going to need an independent, third-party service to help you see the bigger picture. Ideally, this would come in the form of an application performance monitoring tool that gives you visibility into both on-premises and multiple cloud services providers. This way, you can consolidate multiple disparate tools into a unified view across your environment, giving you visibility into your customer’s experience and insight into where your performance bottlenecks lie.

What else do you need to know?

Find out in our “Adopting the Cloud Mindset” article. And for more cloud resources, check out:

Asami Novak is director of content strategy and development at New Relic. Prior to joining the New Relic team, she wrote marketing and ad copy for a variety of B2B and B2C companies. Her editorial writing has appeared in WIRED and Dwell, among other publications. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!