Views: 13
Summary – Ongoing pressure from legacy software slows innovation, increases operational costs, and heightens integration and security risks with every change. Between undocumented business complexity, outdated dependencies, and refactoring cost overruns, the decision to reprogram must be based on a precise comparison: gains (productivity, security, time-to-market) versus budget (300–800 kCHF + risk margin).
Solution: ROI-based trade-off → modular migration to microservices/APIs → business-led governance and data stewardship to deliver value quickly without service disruption.
In many Swiss small and medium-sized businesses, software solutions developed one or two decades ago still drive daily operations. They do their job, seem adequate, and replacing them appears risky and costly. Yet these legacy systems can hinder agility, inflate expenses, and stifle innovation. The question isn’t whether the technology is old, but whether it still serves your strategic goals. Rewriting merely to replicate existing features without added value is a mistake; rewriting to create a competitive edge is a strategic choice.
The Shock of Redesign Costs
Rewriting a historical software demands a significant investment. Reproducing years of business evolution is never simple.
Cumulative Business Complexity
Every feature in your legacy application results from a chain of business rules refined over the years. Processes added ad hoc to meet a client’s need, regulatory adaptations, or tweaks for specific suppliers have woven a complex—and often poorly documented—fabric.
When you decide to reprogram, you must dissect this logic to understand every nuance. This analysis phase represents a large portion of the budget, as each edge case can trigger questions and back-and-forths with the business experts.
Tacit knowledge stored in the minds of long-time users is hard to transfer. Without comprehensive documentation, the technical translation of each rule is open to interpretation, increasing the risk of functional discrepancies.
Accumulated Dependencies
An older software often incorporates outdated third-party components, connectors to external systems, or even protocols specific to a former vendor. These dependencies are sometimes no longer maintained by the community and are difficult to update.
Every integration point must be revalidated: internal or external APIs, file exchanges, EDI streams… The reimplementation effort covers not only the business code but also the overhaul of all integration points.
Migrating these dependencies may require workarounds or developing wrappers, which expands the scope and directly impacts the project’s timeline and cost.
Impact on the Initial Budget
Cost estimates for a purely technical rewrite often range between 300,000 and 800,000 CHF for a mid-sized SME. This range reflects uncertainties around real complexity and unforeseen issues likely to surface once the project begins.
The sticker shock is even greater when leaders compare this figure to the current maintenance budget, without accounting for the support, bug fixes, and security efforts already included each year.
A redesign project must include a contingency margin to manage risks and additional iterations. Without this buffer, the initial budget is quickly exceeded, jeopardizing the project’s success.
Illustration from a Swiss Case Study
A mid-sized industrial manufacturer commissioned a rewrite of its custom ERP at 450,000 CHF. During the analysis phase, the team uncovered 200 undocumented business rules, resulting in a 20% budget overrun and a six-week delay. This example shows how historical complexity can be underestimated and heavily burden the initial budget.
The Hidden Cost of the Status Quo
Maintaining an old software may seem cheaper in the short term. Hidden costs weigh on innovation, security, and performance.
Barrier to Innovation
When every new feature becomes a project, teams give up on innovation. The need to test existing code, fix old bugs, or work around architectural limitations drastically slows development cycles.
Priority projects struggle to start because even minor changes require preliminary analysis and stabilization. Your time-to-market lengthens while more agile competitors capture market share.
This hinderance translates into missed opportunities, especially for digital services your clients might expect but deem too risky or costly to implement.
Integration Limitations
A legacy software often lacks modern APIs or standardized connectors to cloud and SaaS solutions. Data exchanges happen via flat files or proprietary streams, limiting automation and the creation of omnichannel customer journeys.
For each new partner or tool—CRM, BI, e-commerce platform—you must develop a bespoke connector. These ad hoc developments increase technical debt and generate recurring maintenance costs.
Over time, the absence of standards opens the door to synchronization errors, processing delays, or service interruptions, directly impacting user experience quality.
Security and Compliance Risks
Old architectures can contain unpatched vulnerabilities, outdated software stacks, and obsolete authentication mechanisms. Security audits often reveal critical flaws that lack available patches for legacy versions.
From a regulatory standpoint, data traceability may be insufficient: change history, role and access management, and encryption of sensitive data may no longer meet current compliance requirements (GDPR, FINMA, ISO 27001).
Assuming that “if it works, it’s safe” is a dangerous illusion. An incident can incur remediation costs far exceeding those of a targeted rewrite.
Example from a Swiss SMB
A logistics service provider relied on an internal application without APIs. Each month, the IT team spent two weeks manually consolidating stock reports before migrating them to BI. The result: repeated delays in strategic reporting and an inability to react quickly to demand shifts.
Edana: strategic digital partner in Switzerland
We support companies and organizations in their digital transformation
Reprogram or Not: A Strategic Trade-Off
Rewriting to achieve the same functionality is often unjustified. Rewriting to deliver real gains is strategic.
When to Say NO
If your legacy software still performs its tasks efficiently without increasing maintenance costs or hindering growth, a purely technical rewrite adds no value. Investing in slow “copy-paste” rewrites amounts to spending hundreds of thousands of francs for a disguised status quo.
In this case, it’s better to allocate resources to incremental improvement projects, optimizing processes around the existing system rather than rewriting the application entirely.
A trade-off might involve reducing technical debt through targeted fixes, strengthening test coverage, or redesigning workflows without touching the application core.
When to Say YES
A rewrite becomes strategic when you aim for measurable gains: increased productivity, lower operational costs, integration of new channels, enhanced customer experience, or stronger security.
The key question: what return on investment do you expect? For example, reducing order processing time by 30% may justify a rewrite budget if it translates into growth or significantly lower staffing costs.
Your decision should align with your business roadmap, supported by clear performance indicators and value-driven management.
Calculating the Expected ROI
Start by quantifying concrete gains: person-hours saved, error reduction, accelerated time-to-market, infrastructure or licensing cost savings. Compare these benefits against development and migration expenses.
A structured business case also factors in risks: extended timelines, technical surprises, team training, and transition costs. A 10% budget contingency ensures forecasting reliability.
This ROI calculation must be approved by finance and monitored throughout the project, with reviews at each strategic milestone.
Illustration from a Swiss Distribution Group
A distribution group compared three scenarios: maintaining the status quo, partial module rewrites, and a complete overhaul. The intermediate scenario—focusing on order management modules—delivered a 150% ROI in two years, while the full rewrite achieved only 80% ROI over the same period.
Progressive Migration and Decision Criteria
Modular migration limits risks. Clear criteria guide the prioritization of workstreams.
Prioritizing by ROI and Business Impact
Identify modules with the highest gain potential: crucial automations, revenue-generating features, critical integration points with partners or BI. Assess migration costs and operational benefits for each.
Assign a score to each module based on two axes: revenue impact and risk exposure (security, compliance). This matrix guides the delivery sequence.
By concentrating investment on high-return areas, you deliver tangible benefits quickly and progressively fund subsequent phases.
Implementing a Hybrid Architecture
Build a new technology foundation alongside the existing system. Develop microservices for critical features and expose them via REST or GraphQL APIs.
This hybrid architecture allows data sharing between old and new systems and incremental progress without service disruption. You minimize the “big bang” approach and ensure operational continuity.
The approach also favors open-source technologies and avoids vendor lock-in, retaining flexibility to choose the best stack for each module.
Managing Risks and Securing the Transition
Define clear milestones with success criteria for each step. Incorporate automated tests and code reviews to prevent surprises.
Plan rollback mechanisms and pre-production environments that mirror production. Load testing and version upgrade simulations ensure performance remains under control.
This rigorous governance minimizes interruptions, reassures stakeholders, and secures timelines and budgets.
Establishing Data Governance and ROI Tracking
Ensure each migrated module maintains consistent data management: formats, access policies, traceability, and compliance. Data governance becomes a critical success factor.
Regularly measure predefined performance metrics: processing times, support costs, service quality, and user satisfaction. These indicators inform decisions for subsequent phases.
A cross-functional project leadership—uniting IT, business owners, and development teams—ensures continuous alignment with corporate strategy.
Turn Your Legacy into a Growth Lever
Every rewrite decision hinges on your strategic objectives and expected ROI. Keeping an old software may seem cheaper, but the status quo carries hidden costs that drag on innovation, security, and agility. A progressive, modular, value-driven approach reduces risks and funds the migration steps.
Our experts support IT leadership and corporate governance in decision-making, hybrid architecture design, and robust data governance. Let’s discuss your challenges and transform your legacy system into a competitive advantage.
