Migration Evaluator (formerly TSO Logic)

Name: Migration Evaluator (formerly TSO Logic)
Brand: Amazon Web Services (AWS)

Leader

Official Global LinkedIn page for Amazon Web Services (AWS).

Est 2006|Valuation $2560B|1 Ref Customers

LinkedIn 10.9M|Website|Web traffic 1.1M|FTEs 148,001|HQ Seattle, Washington, US

MarketsCloud Management & FinOps

Migration Evaluator (formerly TSO Logic) screenshot

Published Oct 13, 2026

01Common complaints

1. Not committed to AWS as a target. - If an organization is comparing AWS, Azure, and GCP and requires a neutral TCO, consider independent assessment tools or parallel analyses (e.g., Azure Migrate for Azure-bound, plus a third-party tool for neutrality). 2. Need continuous discovery/CMDB accuracy as the primary outcome. - Consider dedicated discovery/CMDB platforms (e.g., Device42) if the goal is long-term asset management rather than an assessment snapshot. 3. Small environment (e.g., a few dozen servers) where a rough estimate is sufficient. - The process overhead may outweigh benefits; a simpler sizing exercise and cloud provider pricing calculators can be faster. 4. Strict governance constraints around account creation/data movement. - If AWS-managed assessment accounts and lifecycle controls are difficult to reconcile with internal policy, a fully internalized approach may be preferable. 5. Need strong independent peer reviews and benchmarks. - Migration Evaluator has limited direct review visibility; alternatives with stronger public review footprints may be easier to evaluate.

Deal disqualifiers

Organizations that require a cloud-provider-neutral assessment deliverable.
Organizations that rely primarily on crowdsourced, third-party validated product reviews to drive selection.
Organizations that want a lightweight self-serve tool with minimal stakeholder involvement.

Limitations acknowledged or implied by documentation

- Data sensitivity: AWS provides guidance to anonymize sensitive network data for regulated environments, implying raw exports may contain sensitive details that require handling. - Assessment snapshot nature: focuses on producing a business case rather than continuous lifecycle management. - File/upload constraints in adjacent tooling: AWS Transform documentation (which can consume Migration Evaluator exports) mentions limits like server counts per assessment job and file size limits for uploads—suggesting some operational constraints in workflows that integrate assessment artifacts.

Roadmap / future direction signals

AWS Transform content suggests AWS is increasingly using AI-assisted assessments and can consume Migration Evaluator exports. This may indicate a future where parts of Migration Evaluator’s functionality are integrated into broader Transform/assessment experiences.

Where it struggles / is not ideal

Deep application dependency mapping and modernization sequencing can require more specialized tooling and workshops beyond what a TCO assessment captures.
If stakeholders expect high precision without human validation, results may be misleading—human validation is typically necessary.

02Why they buy

Apparent differentiators (with evidence caveats)

AWS-aligned right-sizing and licensing scenario modeling (BYOL vs License Included) is a consistent theme in AWS documentation.
Alignment with MAP-style migration processes: Migration Evaluator is positioned as part of AWS’s structured migration approach (Assess → Mobilize → Migrate/Modernize).

Where competitors may have an advantage

Azure Migrate: clearer public pricing mechanics and a broad integrated migration hub.
Third-party tools: may provide deeper cross-cloud neutrality, broader integrations, and more flexible reporting.

03Field reports

Important limitation: scarcity of direct end-user reviews on major review platforms

Unlike typical SaaS products, Migration Evaluator is an AWS assessment offering and does not appear to have a robust, easily-accessible footprint of direct reviews on platforms like G2/TrustRadius for the product specifically. - Some third-party blogs claim high counts/ratings for “AWS Migration Evaluator” on Gartner/G2, but these claims were not validated via direct listings and may reflect category-level confusion or misattribution. - Review platforms can also be noisy/incentivized; several community discussions suggest G2-style platforms may contain incentivized or manipulated review patterns — relevant when evaluating any reported star ratings.

Vendor-published testimonials (positive)

