Cost
What does application modernization cost? The factors first, then illustrative ranges.
No honest price exists before someone has looked at the code. These are the factors that move it, and typical ranges to plan against.
The short answer
Application modernization cost depends mainly on the number and size of applications, test coverage, the target platform and how much domain knowledge is available. As an illustrative range, a single Java upgrade runs from tens of thousands of dollars, while an app-server exit or monolith split costs several times more. Quotes need an assessment.
Factors
What sets the cost?
| Factor | Why it moves the price | Lower cost when | Higher cost when |
|---|---|---|---|
| Number of applications | Each one needs inventory, tests, change and cutover | A few, similar apps | Dozens with different stacks |
| Size and age | More code, more places for old behavior to hide | Small, recent codebase | Large code on Java 6 or 7 |
| Test coverage | Tests are how you prove nothing broke | Strong automated tests | None, so we write them first |
| Target platform | Distance between source and target | Java 8 to 21 on the same server | WebLogic EJB to Spring Boot |
| Coupling | Shared databases and servers spread the change | Clear boundaries | Shared tables and hidden dependencies |
| Access to people | Someone must answer what the code is for | An engineer who knows it | No original authors left |
| Cutover constraints | Parallel runs and change windows add work | Short outage is fine | Zero downtime required |
| Compliance | Evidence and sign-off add effort | Internal tooling | Regulated, audited systems |
Illustrative ranges
What are typical price ranges?
Treat the high end as a warning, not a target. A well-tested application on a supported framework sits near the low end. Missing tests and tangled data push it up.
| Project type | Illustrative range (USD) | What drives it |
|---|---|---|
| Assessment of an estate | 15,000 to 60,000 | Number of applications; fixed price after scope is agreed. See modernization assessment |
| Java upgrade, one application with good tests | 25,000 to 90,000 | Library count, test quality; see Java upgrade |
| Spring Boot 2 to 3 plus jakarta, one application | 30,000 to 110,000 | Custom security, many javax imports; see Spring Boot 3 migration |
| App-server exit, one application (to Tomcat or Spring Boot) | 60,000 to 250,000 | EJB, JMS and server-specific features; see WebLogic migration |
| Monolith decomposition | 250,000 to 1,000,000 and up | Data splitting, cutover, number of services |
Tools
How do AI-assisted tools change the cost?
Tools reduce the cost of the mechanical part: rewriting imports, bumping versions, updating deprecated calls. They do not remove the cost of tests, review, configuration changes or cutover. In our experience review and fixes are the larger share of effort on most upgrades, which is why we record review minutes in our benchmark; results are pending.
A tool that is cheap to run and leaves a long review is not cheap. Ask any provider how much of the estimate is review and testing.
Offsets
What can offset the cost?
Count these in your own numbers. Ours would be guesses about your estate.
- Licence fees you stop paying for a commercial app server. We are building a worked licence-cost model for WebLogic, WebSphere and JBoss EAP; it is not published yet.
- Open vulnerabilities closed on unsupported frameworks.
- Faster releases once the build and tests are in place.
- Infrastructure saved by moving to a smaller runtime.
Savings
How do you keep the cost down?
- Start with an inventory, so you do not pay to migrate an application that should be retired.
- Add tests first. It is the cheapest risk reduction available.
- Phase the work so each phase stands alone and can be stopped.
- Choose open targets, with no new lock-in.
- Agree fixed scope, then fixed price, in that order.
Next step
How do you get a real number?
Book a fixed-price assessment. It inventories applications, measures test coverage, scores risk, names a target for each application and returns a phased roadmap with a fixed price for phase one. There is no commitment to continue. Ace8 is the AI-assisted application modernization practice of AceMQ. If you are comparing providers, see how to choose an application modernization company.
It ranges widely. As illustrative planning numbers, a single Java upgrade runs from tens of thousands of dollars, and app-server exits and monolith splits cost several times more. A real figure needs an assessment.
Per-application cost depends on size, tests and target. Illustrative ranges are in the table above, and they are not quotes.
Scope assumptions differ. Check whether an estimate includes tests, review, configuration changes, cutover and support after go-live.
Yes, once scope is agreed. That is why we assess first and quote after.
No. They are illustrative planning ranges. We will replace them with ranges drawn from quotes once we have enough.
Know the cost before anything moves.
A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.
Book a Fixed-Price AssessmentGet in touch
Talk to a modernization engineer
Tell us what you run today. An engineer, not a sales script, replies within one business day.