CASE STUDY · OCTOBER 22, 2026

A 350-server AWS migration, priced at three levels of detail.

How one customer used Sherpa's Migration Assessment to see what server exports, measured usage and business context each add to an AWS migration price.

429servers reviewed
350servers the business agreed to move
$630,987three-year AWS cost, priced lines
100%of figures trace to a source

Business description

The customer already runs its production systems on AWS. Its development and engineering estate still runs on very old hardware, on operating systems and software past vendor support and without current licences. Every patch cycle costs engineering hours the team would rather spend on product, and each year on that hardware adds risk the leadership team can see but could not yet price.

The question for the leadership team was practical: what does it cost to bring that estate to AWS, which servers should move, and how much detail do we need before we commit? The customer did not connect its production AWS accounts to Sherpa. It shared the facts about that environment, and Sherpa's agent relied on what it was told.

The challenge

  • The facts lived in pieces. Server exports from two virtualisation environments, a discovery tool's usage data, nine application questionnaires, recorded planning sessions and planning forms each held part of the picture. No two sources agreed on the server count.
  • A server list is not a plan. Knowing what runs on a box says nothing about what it is for, who owns it, what depends on it, or whether the business wants it in the cloud at all.
  • Automated sizing needs a referee. AWS Transform sizes and prices servers quickly, but it works only from the files it is given. It does not know which servers the customer has already decided to retire or keep.
  • A one-person cloud team. The engineering lead carried cost, security and infrastructure decisions alone. There was no Cloud Center of Excellence to gather requirements, hold the context and guide the decision.

Sherpa as the customer's AI Cloud Center of Excellence

A Cloud Center of Excellence captures the business context (what each system is for, who owns it, what the business expects from the move), gathers the telemetry (what the servers really do), and turns both into decisions the business can act on. Sherpa's Migration Assessment does that work as one guided conversation across seven sections.

Sherpa worked through nine application questionnaires and more than 130 questions. It read each document, repeated back what it understood, recorded only what the customer confirmed, and asked when a document was silent. Nothing was assumed, and what was still unknown was shown as unknown, never as zero.

SectionWhat it determinesWhat it produced for this customer
Introduction & KickoffContext: sponsors, goals, the first data requestGoals and sponsors recorded; 2 data requests opened; the customer's existing AWS support plan noted as a fact
Business Scope & OwnersContext: why now, what is in scope, who owns each systemRanked business outcomes, change freezes, funding and the owner of the on-premises cost, recorded as decisions and open items
Estate DataTelemetry: the server inventoryFour exports combined into 429 servers, 216 with measured usage; duplicates listed; scope proposed from the documents and confirmed; readiness checked before any automated sizing
Workload & Domain DiscoveryContext joined to telemetry: applications, owners, dependencies19 documents read; 12 applications with owners and tiers; 8 dependencies and 5 file shares; servers matched to applications only where the evidence supported it
InfrastructureDecisions: what stays, retires or movesFrom three recorded sessions: 67 servers stay, 4 retire, 28 more confirmed to move; the scope settled at 350; the customer's right-sizing holds recorded
Target State & PricingAgentic output: sizing, pricing, the business caseTerm, AWS support plan and storage growth recorded; AWS Transform's results checked against the scope; two prices side by side; the customer's choice recorded
Review & CompileAgentic output: the plan12 waves carrying 41 confirmed servers with environment, cutover window and rollback; 17 risks with owners; 429 = 350 moving + 79 out of scope

Three levels of pricing, one estate

The customer was offered the price at three levels of detail, and could have stopped at any of them. The same servers were run through AWS Transform each time, with more context added at each level.

Level 1: AWS Transform on the server exportsLevel 2: AWS Transform with measured usageLevel 3: AWS Transform with Sherpa
What went inThe virtualisation exportsPlus the discovery tool's usage dataPlus nine application questionnaires, the recorded sessions, the planning forms and the business goals
Servers AWS Transform priced419412343, from a scope of 350 the business agreed
AWS Transform's own estimate, a year (compute, licences and network)$214,351 on a three-year Compute Savings Plan$232,262, 8% higher: the servers were busier than assumed$163,240 on a three-year Reserved Instance
What else is pricedNothing. Databases, block and file storage and platform services are outside the figureSameSherpa's full priced lines: compute, databases, block and file storage, platform and network: $210,329 a year, $630,987 over three years
What the business learnedA compute number for a server listThe sizes improved; the questions did not. Still no owners, no scope decisionsWhich 79 servers to keep or retire, who owns what moves, a wave plan with servers in it, the risks with owners, and a price it can trace line by line

The more context Sherpa had, the better its answer. With the business goals and application context beside the telemetry, it cut the scope from 425 servers to the 350 the business meant to move, honoured the customer's own right-sizing decisions, and priced the databases, storage and platform services that a server-only estimate leaves out. Level 3's figure leaves out the AWS support plan, which the customer already pays for on its production accounts.

Results and business impact

  • The three-year figure. The priced lines come to $210,329 a year, $630,987 over three years, for 350 servers in scope. It is a cost estimate, not a saving: no on-premises cost was supplied.
  • Every figure is traceable. All 264 numbers in the assessment's outputs traced to the pricing workbook or a recorded answer; none was invented.
  • Measured accuracy. This engagement scored 99.5% with exports and usage data, and 98.3% with every input, against our 98% bar.
  • A plan with servers in it. The wave plan carries 41 confirmed servers across 12 waves, each with its application, environment, cutover window and rollback, and 17 risks with named owners.

For the leadership team, the result is a migration budget they can defend line by line, a scope the business agreed, and the open questions listed instead of hidden inside a total.

Sherpa mascot holding a map

Find out what's really happening in your AWS cloud.

On a 30-minute onboarding call, our team connects your AWS organization with you using one CloudFormation template. Your first cost data usually arrives within 24 to 48 hours.

After you sign up, a member of the Sherpa team contacts you within one business day to discuss your AWS environment and the right way to start.