AWS publishes customer quotes on its Migration Evaluator customer page. Example quote: - “Using insights from Migration Evaluator, we reduced our technology costs by a substantial amount by running on AWS instead of our data center.” (Customer name/context not included in the snippet we accessed; this is vendor-hosted and not independently verified.) Critical note: These are marketing testimonials; they often lack methodological detail (baseline assumptions, time horizon, included/excluded costs, and whether results reflect rightsizing, vendor discounts, or architectural changes).

Community discussions (mixed / more operational nuance)

Direct Migration Evaluator user discussion is limited, but there is some community content about how it relates to other discovery tooling. From Reddit community: - A thread explicitly compares Migration Evaluator vs Application Discovery Service, indicating practitioner confusion about overlapping roles and nuances between inventory discovery approaches. - In a separate migration-advice thread, commenters note that MAP (AWS’s migration program) may require minimum spend/qualification and that vendor-promoted no-charge offers may not apply to smaller estates — relevant because Migration Evaluator often appears in MAP-related contexts.

Common reasons customers choose it (inferred from vendor positioning + community patterns)

Desire for an AWS-backed TCO model and a business case suitable for executive review.
Need for a structured assessment in MAP-style migration motions.
VMware/on-prem estates where rightsizing and licensing scenarios are material to TCO.

Common reasons customers might not choose it / may churn away

If an organization wants a cloud-neutral assessment, Migration Evaluator’s alignment with AWS recommendations may be perceived as biased.
If the organization already standardized on Azure or GCP assessment stacks, they may prefer native equivalents.
If the organization needs continuous discovery and CMDB-quality data, Migration Evaluator may be more assessment-centric than ongoing discovery platforms.

AWS customer stories / quotes

AWS hosts Migration Evaluator customer content and highlights cost reduction claims (e.g., a notable percentage reduction in one quote).

Critical evaluation:

These are vendor-selected success examples.
Typically missing: exact workload composition, migration pattern (lift/shift vs re-platform), discounting assumptions, costs of migration services, and whether savings persist after steady state.

Partner-led deliverables via AWS Marketplace (case-study-adjacent)

AWS Marketplace listings show partners selling Migration Evaluator-based engagements with deliverables such as:

TCO report
reference architecture
statement of work for migration

Critical evaluation:

The experience and quality can vary by partner.
Buyers should request sample deliverables and validate assumptions.

04Best fit

Company sizes

Best fit tends to be:

Mid-market to large enterprises, especially organizations with sizable server fleets where rightsizing and licensing optimization materially impact TCO.

Industries

Regulated industries appear in AWS guidance around anonymization for protected environments (public sector pattern).
Strong fit for VMware-heavy shops (AWS messaging and partner offerings often emphasize VMware estate assessment).

Roles and personas

Decision makers: CIO/CTO, VP Infrastructure, Head of Cloud/Platform
Influencers: FinOps, enterprise architecture, security/compliance
End users: infrastructure engineers, migration factory teams, partner solution architects

Fit qualifiers

Organizations that are seriously considering AWS and need a business case suitable for executive review.
Organizations with sufficient inventory/utilization data (or willingness to collect it) to support modeling.
Organizations that want AWS/partner involvement to support planning and accelerate migration readiness.

05The pitch

What the product does (objective core value proposition)

Amazon Migration Evaluator (an AWS service) is a business-case and migration-planning assessment offering intended to help organizations build a data-driven TCO (total cost of ownership) and migration plan for moving on-premises (and sometimes other-cloud) workloads to AWS. It combines: - Inventory/imported discovery data (from exports or discovery tooling) - Right-sizing and cost modeling (EC2/EBS recommendations, licensing scenarios like BYOL vs License Included) - Consultative involvement (AWS and/or partner migration experts) AWS describes the product as intended to reduce estimation uncertainty, identify over-provisioned infrastructure, and model multiple migration scenarios, including licensing reuse. The vendor also cites scenario-based claims of substantial cost reductions; these claims are scenario-dependent and lack a published, independently verifiable methodology. Primary output is typically a packaged assessment deliverable (TCO/business case, roadmap inputs, quick insights exports) rather than an always-on operational tool. Official vendor product overview and feature pages.

Target market and market positioning

