Discovery
Application Discovery
Understand your full application portfolio — scope, criticality, ownership, and technology landscape — before planning your migration.
Overview
Application Discovery gives you a multi-tab executive dashboard that slices your application estate across scope, criticality, environment, owner, vendor, technology stack, and architecture type. It is designed to answer the question: what are we migrating and who owns it?
Executive Summary
Total counts, scope split, and criticality breakdown at a glance.
Portfolio Breakdown
Top owners, business units, and vendor concentration.
Technology Landscape
Platform distribution, architecture types, and tech stacks.
When to Use
- At the start of a migration project to baseline the application estate
- When briefing stakeholders on scope and risk
- To identify which business units or owners need to be engaged
- To spot technology concentration risks (e.g. a single vendor or platform)
Dashboard Tabs
| Tab | What it shows |
|---|---|
| Executive Summary | Total apps, in-scope vs out-of-scope split, apps by criticality (Critical/High/Medium/Low), apps by environment, apps by type. Quick KPI cards at the top. |
| Portfolio Breakdown | Top application owners (by count), top business units, top vendors, average apps per owner. |
| Technology Landscape | Platform distribution (Windows/Linux/SaaS/etc.), architecture types (Monolith/Microservices/etc.), technology stacks, data classifications, install types. |
How to Use
1
Navigate to Discovery → Data Quality & Discovery → Application Discovery.
2
Review the Executive Summary tab. Check the total application count and the in-scope vs out-of-scope ratio. A large out-of-scope percentage may indicate the CMDB import needs review.
3
Switch to Portfolio Breakdown to identify owners with many applications. These are the key contacts to engage early.
4
Open Technology Landscape to review platform and architecture distribution. Flag any applications on unsupported platforms or with complex architectures for extra attention during planning.
Key Metrics & Fields
| Metric / Field | Description |
|---|---|
| Total Applications | All application records in the CMDB regardless of scope. |
| In-Scope / Out-of-Scope | Applications flagged as in or out of the migration scope. |
| Criticality | Business criticality rating: Critical, High, Medium, or Low. |
| Environment | Production, Development, Test, UAT, etc. |
| Application Type | Classification such as Business Application, Infrastructure Tool, or Custom. |
| Owner | The person responsible for the application. |
| Business Unit | The organisational unit that owns the application. |
| Vendor | The software vendor or supplier. |
| Platform | The underlying platform (Windows Server, Linux, SaaS, etc.). |
| Architecture Type | Monolith, Microservices, Serverless, etc. |
| Technology Stack | Runtime and framework (e.g. .NET, Java, Node.js). |
| Data Classification | Sensitivity level of data processed (Public, Internal, Confidential, etc.). |
| Install Type | On-Premises, Cloud-Hosted, SaaS. |
Tips & Common Mistakes
If the Executive Summary shows a high number of unknown criticality or environment values, go to the CMDB Applications list and bulk-update these fields before using this dashboard for reporting.
Use the Portfolio Breakdown to produce a stakeholder engagement list — export the top owners and business units and share with your project manager.
This dashboard reflects the current state of CMDB data. It is only as accurate as the underlying application records. Run a CSV import or integration sync before presenting this to stakeholders.