Marcus Biel.

Java modernization and migration

Modernize the Java applications your business depends on

Your Java application supports important business processes. Now you need new features, updated dependencies or connections to other systems.

I assess the part of the system that needs work, then plan upgrades your team can test and release one at a time.

I’m Marcus Biel. I’ve worked with Java since 2001, and I’ll help plan the migration and make the changes in your codebase.

What do you need your application to do better?

Often a new requirement exposes a problem the team has been working around for years.

You might recognize one of these situations.

  • Adding a small feature means editing several unrelated parts of the code.
  • An old dependency is holding up an upgrade.
  • It’s hard to add an integration the business needs.
  • A change is risky because tests don’t cover the workflows people rely on.
  • Only a few people know how core parts of the application work.
  • You need to know what has to change before committing to a major investment.

I start with the business goal. What does the application need to do in future? That tells me which parts need to change and where to begin.

Changes I can make

Update Java versions and dependencies

I review the versions, frameworks and libraries in use and what depends on them.

I then plan and implement changes to the code, configuration and build. I verify the migration against the features and interfaces it affects.

Restructure parts that have grown difficult to change

Refactoring can help when your team has to trace a change through several packages just to find out which one owns a business rule.

I follow the affected workflow in the code and identify what belongs together. That might mean separating two responsibilities, changing how a module handles data, or making its interface explicit.

See how an architecture review works

Replace individual components

Sometimes one component has outlived its usefulness even though the rest of the system still works well.

I define the boundaries and plan how the replacement will work with the rest of the system. I cover interfaces, existing data and rollout.

Start with a modernization assessment

An assessment is useful when you know what the application needs to do but are unsure what has to change underneath.

Tell me what you need to find out. I’ll help you narrow the review to the relevant part of the system. Depending on the problem, I review the architecture, dependencies, build, tests, storage, and deployment.

What you’ll have in writing

  • how the application works today
  • what is blocking the changes you need
  • which changes depend on others
  • what to tackle first and why
  • an estimate for the first phase

You’ll have a recommendation for the first phase, an estimate, and the reasoning behind the proposed order of work. You decide which changes to commission.

If your team already has an agreed modernization plan, I can go straight to implementation.

Discuss your modernization project

Fixed-fee review

Java build and release review

Are your developers waiting for builds to finish or working through the same manual checklist for every release? I trace one Java application from commit to deployment to find out where the time goes.

Get a fixed-price quote

What the review covers

On our first call, we agree on one application and one release pipeline, which configuration files and logs I can review, and who can walk me through a release. I send you a written quote with the full fee before you commit.

What your team gets

You get a written account of what slows releases down, which steps are worth automating and what I’d tackle first. I walk your developers through the recommendations so they can make the changes themselves. You can also hire me separately to implement them.

How we simplified the Maven build

How I modernize your application

  1. 1. Pick a change with a clear outcome

    I help you select one part of the application and define what people should be able to do once it’s changed.

    A first phase might cover a platform upgrade, restructuring one module or preparing a new integration.

    We agree on how you’ll tell whether that first phase has succeeded.

  2. 2. Establish the current behavior

    I examine the affected processes, data and interfaces.

    I use existing tests and add coverage where the planned change requires it. People who know the business help me understand rules and exceptions.

    Those tests make it easier to spot unintended changes.

  3. 3. Develop the agreed changes

    I implement the changes to code, dependencies, configuration and, if necessary, data structures.

    You see the work regularly. We discuss new findings and their impact on scope as they arise.

  4. 4. Prepare for rollout and operation

    I test the changes and plan the rollout with the people who run the system.

    I automate builds, tests and deployments in your CI/CD pipeline. We agree on how to check a release and how to roll it back if it goes wrong.

A Java developer who can lead the migration

I’m Marcus Biel. I’ve been building Java applications since 2001. I work on the architecture and make changes in the codebase.

At a German energy company I helped the team untangle a Java 8 application from Eclipse RCP for a staged move to Java 25 and Quarkus. Read about the energy project.

I can join your developers or bring in specialists for a particular part of the migration.

I work remotely with clients across Germany.

More about working with me
Marcus Biel
Marcus BielSoftware developer and architect

Frequently asked questions about Java modernization

Will we need a complete rewrite?

This depends on the goals and the state of the application.

I assess what an upgrade, focused restructuring or component replacement would accomplish. I also evaluate a rewrite against the same goals and constraints.

I factor in the rules your users rely on, the data you need to keep, and the cost of rebuilding integrations.

Can people keep using the application during modernization?

I plan changes around how people use the application today.

Some changes can be prepared independently and others need a coordinated cutover. Shared interfaces and changes to existing data are especially important here.

Before implementation, we agree on test environments, checks and any migration windows.

What documents do you need to get started?

Start with what the application does, what you need to change, and the technologies it uses.

For a technical assessment I need the relevant code and information about builds, tests, data storage and deployments. Documentation and people who know the system help me interpret what I find.

We agree what access is needed for the part of the system under review.

How much does Java modernization cost?

Cost depends on the parts of the system I need to change and what else depends on them.

Test coverage, documentation, and rollout requirements also affect the estimate.

Once the scope is clear, I can quote for the work or agree on a budget for a first phase. Larger projects can be divided into successive phases.

Can you work with our team on the migration?

Yes. I can join your developers to plan the architecture, upgrade the platform, or implement a specific part of the migration.

Your team and I agree on responsibilities, and I fit the work into your existing process.

Work with a freelance Java developer and architect

What changes does your Java application need?

Briefly describe your system, the current obstacles and the outcome you want to achieve.

We’ll identify what’s holding the application back and choose a first change your team can put into production.

Other project inquiries: Architecture or code review · Bring me onto your Java team.

Prefer to talk first? Call +49 171 1151013 or message me on LinkedIn.

Discuss Java modernization