- Target users: enterprise and upper mid-market IT leadership (CIO/CTO organizations), infrastructure teams, cloud centers of excellence, finance/FinOps stakeholders who need a defensible cost case. - Where it sits in AWS migration stack: commonly used in the Assess phase (often referenced alongside the AWS Migration Acceleration Program (MAP) framework and other assessment tooling). - Typical triggers: data center exit, VMware estate cost pressure, hardware refresh avoidance, shifting CapEx → OpEx, licensing strategy change.

Get a comprehensive analysis of Migration Evaluator (formerly TSO Logic) including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 13, 2026

01Common complaints

Not committed to AWS as a target.
- If an organization is comparing AWS, Azure, and GCP and requires a neutral TCO, consider independent assessment tools or parallel analyses (e.g., Azure Migrate for Azure-bound, plus a third-party tool for neutrality).
Need continuous discovery/CMDB accuracy as the primary outcome.
- Consider dedicated discovery/CMDB platforms (e.g., Device42) if the goal is long-term asset management rather than an assessment snapshot.
Small environment (e.g., a few dozen servers) where a rough estimate is sufficient.
- The process overhead may outweigh benefits; a simpler sizing exercise and cloud provider pricing calculators can be faster.
Strict governance constraints around account creation/data movement.
- If AWS-managed assessment accounts and lifecycle controls are difficult to reconcile with internal policy, a fully internalized approach may be preferable.
Need strong independent peer reviews and benchmarks.
- Migration Evaluator has limited direct review visibility; alternatives with stronger public review footprints may be easier to evaluate.

Deal disqualifiers

Organizations that require a cloud-provider-neutral assessment deliverable.
Organizations that rely primarily on crowdsourced, third-party validated product reviews to drive selection.
Organizations that want a lightweight self-serve tool with minimal stakeholder involvement.

Limitations acknowledged or implied by documentation

Data sensitivity: AWS provides guidance to anonymize sensitive network data for regulated environments, implying raw exports may contain sensitive details that require handling.
Assessment snapshot nature: focuses on producing a business case rather than continuous lifecycle management.
File/upload constraints in adjacent tooling: AWS Transform documentation (which can consume Migration Evaluator exports) mentions limits like server counts per assessment job and file size limits for uploads—suggesting some operational constraints in workflows that integrate assessment artifacts.

Roadmap / future direction signals

AWS Transform content suggests AWS is increasingly using AI-assisted assessments and can consume Migration Evaluator exports. This may indicate a future where parts of Migration Evaluator’s functionality are integrated into broader Transform/assessment experiences.

Where it struggles / is not ideal

Deep application dependency mapping and modernization sequencing can require more specialized tooling and workshops beyond what a TCO assessment captures.
If stakeholders expect high precision without human validation, results may be misleading—human validation is typically necessary.

02Why they buy

Apparent differentiators (with evidence caveats)

AWS-aligned right-sizing and licensing scenario modeling (BYOL vs License Included) is a consistent theme in AWS documentation.
Alignment with MAP-style migration processes: Migration Evaluator is positioned as part of AWS’s structured migration approach (Assess → Mobilize → Migrate/Modernize).

Where competitors may have an advantage

Azure Migrate: clearer public pricing mechanics and a broad integrated migration hub.
Third-party tools: may provide deeper cross-cloud neutrality, broader integrations, and more flexible reporting.

03Field reports

Important limitation: scarcity of direct end-user reviews on major review platforms

Some third-party blogs claim high counts/ratings for “AWS Migration Evaluator” on Gartner/G2, but these claims were not validated via direct listings and may reflect category-level confusion or misattribution.
Review platforms can also be noisy/incentivized; several community discussions suggest G2-style platforms may contain incentivized or manipulated review patterns — relevant when evaluating any reported star ratings.

Vendor-published testimonials (positive)

AWS publishes customer quotes on its Migration Evaluator customer page. Example quote:

“Using insights from Migration Evaluator, we reduced our technology costs by a substantial amount by running on AWS instead of our data center.” (Customer name/context not included in the snippet we accessed; this is vendor-hosted and not independently verified.)

Critical note: These are marketing testimonials; they often lack methodological detail (baseline assumptions, time horizon, included/excluded costs, and whether results reflect rightsizing, vendor discounts, or architectural changes).

