Migration Evaluator – Getting your Business Case Started for AWS

In this video, you’ll see how to fast track yourbusiness case for AWS with Migration Evaluator (formerly TSO Logic).

Organizations of all sizes are migrating hundredsof thousands of applications to AWS.

The key to a successful migration strategyis having a business case that can quantify your return on investment before, during, and after migrating each application.

Creating a business case on your own can bea time-consuming process that may take weeks and doesn’t automatically identify the bestdeployment and purchasing options.

Even the most experienced organizations are likely to create a migration plan based on what’s known, rather than what’s possible.

Migration Evaluator is an assessment servicedesigned to help AWS customers make faster and smarter migration decisions.

The service includes a team of experts who can help you define and achieve your migration objective.

Examples of migration objectives include exitinga data center, shifting from capital expenses to operating expenses, or changing softwarelicensing strategies.

Based on your migration objective, MigrationEvaluator builds a data-driven business case for migrating your existing workloads to AWS, automatically recommending the most cost-effective AWS deployment options.

The service can deliver up to 80% savingsfor database workloads and, on average, a 30% reduction in server costs.

To get started with Migration Evaluator, navigate to the product page on the AWS site, and then click Start building your business case.

On the page that opens, scroll down, and provideyour information to request an assessment.

Soon after submitting your request, you’llreceive an email with an invitation to create an account on the Migration Evaluator website.

Provide your email and create a password.

Then, agree to the terms and sign up.

Once you are signed in to the site, you canbegin your on-premises inventory discovery.

To see the methods of discovery availableto you, navigate to the Tools page.

Here, you have two options for providing informationon the environments you want to migrate.

The first option is to use the on-premisesdata collector, which you can install in your data center to collect information and reportit back to the Migration Evaluator.

You can review the provided documentationto learn how to install and operate the collector.

Let’s return to the Tools page.

To deploy the collector, you’ll need tofollow the rest of the steps here.

For now, let’s select View and ConfigureCollectors.

On this screen, you can review and access specific information needed to deploy an on-premises data collector in your organization, such as the encryption certificate, the Amazon Simple Storage Service (Amazon S3) synchronizationpath where collected data is stored, and access keys.

Let’s return to the Tools page to reviewthe second option for providing server information.

You can import an Excel file.

This page provides the Excel inventory templatefor manually entering information about the environments you want to migrate to AWS.

Let’s take a look.

The Glossary tab provides descriptions ofall the fields in the template.

The Template tab is where you can provideinformation on the servers in your environment.

When your template is filled out, return to the Tools page in Migration Evaluator to import the file.

Select View and Import Files.

Then, upload your file here.

Once you have finished providing your migrationdata, either through the on-premises connector or a self-reported file, a team of solutionspecialists at AWS will review the information and reach out to deliver a full business caseevaluation for your review.

Let's take a quick look at some of the informationcontained in this sample business case summary.

The business case summary includesfive main sections.

In the Overview, we can see a count of serversand attached block storage discovered by the agentless collector during the collectionperiod.

SQL Server licenses were also discovered bythe collector, in addition to environment and application groupings of business data.

In the Executive Summary, we can see thatby simply running current workloads on Amazon Elastic Compute Cloud (Amazon EC2) and ElasticBlock Storage, the projected savings would be significant over modeled on-premises infrastructurecosts.

Additionally, many of the monitored serverswere rarely used, providing opportunities to leverage the elasticity of AWS to right-sizethe workloads as part of the migration.

The Data Insights page displays the percentageof time servers were used, environment insights, and licensing details.

The pie chart shows that this company’sservers were in use less than 50% of the time.

In the table, you can see how Windows andLinux workloads were split, and the number of servers that had no detected activity andshould be considered for retirement.

In the Cost Modeling section of the businesscase, we can see two three-year savings plans.

In the first savings plan, Microsoft licensesare provided by AWS.

This report includes the number of SQL Serverlicenses AWS would provide as part of the cost.

In the second savings plan, the company leveragesits existing SQL Server licenses on AWS.

This report includes the number of SQL Serverlicenses it would need, as well as the projected cost to pay Microsoft for the licenses.

Finally, the business case suggests next stepsto help this customer move forward with its migration.

You’ve just seen how to fast track yourbusiness case for AWS in Migration Evaluator.

To request a business case assessment, visitthe Migration Evaluator website.

Thanks for watching.

Now it's your turn to try.


Give a Comment