In past few years there has been significant cloud adoption, as it provides considerable value over traditional datacenters—achieving greater scalability, cost-efficiency, and improved performance.
Many organizations are now looking to quickly take advantage of this by migrating their existing applications and workloads. But cloud migration requires careful planning and strategy. One of the keys to cloud success is determining the optimal platform and priorities for running business applications. Once considered optional, these applications are now central to infrastructure decisions and achieving company goals.
To enable successful migration, it's important to have a strong plan in place that covers the end-cloud environment, training and, most important of all, the readiness of your workloads and applications. To do this, you need to determine how to successfully create the initial technical plans and business justification, ensure your workloads will run as expected, and perform the migration with limited impact to the business.
If you're an IT manager running on-premises applications and servers, this guide is designed to help you start their migration to the cloud.
Migrating to the cloud does not have to be difficult. With the right tools and processes, your migration project can be fast and friction free. Learn how methods such as lift and shift rapidly move you to cloud, reducing cost immediately, and enabling you to focus on future cloud modernization. Dive into discovery, migration, and optimization methods to help along the way, and start to discover next steps in your continuing adoption of cloud resources.
At first glance migration may seem like a technical decision, but at its core this is a business decision. Ultimately, it begs a fundamental question: what's driving your business to migrate to the cloud, and why now?
The benefits of cloud are universal—reduction in running costs, faster modernization capabilities and increased security. But usually there is an initiator that kicks off the discussion in your organization. These can include:
Operational efficiencies, and reduction of operating expenses. Due to the reduction in hardware support, increased manageability, and efficiency of process, you can save an average of 20 to 30 percent on virtual machine (VM) resource configuration alone.
Decreased time to market/release. By reducing management overhead, and freeing up budget, more time and effort can be focused on rapid software and solution development. Faster deployment of IaaS and PaaS platforms will enable your business to release faster and more often.
Supporting scalability requirements that are more cost effective. By having to plan for peak usage through on-premises systems, most of the time you are left with servers that are running at less than 20 percent utilization. The cloud releases organizations from this model, enabling a scale-when-you-need-it approach.
Renewal of datacenter or hardware leasing. If you're currently extending your budget on renewing hardware or paying for datacenter locations to host them, this is the perfect time to look toward cloud migration. The cloud can make these necessities a thing of the past by enabling a cloud vendor to host these services for you.
Renewal of licensing. Nearly everyone has an annual licensing agreement with their major IT providers. These too require ample budget to ensure your virtualization and OS platform are sufficiently covered. The cloud can help you here, providing a pay-as-you-go offering to reduce this cost.
" One of our big objectives was to eliminate $3 million in capital costs over about three years, and to reduce our operating costs by approximately the same amount. At the same time, we wanted to improve our quality of service. With Azure, we're confident that we'll meet those goals."
Jim Slattery, Chief Financial Officer, Capstone Mining
Application development and modernization. If you're in the software business, your resources are probably spread thin. And using on-premises platforms is likely not enabling you to adopt modern services. The cloud provides an integrated platform for modern development where development teams can increase speed by up to 33 percent.
Ultimately, by migrating your current environment to the cloud, you're putting yourself in a better position to accelerate your business. By reducing costs and making management more efficient, a cloud platform can immediately impact your IT group's ability to invest back into core strategic projects, increasing security and reliability while advancing application development.
Sometimes cloud migration can be simple, with only a few decision points. However, your case may be more complex, depending on how many servers and VMs you use.
Your migration could require you to run parallel and iterative migration processes as you progressively move your applications and workloads to the cloud.
Whether your migration is simple or complex, it's helpful to think of the basic elements of the process.
Also referred to as "lift and shift," this stage entails migrating your physical servers and VMs as-is to the cloud. By simply shifting your current server environment straight to IaaS, you reap the benefits of cost savings, security, and increased reliability.
In the new rehosted cloud model, hardware and OS you previously managed yourself is now managed by the cloud provider. All the other aspects of the workload or application remain the same. This is the most popular migration approach, as it lets organizations move quickly with little risk or impact and receive immediate benefits. It also allows customers to see lower TCO faster, enabling investment back into the migration process to evolve through the model.
Also known as "cloud optimization," this stage involves using additional cloud provider services to optimize the cost, reliability, and performance by refactoring your applications. Where in lift and shift, you were only taking advantage of the provider managed hardware and OS, in this model you also take advantage of cloud services to drive down cost.
You continue to utilize your current application as-is, with some minor application code or configuration changes, and connect your application to new infrastructure services such as containers, database, and identity management systems. By employing modernized services in this scenario, you can lower cost and management.
Also known as "app modernization," this stage means to revise the existing application by aggressively adopting PaaS or even SaaS services and architecture. The process encompasses major revisions to add new functionality or to rearchitect the application for the cloud. An example of this stage would be code redesign to decompose the original application into smaller chunks, and then deploy using modern cloud provider services.
Lift and shift is the most common (and easiest) first step, enabling you to move quickly to the cloud. Through process discovery efforts, you can easily map the next best steps for each workload based on goals, effort, and complexity. An advantage of this approach is that it enables you to sustain parallel migration efforts. And, as your IaaS projects continue, you can easily start modernizing certain applications to PaaS and even SaaS options.
While the migration evolution model shows a potential step-by-step journey for workload in moving from on-premises to the cloud, the model also suggests that workloads could start at a different pivot points. Where you begin depends upon the complexity of the workload and, ultimately, what you want out of it. For example, if you have a simple web application hosted in Windows Server Internet Information Server (IIS), connected to a database, then it may make sense to proceed directly to the cloud optimization stage. In this case, you could migrate that application using Azure App Service and Azure SQL Database. To do this, you'd need to have a deep understanding of the application, including its complexity and dependencies.
No matter what option you choose, you need a solution that provides a smooth and easy cloud adoption, so you can migrate at your own pace. This requires a cloud provider (and core partners) that can deliver a comprehensive set of tools, methods, and offers for helping to ease migration and overall reduce risk. Most of all, this solution should offer a simple process that's easy to follow.
With these goals in mind, Microsoft recommends a simple three-step migration process for moving to the cloud.
With this straightforward framework, you get a proven approach to migration. This process provides a clear picture of your entire application and workload portfolio, the best way to configure them to achieve migration, convenient tools to ensure low-impact transfer, and ongoing performance and cost optimization.
But before migration begins, how do you ensure that your virtual datacenter in the cloud is ready to receive your workloads? As you're planning to run your most critical applications there, you want to be confident that your cloud foundation is solid. If you already have workloads or DevTest running on the cloud, then you may have an environment and connectivity ready to go. However, if you're new to the cloud or only have a basic setup there, then you'll need to perform few steps before migration.
Prior to migration, you essentially need to build a virtual datacenter in your cloud, including connectivity, networking, storage, and identity—elements comparable to your on-premises environment.
By building this virtual datacenter, you can ensure that your applications will continue to support the business after migration, without surprises.
There are many excellent tools and guidance to help you accelerate this step, but below are some of the basics—and why they're important to migration.
As with your on-premises environment, you need a way for users to be identified and authenticated to ensure secure access to your new cloud resources. In most cases, this means running Azure Active Directory or a similar solution. You could simply extend your on-premises identity to the cloud to support the migrated workloads. However, many cloud providers have built-in identity solutions provided as a service. These can also integrate with your on-premises identity systems to enable single sign-on for user convenience. As your workloads will now be stored within the cloud, you'll also want seamless access for users between your existing on-premises systems and the systems you've migrated.
To ensure a harmonious user experience—while supporting your expected growth into more advanced cloud services—a good investment would be a cloud based identity management solution connected to your on-premises environment.
Another necessity in your cloud is a storage platform that will meet the expected performance needs of your migrated workloads. On-premises, this storage is usually through NAS or SAN-based systems. In the cloud, virtual storage is usually through blob or page, depending on the type of data being stored.
Fortunately, you can choose among many storage types to guarantee reliable performance, including performance and access levels, backup, geographical replication, and disaster recovery. Working with a virtual storage platform means you also have a finer degree of control and configuration. You can easily configure exact storage requirements for each workload as needed, without having to worry about the physical architecture. Azure even offers managed storage, which takes the pain out of storage configuration. It requires you to enter just a few details before acquiring up to thousands of secure, reliable, and available disks for your migration project.
Networks are crucial. They are the figurative backbone of the datacenter. Moving to the cloud requires a new way of networking since you're no longer reliant on physical topology. In fact, you can now overcome physical boundaries with a single subnet, which simplifies networking communication.
When moving applications from on-premises to the cloud, you may want to keep them in the same networking subnets and even IP address ranges to ensure a seamless migration. Virtual networking can support this, and merge with your on-premises physical networking architecture, as needed. This ensures that your applications can continue to use the network topology they were built upon, further easing migration.
During migration you're going to move vast amounts of data. However, you'll still be moving data even after the bulk of your critical workloads are hosted in the cloud. As such, you should consider a more dedicated connectivity option to help with data transfer and ultimate end-user experience.
You may currently have virtual networks set up, possibly using these over the internet or site-to-site VPN to connect to your cloud environment. While this works well for smaller deployments, you'll need a new approach to run an entire enterprise both during and after the migration.
Azure ExpressRoute as an example, is a compelling tool to use for this. It ensures both performance and security—especially in the initial heavy lifting of VMs to Azure, which involves considerable data flowing across the wires. ExpressRoute enables a faster, private connection to Azure.
Azure Data Box is another option for migrating large amounts of data—when you're limited by time, network availability, or cost. Azure Data Box is a physical device that you connect to your network and load your data to using standard NAS protocols. Then you simply send it to Microsoft through a delivery transport service. Your data will then be securely loaded into your Azure environment.
While many core management skills can migrate to the cloud, there are some key differences. You'll need to get up to speed on new skills. However, training means time away from performing core duties, can be costly and, frequently, doesn't properly build on what you already know.
Azure Essentials can help solve this with unique learning paths focused on job roles. This readiness tool offers simple online training in bite-sized pieces, practical labs, and assessments to test your knowledge. It's the fastest way for your team to grow their skills, and, best of all, it's free.
Now it's time to begin your migration journey to the cloud. This e-book focuses on a migration process where you would be moving the bulk of your applications and workloads running in VMs to IaaS (and plan to modernize after that has been performed). The environment in this scenario is set up in Azure with Azure Active Directory (linked to on-premises AD) for identity management, with managed disks ready to receive the data and virtual networks deployed.
In migrating to the cloud, you first need to get a better understanding of your applications, how many servers and/or VMs you have, and how you'll need to plan to move them to the cloud.
Uncertainties about the total savings and perceived complexity can get in the way of taking this step. Many organizations have come to realize that moving existing workloads to Azure can yield significant benefits. Justifying the investment requires confidence that you'll save a significant amount on operational costs, and that your current workloads will work as expected in the cloud.
Some workloads can run immediately on Azure without modification, while other workloads that have operational and application dependencies in an on-premises environment require further analysis and planning. If your applications are made up of multiple servers or VMs, then consolidated planning must be done to identify and shift these to the cloud. This is not a manual process and you'll need intelligent planning tools to do it. Similarly, getting accurate cost comparisons can be challenging when you're estimating the load and cloud VM series type. Without automated analysis to map on-premises capacity to VM instance, your estimations may fall short—causing performance issues. Or your estimations may go too far—stretching your budget.
" We don't want to be in the datacenter business; we're in the thread business. We plan to move 90 percent of our global datacenter infrastructure into Azure, and we're at about 75 percent now. The only things we'll leave on-site are a few domain controllers and file/print servers."
Richard Cammish, Chief Information Officer, Dillon Gage
Technical and business planning for migration comes down to four straightforward steps:
It's likely that your organization runs hundreds—if not thousands—of servers and VMs. While your current management tools may have a good representation of these, to kick-start any migration you'll need a discovery mechanism that can feed data into subsequent steps.
Discovery of servers and VMs is usually a straightforward process. It relies on interaction directly with the endpoint (using an agent) or managing hypervisor (such as vSphere or Hyper-V).
Ultimately, the goal of discovery is to collect server and application information, including type, configuration, usage, and applications that may be running.
Once discovery is complete, you'll need to map any dependencies or communication between your servers (and applications). This is critical because when migrating an application, you need to know all the servers and processes the app is using.
Many tools provide server dependency mapping, but don't extend to application dependencies. To ensure a full picture of all communication between workloads, you need a tool that will perform both. This will allow you to create visual maps of all your applications and workloads, which enables their interaction as a single entity for costing, configuration analysis, and eventually migration.
Discovery enables you to ensure that each workload will function on your cloud platform. Through the collected analysis, discovery tools will be able to provide you metrics on the compatibility of the workload in the cloud. For example, is the workload OS-supported? Or are there specific hardware dependencies that may not be replicated in a cloud environment (such as running a UEFI boot, which is larger than a 4 TB data disk size)? Configuration analysis should tell you which workloads will migrate with no modifications, workloads that may require basic modifications to comply, and any workloads that are not compatible in their current formation, as well as provide guidelines to remediate potential issues or recommend configuration changes.
The final step of discovery is collecting resource usage reporting (such as CPU, memory, and storage). This is important as on-premises VMs are often overprovisioned but actually utilized under 20 percent. If you were to take the physical configuration of your on-premises server and map this to an IaaS VM series type, you'll likely find that you're paying for more performance and scale than you need.
As the cloud is costed as a usage model, you should ensure your choice meets both performance and economic targets. The goal in any cloud model is to drive your VMs to at least 90 percent utilization, while making sure you meet performance and reliability goals. Through historic resource analysis, intelligent cost analysis tools can determine the actual usage of your workload and suggest the best cloud IaaS VM series to use.
There are many tools in the Azure ecosystem that enable you to tackle these needs simultaneously.
As part of the Azure subscription for all customers, Microsoft provides Azure Migrate to assist in discovery and assessment. There are also many supporting partner discovery tools that can help you accurately map on-premises relationships. These tools can also help you with usage characteristics like CPU, memory, and storage to equivalent Azure environments, giving you the technical and business reporting needed to continue your migration plans. Using these tools will help you maximize the benefits of moving to Azure, as well as identify where programs such as Azure Hybrid Benefit best fit into your migration to save further budget. With Azure Hybrid Benefit, you can utilize your on-premises Windows Server licenses with Software Assurance when migrating and save up to 40 percent in Azure VM runtime costs.
For further information on these tools, explore the following resources:
Once you have completed your discovery and assessment, it's time to prepare for the next step: cloud migration.
This is where, after you have landed on your migration goals and gathered all requirements and constraints, you can choose the best method of migration.
Earlier in this e-book, we overviewed the migration evolution model that showed workloads progressing through phases of lift and shift, cloud optimization, and eventually app modernization.
It's through the migration effort where you'll determine the approach that best meets your requirements.
This could be done on a case-by-case basis (per app/workload) or by looking at the datacenter as a whole.
Essentially in this phase, you're physically moving your workloads and applications (including their data) to the cloud and planning to retire the on-premises versions.
Every customer will have a different approach and mixture of using rehosting, revising, or refactoring for their workloads.
This e-book focuses on the lift-and-shift approach, moving applications running on tradition servers and Virtual Machines to Azure Infrastructure-as-s-Service (IaaS). In many cases, organizations will start with lift and shift to drive rapid migration and early cost savings. Lift and shift involves no change in your app or workload framework or architecture; it simply means exchanging hardware and OS management with the cloud environment. This approach requires confidence regarding two key issues. Can your workload can be easily migrated without too many manual steps? And will your workload function as expected in the cloud? As such, several decision points come into play based on what's being moved, and especially how (or if) you want to access it while the migration is taking place.
The lift-and-shift method most often employed for server or VM migration is real-time replication, due to its flexibility and capability in staged migration. Real-time replication allows the workload to remain online and accessible during the migration. And, as you'll see in the next section, modern tools enable the system to cleanly migrate real-time data even when actively being used.
Real-time replication involves setting up a copy of the workload in the cloud and allowing asynchronous replication to keep these in-sync. This means that while you're building and executing your migration plans, any data or server updates are synced between the copies.
This model also enables groups of VMs to be connected, such as a multi-tiered application or workload. This is important when testing and the final migration cut-over begins. With the system understanding the connections and dependencies between VMs, you can create plans to ensure the VMs are bought up in the correct order when starting. For example, with a simple web app, your database source needs to be available before the application runtime begins.
Using your discovery plans as a guide—and your migration tool of choice—you can configure each VM to replicate to the correct VM instance in your cloud provider. This is also the point when you should define the storage and network connections that you set up initially in the environment creation. Most tools have a mechanism to define the replication timeframe (usually from 30 seconds to 15 minutes). This will be based on your network capability and latency.
Many tools also support application-aware replication automatically. Microsoft applications (such as SharePoint, Dynamics, SQL Server, and Active Directory) and apps from other vendors (including Oracle, SAP, IBM, and Red Hat) can be migrated with applicationaware replication, which ensures the source data consistency before replication. Initial replication is also bandwidth intensive, and mechanisms discussed earlier—like ExpressRoute and Databox—can assist with this. It's something to consider when planning your migration timeline.
Testing is integral to ensuring the system health before final cut-over. Many migration tools have options to start your set of VMs up in an isolated environment, which allows you to mimic the production environment in the cloud. This means you can fully test the application without affecting either the on-premises or cloud production versions. Once replication is complete, simply start your application or workloads using the isolated environment option, while taking time to test your startup script or runbook for any errors. When you're fully satisfied both function as expected, it's time to perform the final cut-over.
Migration tools can also do the final launch in your cloud as well and turn-off the on-premises version. In some cases, you may have to update some DNS records for the new cloud-based workloads. However, if you migrated to use DNS in the cloud as part of your initial environment setup, this may happen automatically.
" To expand globally, we can simply clone the infrastructure that we have running in our US Microsoft Azure datacenter to Azure datacenters in Asia and elsewhere."
Tom Grounds, Chief Information Officer, Coats
As you continue your migration of existing VMs in Azure, this is also the perfect time to continue the path to application modernization. To do this, you can take advantage of your cloud provider, delivering even further cost savings and flexibility.
As you may remember from the migration evolution model, cloud optimization is next logical step following lift and shift, or "rehosting," for your workloads, as you'll find many of them can take advantage of PaaS services.
The PaaS services of immediate interest are containers, app services, and database services. Why look at cloud optimization so soon after migrating? The answer is simple. Now that you have done all the hard work in discovery, analysis, and migration to the cloud, you've made it easier to take the step to PaaS. Plus, you can get more cost benefits through reduced management and operating expense reduction.
A clear place to start is containerization. Containerization provides an OS-level virtualization method used to deploy and run distributed applications without launching an entire VM for each app. With containerization, you get immediate savings on operational expenditure due to a reduced footprint in the cloud. Remember that the smaller your footprint, the more economical it is. Containerization rapidly moves compatible apps to containers (out of large VMs) with no code change. It immediately provides you with the benefit of running multiple apps with no impact in experience to your end-users.
The next consideration in optimization is moving to specific PaaS services. There are a lot of options to choose from, but two to start with are app services and database services due to the ease of the migration activity. In many cases web and mobile applications can migrate to App Services with little refactoring effort.
By moving to PaaS for your suitable apps and databases, you're significantly lowering costs by reducing your footprint and management requirements. You can save an additional 15-20 percent or more by migrating workloads and applications to PaaS over and above the savings you are making today with IaaS.
It's important to note that there will be initial investment of time, effort, and budget to move to more advanced PaaS services. In some cases, you'll have a simple migration where the application is "cloud-ready," but in others configuration changes and code updates may be required. Fortunately, there are tools available that enable you to analyze the code and determine the requirement of effort in moving to App services.
For your databases, this is a straightforward process. Azure provides options for database PaaS services, including Azure SQL, where you are hosting the data on a full DBaaS platform. Azure SQL enables you to host DB data in a service, reducing your database management costs, but has some limitations compared to a full SQL server deployment. If your applications need functionality that may not be available in Azure SQL, then SQL Database Managed Instance is a recommend choice.
SQL Database Managed Instance enables a full platform experience of SQL; however, the underlying OS and SQL service is fully managed by Azure.
As migration of servers and VMs are different for everyone, there are multiple tools available to support your needs. These range from Microsoft tools such as Azure Site Recovery (ASR), and third-party tools as well. Third-party tools are valuable alternatives when you have specific needs not covered by ASR. For example, while there are some OS types ASR can't migrate, various partner tools can extend to support these efforts.
Alternatively, you may have other specific needs like rapid migration (migrating over a hundred VMs per day) where normal replication may not be sufficient. In this case, there are tools that assist in migrating run-time to Azure first while leaving the storage on-premises. Then over time, the storage is replicated. Many options can meet your unique migration needs. Learn more at Azure Migration Center.
For further information on these tools, explore the following resources:
Once you've implemented your cloud migration strategy, you'll want to ensure that you're successfully taking advantage of the cloud's performance, scalability, and costsaving benefits.
This will enable you to only pay for the services and resources you use, achieve a greater ROI, and receive additional savings from leveraging the latest cloud capabilities. This is also the best time to start looking at new services for modernizing your application, migrating to PaaS and even SaaS, where applicable.
On-premises tools are not built for cloud scale and agility. Plus, they're simply not aligned with the new usage models enabled by the cloud. Continual optimization is a critical third step in your migration journey. Optimization targets two main areas—ensuring peak performance and continual cost efficiency.
Once you migrate, you'll additionally want to make sure to keep your VM continuously secure, protect your data, and monitor your cloud health. And that's easy to do with Azure—once you get an understanding of the full suite of controls and capabilities available to you.
Ensuring strong security for your cloud-based resources is a shared responsibility between you and your cloud provider. Azure is built with a foundation of trust and security, compliance, privacy, and transparency. The Azure platform provides a secure foundation to host your infrastructure with built-in security controls and capabilities to help you further protect your data and applications.
Azure Security Center provides unified security management and advanced threat protection across hybrid cloud workloads. The Security Center enables you to take advantage of capabilities such as:
Azure ensures workloads and data are fully backed up and protected from disasters, while providing encryption of stored data for internal and customer security. Azure can also automatically encrypt your stored data—while allowing full accessibility to all applications and users.
As with any system monitoring is important to drive both proactive and reactive analysis. Azure provides a number of monitoring services targeted at applications, workloads and core service health to ensure you have full visibility into current status, and access to important data when working with break-fix situation. In Azure you can use utilize both basic or premium monitoring services.
Basic monitoring provides fundamental, required monitoring across Azure resources. These services require minimal configuration and collect core telemetry that the premium monitoring services use.
Premium monitoring services build on basic monitoring and provide powerful analytics with collected data to give you unique insights into your applications and infrastructure. Plus, they present you with data in the context of scenarios that are targeted to different audiences.
Many premium management solutions are packaged sets of logic that provide insights for an application or service. They rely on Log Analytics to store and analyze the monitoring data that they collect. Azure Log Analytics enables deeper visibility into your hybrid IT environment and allows you to diagnose performance issues from an advanced analytics portal in one click.
Azure Log Analytics enables you to:
Performance monitoring can help you achieve beneficial cost optimization. In the initial discovery, you performed right-sizing for your on-premises workload based on a point in time. Once those workloads are moved to Azure, their usage may change. For example, if you move a moderately-used app from on-premises to Azure, the initial discovery phase may be recommended for the middle-tier VM an D2v3 instance (2 vCPU and 8BG RAM). However, after six months, the use of that application has declined, then you'll want to downsize to a lower VM instance to reduce costs.
Azure Cost Management shows you usage and costs so that you can track trends, detect inefficiencies, and create alerts. All usage and cost data are displayed in intuitive dashboards and reports. With Azure built-in cost management services, you can continually monitor for CPU and memory usage enabling recommendations for VM instances that can be further right-sized. These services can also help you monitor for over-utilized VMs and up-size as needed to ensure performance SLAs. Plus, these services can help you discover under-utilized VMs for potential downsizing. For example, Azure cost optimization can provide you a regular view of your current VM total utilization.
With a quick glance, you can determine the number of VMs that are consistently under-utilized (that is, running below 90 percent). Then, with the Azure cost optimization sizing opportunities, you can find recommendations for which VMs should be actioned, as well as the suggested instance change (including potential annual savings).
As you continue to utilize your new IaaS environment, then targeting maximum cost savings through Azure Reserved VM Instances (RI) becomes attractive. Reporting available in Azure Cost Management can recommend the workloads that would benefit from RIs, maximizing your TCO.
For further information onoptimization tools, explore thefollowing resources:
No matter the reason why your organization is looking to move to the cloud, you shouldn't be put off by its seeming complexity. As you've learned in this e-book, the process is far less daunting once you break it down into its elemental steps.
First, you need a clear plan that takes into careful consideration your servers, VMs, and workloads—and what's required for these to function in the cloud.
Along with this discovery, you need to determine your true resource usage and analyze any configuration dependencies for your workloads. Then, when you go forward with migration, you need to make sure that your workloads in the cloud are in sync with your on-premises system in real time. Along with this, you want to test the health of your system, so that your final cut-over is smooth. Lastly, you should continue your cloud journey by ensuring peak performance and cost efficiency through cloud optimization.
The benefits of your migration will be immediate on your time and budget. The cloud will allow you to be more agile and, in many cases, respond to business needs faster. The cloud may even lower your total cost of ownership (TCO) by as much as 84 percent,9 freeing you to take that massive savings and invest it back into your business to drive modernization faster. Plus, you can explore PaaS and SaaS options, decreasing your TCO even more while expanding your IT capability.
Whether you're in early stages of migration discovery, or planning your approach, keep in mind that migration can easier with a trusted provider like Microsoft. Through integrated tools, a strong partner ecosystem, and rich guidance, you can tread a well forged path to minimize risk and impact to your business.