Application Portfolio Assessment vs AWS Transform

Organizations starting AWS Migration Acceleration Program (MAP) Phase 1 face a tooling choice. Which assessment platform should they use?

Most start with AWS Transform. It is built by AWS. It produces migration cost estimates, instance recommendations, and agentic execution for VMware, .NET, mainframe, and other workloads.

This is half the picture.

The Problem: Organizations Confuse the Two Assessment Layers

MAP Phase 1 requires both:

• Infrastructure assessment and execution: TCO modeling, instance sizing, and migration or modernization execution
• Application portfolio assessment: Application logic, dependencies, business context, and prioritization

Teams often assume AWS Transform covers both. It does not.

AWS Transform answers: “What will this cost to run on AWS?” and “How do we execute this migration or modernization job?”

It does not answer:

• “Which applications should we migrate first?”
• “What dependencies exist between applications?”
• “Which applications should we modernize versus rehost?”
• “What is the business case for each migration wave?”

Incomplete Phase 1 assessments lead to:

• Migration waves that stall on undocumented dependencies
• Budget requests without business value justification
• Execution plans for applications that should be retired

The Observation: AWS Transform vs Tidal Serve Different Purposes

AWS has consolidated much of its migration assessment surface into AWS Transform, which replaced older services such as Migration Hub Strategy Recommendations and Refactor Spaces for new customers. The standalone Migration Portfolio Assessment (MPA) tool is legacy input data. AWS Transform still accepts MPA exports alongside RVTools and Migration Evaluator, but Transform is the execution engine.

AWS Transform

AWS Transform analyzes infrastructure and workload mechanics:

• CPU, memory, storage, and network utilization
• VMware, .NET, mainframe, and custom code transformation
• AWS instance type recommendations
• TCO and business case outputs

AWS Transform produces:

• Migration and modernization job plans
• Monthly cost estimates
• Agentic code transformation and validation

AWS Transform focuses on how to move and modernize workloads.

Tidal Accelerator

Tidal Accelerator analyzes application logic and portfolio context:

• Application boundaries and components
• Code complexity and technical debt
• Database dependencies and data flows
• API connections and integrations
• Business criticality and owner assignments

Tidal produces:

• Application dependency maps
• Migration complexity scores
• 6R strategy recommendations (rehost, replatform, refactor, etc.)
• Wave sequencing based on dependencies
• Business case per application

Tidal focuses on which apps to move, modernize, or retire — and why.

Three-Line Rule

AWS Transform estimates infrastructure costs for 500 servers
Tidal maps dependencies across 89 applications
Execution without portfolio context misses application complexity

The Recommendation: Tidal Upstream, AWS Transform Downstream

Complete MAP Phase 1 requires both layers. Tidal Accelerator is the portfolio analysis tool. AWS Transform is the execution engine.

Phase 1 Workflow

Step 1: Run Tidal Accelerator on the application portfolio

• Discover application boundaries
• Map dependencies
• Score migration complexity
• Prioritize by business value

Step 2: Run AWS Transform on prioritized workloads

• Collect infrastructure metrics or import RVTools / MPA / Migration Evaluator data
• Generate AWS cost estimates and target architectures
• Plan agentic migration or modernization jobs

Step 3: Integrate findings

• Feed Tidal wave plans and 6R recommendations into AWS Transform job queues
• Align Transform TCO outputs with Tidal application groups
• Present a business case backed by both portfolio and financial analysis

Three-Line Rule

Tidal provides complexity scores and prioritized workloads
AWS Transform provides TCO estimates and execution plans
Together they create complete MAP Phase 1 deliverables

Deliverables Checklist

Complete Phase 1 submission includes:

The Cost: AWS Transform and Tidal Are Free for Qualified MAP Engagements

AWS Transform Cost

AWS Transform is available to customers through AWS migration and modernization programs. Assessment and agentic execution capabilities are part of AWS’s funded migration motion for qualified engagements.

Tidal Accelerator Cost

Tidal Accelerator is free for qualified MAP engagements under the AWS ISV Tooling Program.

Qualification requirements:

• Active or planned MAP engagement
• 30+ applications or 100+ servers in scope
• AWS customer or partner status

What Free Includes

Tidal Accelerator free tier provides:

• Application discovery and mapping
• Dependency analysis
• Migration complexity scoring
• 6R recommendation engine
• MAP-compliant reporting exportable to AWS Transform workflows

No license fees. No per-server charges. No hidden costs.

MAP Funding

AWS MAP provides:

• AWS service credits (10-30% of migration costs)
• Professional services funding
• Tooling subsidies

Both AWS Transform and Tidal Accelerator qualify as MAP-compliant tooling.

The Risk: Choosing the Wrong Layer Delays Migration

Scenario 1: AWS Transform Only

A team runs AWS Transform on 500 servers. Transform estimates $2.1M annual AWS cost. Leadership approves budget. Migration planning begins.

Week 8 of mobilization: Engineers discover that Server A hosts 12 applications. Three applications share a database with hardcoded connection strings. Two applications have undocumented API dependencies on a system marked for retirement.

Result: Migration wave stalls. Dependencies require redesign. Timeline extends 4 months.

Scenario 2: Tidal Without AWS Transform

A team runs Tidal Accelerator. They map 89 applications. They sequence waves based on dependencies. They present a migration plan.

Leadership asks: “What will this cost?”

The team has complexity scores. They have effort estimates. They lack AWS infrastructure costs and execution job plans.

Result: Leadership delays approval. The team runs AWS Transform retroactively. Planning cycle extends 3 weeks.

Three-Line Rule

Transform-only assessments stall on undocumented dependencies
Tidal-only assessments stall waiting for cost approval
Either gap delays migration by months

The Data

Organizations with incomplete Phase 1 assessments experience:

• 40% exceed initial timelines
• 35% exceed initial budgets
• 25% stall in mobilization phase

Source: AWS Migration Partner analysis, 2024

Mitigation

Run Tidal Accelerator and AWS Transform in parallel during Phase 1. Both complete in 2-4 weeks. Together they provide:

• Portfolio prioritization (Tidal)
• Cost estimates and execution plans (AWS Transform)
• Complete foundation for migration planning

Summary

MAP Phase 1 requires both application portfolio analysis and infrastructure assessment.

Tidal Accelerator answers complexity, sequencing, and business case questions. AWS Transform answers cost and execution questions. Neither tool replaces the other.

Use Tidal Accelerator for application portfolio analysis. Use AWS Transform for TCO modeling and migration or modernization execution. Tidal outputs feed AWS Transform with the workloads worth executing.

Both are free for qualified MAP engagements.

Next Step: Start your complete MAP Phase 1 assessment

Tidal Accelerator and AWS Transform are available at no cost for qualified AWS MAP customers.