Migration Portfolio

Manage applications and workloads across the migration lifecycle.

The Migration Portfolio is the business-context view of the estate. It groups applications, workloads, owners, environments, migration state and financial evidence so that decisions are not reduced to AWS resource lists.

Core records

An application can contain one or more workloads; workloads can map to resources and legacy assets. Optional higher-level relationships — business unit, product, cost center and wave — help decision makers understand accountability and portfolio exposure.

Portfolio workflow

Import or create the estate, confirm ownership, assess candidate strategy, resolve readiness blockers, build economics, assign a wave and track transition through dual-run and decommission. Each step has its own evidence and approval requirements.

What the counts mean

An application count comes from customer portfolio records, not from the number of EC2 instances discovered. An empty portfolio after AWS connection is not necessarily a discovery failure: use Legacy Estate & Import or the appropriate application-management workflow.

Concept

AWS resource discovery populates the inventory — it does not automatically create business application records. Applications and workloads must be explicitly imported or created.

Financial context

Cost rollups should use the corresponding historical allocation results or imported source costs. Do not mix an estimated source run rate with a measured AWS run rate without explicit labels, periods and currencies.