Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Engineering

Application modernisation: evolving an ageing estate without service disruption

Not every old application deserves a rewrite, and none can withstand a cutover without evidence. Our consultants help your teams choose the takeover strategy application by application, then migrate in reversible stages.

Our principles

  • A strategy chosen application by application
  • Migration in stages, each one reversible
  • Non-regression demonstrated, not assumed
In brief

Application modernisation refers to the operations that restore an ageing application's ability to evolve: encapsulation, rehosting, replatforming, refactoring, rewriting or replacement. Management Square helps your teams map the estate, choose the right strategy for each application and migrate in stages, with evidence of non-regression at each cutover.

Scope

How we contribute

  1. Mapping the application estate

    An inventory of the applications in scope, their flows and their dependencies, cross-referenced with their business criticality, their technical condition and the knowledge still available.

  2. Choice of strategy per application

    For each application: retain, encapsulate, rehost, replatform, refactor, rewrite, replace or retire. The choice is justified by explicit, comparable criteria.

  3. Modernisation trajectory

    Sequencing of workstreams according to dependencies, risks and imposed deadlines (end of support, end of contract), with stages that each bring a benefit.

  4. Non-regression safety net

    Characterisation tests, reference datasets and a mechanism for comparing the old and new systems, built before the code is modified.

  5. Progressive migration

    Cutover by functional scope behind a routing facade, controlled coexistence of data and a rollback procedure for each stage.

  6. Decommissioning

    Actual shutdown of the old system: data archiving, stopping flows, terminating licences and contracts that no longer serve any purpose.

Page contents

Why so many large rewrites fail

Application modernisation is often decided too late and carried out too broadly. Too late, because an old application works: as long as it provides the service, replacing it gives way to more visible projects. Too broadly, because on the day the decision is taken, the accumulation of problems pushes towards redoing everything at once.

The pattern that follows is well known. A rewrite programme is launched with the aim of replacing the old system in a single cutover. Meanwhile, the old system keeps evolving, because the business does not stop: the target moves. The business rules turn out to be more numerous than expected, buried in code that no one masters any more. The cutover date slips, the cost of double maintenance sets in, and the budget ends up being called into question before a single user has seen the new system.

The other failure, more discreet, is purely technical modernisation. The application changes platform, nothing changes for the business, and the next workstream can no longer find funding. A modernisation must deliver a visible benefit at each stage: an awaited change that has become possible, an operational risk removed, a cost eliminated.

Mapping the estate before deciding

No strategy can be chosen without knowing what you have. The mapping does not aim to cover the entire information system: it concerns the scope to be addressed and the information that weighs in the decision.

  • Business value. Processes served, number and type of users, consequences of an outage.
  • Technical condition. Out-of-support components, code quality, presence of tests, ease of deployment. This is the concrete measure of the technical debt accumulated.
  • Couplings. Inbound and outbound flows, shared databases, chained batch processes. They determine what can be moved on its own.
  • Available knowledge. Documentation up to date or not, people still able to explain the rules, dependency on a service provider.
  • Imposed deadlines. End of support for a component, end of a hosting or maintenance contract, regulatory obligation.

This information comes from the application inventory, code analysis and interviews with those who use and maintain the applications. Cross-referencing business value with technical condition gives a first breakdown of the portfolio, to be discussed with the business departments.

Six application modernisation strategies

Vocabulary varies from one source to another, but six strategies cover most situations. They are ranked by depth of intervention, and therefore by increasing effort and risk.

Strategy Principle When it suits Limitation
Encapsulate Expose functions and data through APIs, without modifying the core Reliable, stable core, but closed to new uses The internal debt remains intact
Rehost Move the application as it is to another infrastructure Hosting deadline, hardware at end of life No gain in the code or in the ability to evolve
Replatform Replace the runtime platform (operating system, database, application server) with few code adaptations Platform component at end of support Full tests to rerun for zero functional benefit
Refactor Restructure the code without changing its behaviour Valuable application, set to evolve a great deal Requires a prior safety net of tests
Rewrite Rebuild the application on new foundations Technology with no future, unrecoverable code Highest risk, business rules to be rediscovered
Replace Abandon the application for a market solution Function that has become standard Adapting processes, data migration

To these six strategies are added two decisions that are too often forgotten: retaining the application as it is, when it is stable and little used, and retiring it, when its use no longer justifies its cost. The strategies can be combined: the same application can first be encapsulated, then rewritten piece by piece. When the chosen strategy consists of rehosting or replatforming the application, the work joins that of cloud migration, which we cover on a dedicated page.

Our approach: migrating in reversible stages

When the application has to be transformed in depth, we recommend setting aside the single cutover in favour of progressive replacement. A proven pattern, known as the strangler fig, consists of placing a facade in front of the old system. This facade routes each request to the old or the new code according to the functional scope concerned. Scopes are cut over one by one, and the old system shrinks until it can be switched off.

Three points call for particular attention.

The boundary between the two worlds. The new code must not inherit the data model and workarounds of the old one. A translation layer, often called an anti-corruption layer, isolates the two models and disappears with the old system.

Coexistence of data. As long as two systems live side by side, you must state, for each data item and at each stage, which one is authoritative and how the other is kept up to date. This is one of the most underestimated subjects in progressive migrations.

Rollback. Each cutover is prepared with its rollback procedure, tested before it is needed. A stage from which there is no way back is a single cutover in disguise.

Such work extends across several scopes and involves several teams. It is managed as a programme, with its dependencies and trade-offs, according to the principles we describe for programme management.

Proving non-regression

Non-regression is not declared; it is demonstrated. On an old system, the reference specification no longer exists: the only reliable description of the expected behaviour is the current behaviour.

We therefore start with characterisation tests, which record what the system actually does on a representative set of cases, known anomalies included. Next comes parallel running: the old and new systems receive the same inputs, and their outputs are compared automatically. Each discrepancy calls for a decision. Either the new system is at fault, and it is corrected. Or the old one was, and the business decides whether this behaviour should be reproduced or corrected.

The comparisons also cover what functional tests do not see: response times, batch processing durations, volumes. Datasets drawn from production are anonymised or pseudonymised before use when they contain personal data. The overall organisation of these checks falls under software quality and testing.

Five pitfalls of modernisation work

  • Applying a single strategy to the whole estate. ‘Everything to the cloud’ or ‘rewrite everything’ are slogans, not strategies.
  • Aiming for an identical reproduction. Part of the functions of an old system are no longer used. Identifying them before migrating reduces scope and risk.
  • Freezing business changes. A prolonged freeze is rarely held. It is better to plan how urgent changes will be carried during the transition.
  • Forgetting to switch off the old system. As long as the old system runs, its costs keep running and the expected benefit is not achieved. Decommissioning is planned and funded like the other stages.
  • Letting knowledge walk away. The people who know the existing system are involved in the work from its launch, not consulted on the eve of the cutover.

The signs of a modernisation that is progressing

Progress is read in what has actually been cut over, not in the effort consumed. The indicators we track with you concern verifiable facts: the functional scopes served by the new system, the applications and components actually switched off, the number of out-of-support components still in production, the residual discrepancies found during parallel runs.

To these are added indicators of effect. The time to release a change to production on a modernised scope, compared with what it was before. Incidents attributable to cutovers. The number of people able to work on the application, which measures the move away from dependency on a few experts. None of these measures is the subject of a promise made in advance: they serve to decide, stage after stage, whether the trajectory is still the right one.

Typical work

What our consultants contribute to

Estate map and diagnostic

A record per application: criticality, technical condition, dependencies, known cost of ownership and level of available knowledge.

Strategy matrix

The strategy chosen for each application, the criteria applied and the options ruled out, in a format readable by an executive committee.

Modernisation roadmap

Stages, dependencies, major risks and decision points, without committing the organisation beyond what it can absorb.

Non-regression file

Reference sets, results of the comparisons, discrepancies found and the decision taken on each.

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is application modernisation?

Application modernisation brings together the operations that allow an old application to keep serving the business at an acceptable cost and risk. It ranges from exposing its functions through APIs to rewriting it completely or replacing it with a market solution. It does not aim at technical novelty: it aims to regain the ability to evolve the system.

Should an old application be rewritten entirely?

Rarely in one go. A complete rewrite followed by a single cutover is the riskiest strategy: the business rules buried in the code have to be rediscovered, and the old system keeps evolving during the work. When a rewrite is unavoidable, we recommend carrying it out in successive functional scopes, with the old and new systems coexisting for the duration of the transition.

What is the difference between application modernisation and cloud migration?

Cloud migration changes where and how an application is hosted. Application modernisation concerns the application itself: its code, its architecture, its data. The two overlap, since rehosting or replatforming an application are modernisation strategies, but an application moved as it is to the cloud keeps all of its debt.

How do you guarantee non-regression during a migration?

By building the evidence before modifying anything. Characterisation tests record the actual behaviour of the existing system, then the old and new systems are run on the same inputs and their results compared. Each discrepancy is analysed and is the subject of an explicit decision by the business.

How do you prioritise the applications to modernise?

By cross-referencing two readings: the value of the application to the business and its technical condition. A critical application in poor condition goes to the top; a little-used application in poor condition is a candidate for retirement. Imposed deadlines, such as the end of support for a component or of a hosting contract, then set the timetable.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.