India’s Leading Domain & Web Hosting Provider
Support
Domain & Login
Blog
Application Modernization Assessment: 6R Screening of the Portfolio
An application modernization assessment screens an entire portfolio, typically 50-500 applications, and assigns each to a disposition, retire, retain, rehost, replatform, refactor or replace with SaaS, based on business value and modernization effort. NTSPL combines code scanning, owner input and cost data to produce a ranked roadmap that tells CIOs where modernization money earns a return and where it does not.
Delivered on
In scope
Why Modernization Budgets Go to the Wrong Applications
Most portfolios carry a long tail of applications nobody would build again: three tools doing the same approval workflow, a Java 6 system with one remaining user team, a custom HR module next to a licensed HCM suite. Modernization budgets get spent on whichever application has the loudest owner. Meanwhile high-value systems that would genuinely benefit from re-architecture sit on rehost-only plans because nobody compared them across the portfolio.
NTSPL scores every application on two axes. Business value covers users, revenue or regulatory impact, change frequency and strategic fit. Effort covers code size and age, framework support, coupling, test coverage and data complexity, measured with automated code scanning where source is available. The quadrant drives a disposition per application, and the top candidates go forward to deep technical assessment with a funding estimate.
When to Screen the Whole Portfolio
Signals you need Application Modernization Assessment
- 50 or more applications, with duplicate functions across business units
- A modernization budget must be allocated across many owners within one financial year
- More than 20 percent of applications run on unsupported frameworks such as Java 8 or older, .NET Framework 3.5 or VB6
- Licence and support spend on legacy applications is growing faster than IT budget
When to choose something else
- You already know the 1-5 applications to modernize and need code-level design and a backlog: that is a deep modernization assessment.
- The immediate goal is a data-centre exit by a fixed date: profile applications for migration first and screen for modernization afterwards.
Signals Scored for Each Application
Business value
Active users, revenue or regulatory dependence, change requests per year and alignment with the three-year business plan.
Technical health
Language and framework versions, support status, code size, known vulnerabilities and test coverage from automated scans.
Architecture and coupling
Integration count, shared databases, batch dependencies and how hard the app is to separate from others.
Functional overlap
Applications serving the same capability, mapped to a business capability model to expose duplicates.
Cost of ownership
Licence, support, hosting and internal effort per application to show the cost of standing still.
Value-Effort 6R Screening Pipeline
Value-Effort 6R Portfolio Screening Pipeline
Code scans and owner surveys produce value and effort scores per application, mapped against a capability model to expose duplicates. Rules convert the quadrant position into a disposition, and top candidates are costed into a roadmap.
Select any component
Value-Effort 6R Portfolio Screening Pipeline: click any of its 7 components to see its role and the design choice NTSPL makes for it, or trace the 7-step primary path.
Code and Portfolio Analysis Tooling by Cloud
AWS Transform's .NET and mainframe capabilities size effort for those segments of the portfolio, and Marketplace listings help test replace-with-SaaS options.
Application and code assessment scans .NET and Java code for cloud blockers, giving the effort axis real data for Azure targets such as App Service or Container Apps.
The fit assessment scores Linux and Windows workloads for containerisation, informing replatform dispositions toward Cloud Run or GKE.
Disposition Rules We Apply
Disposition by quadrant
High value, low effort: replatform now. High value, high effort: refactor, but only after a deep assessment. Low value, low effort: rehost or retain. Low value, high effort: retire or replace. Override when a platform is unsupported, which forces action, or when a mature SaaS covers 80 percent or more of the functions.
Handling duplicates
Where two or more applications serve one capability, pick the survivor on value and effort, then retire the others with a migration of their data and users. In portfolios over 100 applications, duplicates are commonly 10-20 percent, and retiring them is often the cheapest modernization available.
When source code is unavailable
For ISV products and lost-source custom code, score effort from vendor roadmaps, binary analysis and integration counts. Lean toward replace or retain for these, since refactoring without source is rarely viable. Flag lost-source applications holding critical data for early action.
Funding the roadmap
Group dispositions into waves of 6-12 months with order-of-magnitude costs, plus a three-year cost of standing still per application. Present retirement savings first: they often fund the first refactor wave. Refactor estimates at this stage carry plus or minus 40 percent accuracy until a deep assessment is done.
Six-Week Portfolio Screening
Portfolio intake
Application list, capability model and cost data assembled from IT, finance and procurement.
Code scanning
Repositories scanned for frameworks, vulnerabilities and complexity.
Owner value survey
Surveys completed and validated with usage and incident data.
Scoring and disposition
Value-effort quadrant built, rules and overrides applied.
Roadmap
Costed waves and deep-assessment candidates approved by leadership.
What you receive
Portfolio Outcomes We Track
| KPI | Typical target |
|---|---|
| Applications with disposition | 100 percent of portfolio |
| Applications retired within 18 months | 10-20 percent typical |
| Legacy run cost reduction | 15-25 percent over two years |
| Unsupported frameworks remaining | Under 5 percent after roadmap |
Screening Biases and Countermeasures
| Risk | How NTSPL prevents it |
|---|---|
| Owners inflate value scores | Survey answers checked against usage logs, change requests and incident data. |
| Refactor chosen for technology enthusiasm | Refactor needs high value and a deep assessment before funding. |
| Retirements stall after the report | Each retirement gets an owner, date and data-migration plan in the roadmap. |
Portfolio modernization assessment or deep application assessment: which do we need?
Start with portfolio screening if you have more than about 30 applications and have not yet decided where to invest. It looks at every application at moderate depth and tells you which to retire, replace, rehost, replatform or refactor. A deep assessment examines one to five chosen applications in detail: code, coupling, data model, target architecture and a backlog with effort. Screening without deep assessment leaves refactor estimates too rough to fund; a deep assessment without screening risks modernizing the wrong application. If leadership has already chosen the application, for strategic or regulatory reasons, go straight to the deep assessment.
Key facts: Application Modernization Assessment
Application Modernization Assessment in Practice
2 Application Modernization Assessment scenarios, from BPO and customer experience services and Public sector undertaking (state power generation), plus related platform case studies.
BPO screens 142 client tools and retires 31 duplicates before modernizing on GCP
State PSU ranks 208 applications and funds 12 modernizations from retirements
Real-estate developer handles 40x launch-day traffic on its booking portal
Logistics SaaS scales shipment tracking to 9 crore events a day on EKS with Karpenter
Application Modernization Assessment: Frequently Asked Questions
How long does a portfolio modernization assessment take?
Six weeks for 100-250 applications. Code scanning and owner surveys run in parallel, and the pace is mostly set by owner response rates. Portfolios near 500 applications take eight to ten weeks. Code scanning effort grows with repository count more than with lines of code.
What does an application modernization assessment of the whole portfolio cost?
Typically 0.2-0.3 consultant days per application, plus licences for any third-party scanning tool. A 150-application portfolio usually needs 30-45 days of effort in total. Retirements identified usually cover the fee within the first year of savings.
Does a portfolio-level modernization assessment need access to our source code?
It improves accuracy but is not mandatory. Scans run inside your environment so code does not leave it. Where source is unavailable, we score effort from vendor information, binaries and integrations. Scan results stay with you, and only summary metrics enter the report.
How do public sector or regulated organisations handle replace-with-SaaS?
SaaS options are checked for Indian data residency, DPDP Act 2023 obligations and sector rules such as RBI outsourcing requirements. Government bodies also check procurement routes such as GeM. Options that fail are removed before scoring. This stops non-viable SaaS options from distorting the quadrant.
Is the 6R disposition final?
No. It is a portfolio decision that sets direction. Refactor and replatform choices are confirmed in deep assessments, and the portfolio is re-scored annually as business priorities change. Re-scoring takes about a third of the original effort because the data model already exists.
How does this relate to cloud migration waves?
Dispositions feed migration planning: retire candidates are removed before migration, rehost candidates move first, and refactor candidates may be migrated as-is then modernized, or held until rebuilt. Retire candidates are removed before wave planning so they are never migrated at all.