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.
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.
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.
| Section | What it determines | What it produced for this customer |
|---|---|---|
| Introduction & Kickoff | Context: sponsors, goals, the first data request | Goals and sponsors recorded; 2 data requests opened; the customer's existing AWS support plan noted as a fact |
| Business Scope & Owners | Context: why now, what is in scope, who owns each system | Ranked business outcomes, change freezes, funding and the owner of the on-premises cost, recorded as decisions and open items |
| Estate Data | Telemetry: the server inventory | Four 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 Discovery | Context joined to telemetry: applications, owners, dependencies | 19 documents read; 12 applications with owners and tiers; 8 dependencies and 5 file shares; servers matched to applications only where the evidence supported it |
| Infrastructure | Decisions: what stays, retires or moves | From 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 & Pricing | Agentic output: sizing, pricing, the business case | Term, 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 & Compile | Agentic output: the plan | 12 waves carrying 41 confirmed servers with environment, cutover window and rollback; 17 risks with owners; 429 = 350 moving + 79 out of scope |
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 exports | Level 2: AWS Transform with measured usage | Level 3: AWS Transform with Sherpa | |
|---|---|---|---|
| What went in | The virtualisation exports | Plus the discovery tool's usage data | Plus nine application questionnaires, the recorded sessions, the planning forms and the business goals |
| Servers AWS Transform priced | 419 | 412 | 343, 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 priced | Nothing. Databases, block and file storage and platform services are outside the figure | Same | Sherpa'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 learned | A compute number for a server list | The sizes improved; the questions did not. Still no owners, no scope decisions | Which 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.
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.

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.