Community discussions (mixed / more operational nuance)

Direct Migration Evaluator user discussion is limited, but there is some community content about how it relates to other discovery tooling.

From Reddit community:

A thread explicitly compares Migration Evaluator vs Application Discovery Service, indicating practitioner confusion about overlapping roles and nuances between inventory discovery approaches.
In a separate migration-advice thread, commenters note that MAP (AWS’s migration program) may require minimum spend/qualification and that vendor-promoted no-charge offers may not apply to smaller estates — relevant because Migration Evaluator often appears in MAP-related contexts.

Common reasons customers choose it (inferred from vendor positioning + community patterns)

Desire for an AWS-backed TCO model and a business case suitable for executive review.
Need for a structured assessment in MAP-style migration motions.
VMware/on-prem estates where rightsizing and licensing scenarios are material to TCO.

Common reasons customers might not choose it / may churn away

If an organization wants a cloud-neutral assessment, Migration Evaluator’s alignment with AWS recommendations may be perceived as biased.
If the organization already standardized on Azure or GCP assessment stacks, they may prefer native equivalents.
If the organization needs continuous discovery and CMDB-quality data, Migration Evaluator may be more assessment-centric than ongoing discovery platforms.

AWS customer stories / quotes

AWS hosts Migration Evaluator customer content and highlights cost reduction claims (e.g., a notable percentage reduction in one quote).

Critical evaluation:

These are vendor-selected success examples.
Typically missing: exact workload composition, migration pattern (lift/shift vs re-platform), discounting assumptions, costs of migration services, and whether savings persist after steady state.

Partner-led deliverables via AWS Marketplace (case-study-adjacent)

AWS Marketplace listings show partners selling Migration Evaluator-based engagements with deliverables such as:

TCO report
reference architecture
statement of work for migration

Critical evaluation:

The experience and quality can vary by partner.
Buyers should request sample deliverables and validate assumptions.

04Best fit

Company sizes

Best fit tends to be:

Mid-market to large enterprises, especially organizations with sizable server fleets where rightsizing and licensing optimization materially impact TCO.

Industries

Regulated industries appear in AWS guidance around anonymization for protected environments (public sector pattern).
Strong fit for VMware-heavy shops (AWS messaging and partner offerings often emphasize VMware estate assessment).

Roles and personas

Decision makers: CIO/CTO, VP Infrastructure, Head of Cloud/Platform
Influencers: FinOps, enterprise architecture, security/compliance
End users: infrastructure engineers, migration factory teams, partner solution architects

Fit qualifiers

Organizations that are seriously considering AWS and need a business case suitable for executive review.
Organizations with sufficient inventory/utilization data (or willingness to collect it) to support modeling.
Organizations that want AWS/partner involvement to support planning and accelerate migration readiness.

05The pitch

What the product does (objective core value proposition)

Inventory/imported discovery data (from exports or discovery tooling)
Right-sizing and cost modeling (EC2/EBS recommendations, licensing scenarios like BYOL vs License Included)
Consultative involvement (AWS and/or partner migration experts)

AWS describes the product as intended to reduce estimation uncertainty, identify over-provisioned infrastructure, and model multiple migration scenarios, including licensing reuse. The vendor also cites scenario-based claims of substantial cost reductions; these claims are scenario-dependent and lack a published, independently verifiable methodology.

Primary output is typically a packaged assessment deliverable (TCO/business case, roadmap inputs, quick insights exports) rather than an always-on operational tool.

Official vendor product overview and feature pages.

Target market and market positioning

Target users: enterprise and upper mid-market IT leadership (CIO/CTO organizations), infrastructure teams, cloud centers of excellence, finance/FinOps stakeholders who need a defensible cost case.
Where it sits in AWS migration stack: commonly used in the Assess phase (often referenced alongside the AWS Migration Acceleration Program (MAP) framework and other assessment tooling).
Typical triggers: data center exit, VMware estate cost pressure, hardware refresh avoidance, shifting CapEx → OpEx, licensing strategy change.

Get a comprehensive analysis of Migration Evaluator (formerly TSO Logic) including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →