OSGi and Apache framework migration scoping service

When a team decides to move off a legacy Struts or Wicket application — or gets handed one to modernize — they face a specific, recurring crisis: nobody on the team understands the framework well enough to estimate the work accurately, and they can't afford to hire a specialist just to scope the project. Struts applications are described as 'not transparent, making them harder to understand and optimize,' and Wicket is 'starting to show its age' — both are signals that migration is on the table for a lot of teams right now.

This gap persists because the people who know these frameworks well enough to do migration scoping accurately are senior consultants billing at rates that make a scoping engagement itself a budget conversation. There's no productized middle ground between 'figure it out yourself' and 'hire a consulting firm.' The consultants who do this work have no incentive to productize it — every engagement they keep bespoke is more billable hours.

What teams get wrong when they try to scope this themselves is underestimating framework-specific complexity: OSGi bundle dependency graphs that break in non-obvious ways during refactoring, Struts action classes with implicit state that doesn't map cleanly to modern MVC, Wicket's stateful component model creating session bloat they didn't know existed. The complaints about Felix causing 'issues during troubleshooting traditional applications' and Sling not handling 'all user requests' are exactly the kinds of hidden landmines that blow up migration estimates.

A productized scoping report — delivered in two weeks, fixed price — that analyzes a codebase and outputs a structured risk map, migration path, and effort estimate is a business because migrations happen once per application but organizations have many applications, and the same team often handles several over years. More importantly, a reliable scoping report is the prerequisite to getting budget approved internally, so the buyer is motivated to pay for it to unlock a larger project.

What to build

Build a fixed-price, two-week codebase analysis service that takes a Struts, Wicket, Felix, or Sling application, runs automated static analysis plus expert review, and delivers a structured migration risk report with effort estimates per module, known anti-pattern flags, and a recommended modernization sequence.

Where to start

Start exclusively with Struts-to-Spring migrations, which are the most common and most urgent — Struts had a high-profile security history that created executive pressure to migrate, meaning budget is often already approved and teams are actively looking for scoping help right now.

The hard part

The hardest early problem is proving the report is accurate enough to trust — the first few clients are essentially paying to validate your methodology, and if an estimate is badly wrong, you lose credibility in a market that runs almost entirely on word of mouth.

How it makes money

Fixed fee per scoping engagement ($4,000-$8,000 depending on codebase size), with an optional retainer for ongoing architecture review during the migration itself.