Import a Legacy Estate
Prepare and commit application, workload and legacy financial records.
Legacy data is often the only source for data-center run costs, contracts, depreciation, support and application ownership. CoreFinOps supports a structured import workflow so these numbers can be assessed alongside AWS costs without presenting estimates as billing facts.
Prepare the source
Start with application names, business units, owners, environments and relevant workload/asset identifiers. Add recurring source costs, currency, cost period, confidence and source where available. A sample dataset should be marked synthetic, not used as proof of production savings.
Import workflow
- 1
Open Migration → Legacy Estate & Import
Navigate to the import section from the Migration tab.
- 2
Upload CSV/XLSX or use supported manual entry
The importer accepts spreadsheet files or structured paste input.
- 3
Map incoming columns to CoreFinOps fields
Review unknown columns and required values before proceeding.
- 4
Validate accepted/rejected rows
Check currencies, duplicates, date formats and amounts in the preview.
- 5
Preview the exact commit plan
Correct any errors before accepting. This step is reversible; the commit is not.
- 6
Commit the batch
The backend treats an accepted import as a controlled, transactionally committed operation.
Application and workload identity
The application is the business container; workloads and assets make up its technical and financial footprint. A resource suggestion is not an authoritative mapping until confirmed under the applicable rules.
Common pitfalls
Do not replace historical actual source costs with projected target costs. Avoid mixing one-time migration expenses into monthly recurring run rates. Use the relevant source period and record when the cost is estimated rather than directly observed.
What appears next
Applications and workloads become available in the Migration Portfolio; imported costs can feed assessment and economics. AWS-specific resource inventory and bills remain unavailable until their separate connection/ingestion steps succeed.
Note