Legacy application modernization — US
A legacy application often contains years of business rules that nobody has fully documented. Replacing its technology without understanding those rules can remove behavior the organization still relies on.
FI Digital approaches modernization as a sequence of controlled changes.
The scope identifies what must be retained, what can be simplified and how users will move to the new behavior without losing essential operational continuity.
What the engagement covers
Map users, critical functions, interfaces, data and known limitations.
Compare targeted refactoring, new interfaces, component replacement and a broader rebuild.
Choose a bounded change and test it against representative business scenarios.
Plan data reconciliation, user acceptance, rollback and the criteria for removing old components.
FI DIGITAL / WORKFLOW
Legacy application modernisation
- Behaviour and dependency review
- Modernisation options
- Review and authorise
- Transition and retirement
- Resolve with the owner
A practical example
An illustrative order application has undocumented exception rules used by experienced staff. The first phase captures and tests those rules before replacing the interface or changing how orders are stored.
Questions that shape the scope
Use these questions to identify the first decision and the information needed to make it.
- Which behavior must remain?
- What is undocumented?
- How will data reconcile?
- When can the old component be retired?
Scope the US workflow and its dependencies
Identify the US business process, contracting entity and system owners before using a global template. Multi-state or multi-entity requirements, supported provider accounts and working-hour coverage should be explicit where they affect delivery. The project should have a named acceptance owner and an agreed support arrangement; no local office or round-the-clock coverage is implied.
From assessment to an accepted result
Agree the user, workflow, expected outcome and acceptance owner. Identify the important unknowns early.
Set out records, interfaces, permissions and dependencies. Make failure recovery part of the design.
Review usable work against representative scenarios. Keep decisions and scope changes visible.
Confirm acceptance, rollback, account ownership, documentation and the support arrangement.
Control cost around the work that matters
AI-assisted development, reusable components and supported connectors can reduce parts of the build effort. They do not remove the need to agree requirements, resolve conflicts between systems, review permissions or accept the business result. Keep the first release bounded and compare proposals against the same interfaces, tests, handover and support responsibilities. Ask which recurring provider charges and maintenance tasks remain after launch. Senior coordination is most useful where it resolves a concrete dependency or decision; it should be visible in the scope. The aim is a maintainable working outcome at an understood total cost, not additional complexity for its own sake.
What your team should receive at handover
The handover should cover the working application or integration, relevant source and configuration access, deployment instructions and the accepted test evidence. Document the important dependencies and the actions that require an authorized owner. A useful release record explains what is included, what remains outside scope and how the team can recover from an ordinary failure. These materials support maintainability; they do not replace a separately agreed support arrangement.
Scope and responsibilities
The scope, acceptance criteria, third-party dependencies and operating responsibilities are agreed for the engagement. No partner tier, certification, guaranteed saving or fixed delivery period is implied.
Frequently asked questions
Do we need to rebuild the whole application?
Not always. A targeted integration, refactor or replacement of one component may address the most valuable problem with less disruption. The assessment should compare those options and their operating implications. A full rebuild needs a clear reason and a plan for preserving the business behavior the organization still requires.
What if there is little technical documentation?
Begin with the application’s behavior, users, source access and observable dependencies. Capture representative workflows and difficult cases with experienced staff. The discovery effort may be larger, and uncertainty should remain visible in the plan. Do not treat an incomplete inventory as evidence that an undocumented function is unnecessary.
Can the project start with a smaller first release?
Yes, if the first release covers a useful end-to-end workflow rather than disconnected screens. Agree the user, outcome, acceptance checks and operational owner. Keep later features visible without placing them all in the initial scope. The first release should test the important assumptions and leave a maintainable foundation for the next decision.
How are cost and delivery time estimated?
The estimate follows the agreed workflow, interfaces, data, permissions and operating requirements. Discovery should expose uncertain dependencies before they become hidden commitments. Break the work into reviewable milestones and state assumptions, exclusions and third-party costs. A fixed number of weeks or a low starting price is not a reliable substitute for a defined delivery scope.
Can you integrate with our existing systems?
Integration depends on the systems’ available interfaces, access rights, limits and commercial terms. Review the actual records and actions required before choosing a connector or custom interface. Define identifiers, retry behaviour, duplicate prevention and reconciliation. The proposal should distinguish supported actions from capabilities that still require discovery or permission from another system owner.
Who owns the software and accounts?
Ownership, licensing and access should be explicit in the agreement. Distinguish custom code from existing product components, third-party services and open-source dependencies. Agree where repositories, cloud accounts, credentials and documentation will be controlled, and what is handed over. Do not assume that commissioning a project automatically transfers every underlying software right or provider account.
How do you test before launch?
Test the business workflow, user permissions, ordinary failures and recovery, using representative scenarios agreed with the people who will operate the result. Include data quality and integration behaviour where relevant. Record acceptance and unresolved issues before release, with a rollback or fallback appropriate to the change. A demonstration of the happy path is only one part of readiness.
Is ongoing maintenance included?
The proposal should distinguish delivery, warranty or defect correction, and ongoing operational support. Dependencies, usage and business requirements can change after launch, so assign ownership for updates and monitoring. Support hours, response targets and service levels require a specific agreement. They should not be assumed from a general description of development or platform operations services.