ZTABS delivers legacy app modernization in Helsinki — migrating Finnish enterprise, government, and banking systems from legacy platforms to modern cloud-native architecture while preserving Finnish compliance, business logic, and institutional knowledge.
Legacy app modernization in Helsinki addresses a growing urgency across Finnish organisations — critical business systems built 10-20 years ago on technologies that are now: unsupported (vendor end-of-life), unmaintainable (the developers who built them have retired or moved on), and unable to integrate with modern digital services. Finland's legacy challenge is: not a technology curiosity but a business risk. Government: Finnish government agencies running: systems built during the early 2000s e-government wave — Java EE applications on: WebLogic or WebSphere, .NET Framework applications, and: custom PHP systems — each encoding: Finnish regulatory requirements, administrative procedures, and: decades of policy changes in: code that: current development teams struggle to understand. Healthcare: wellbeing services counties inheriting: patient management systems from municipalities — some dating to the 1990s — running on: ageing databases and: application servers that: the vendor no longer supports. The 2023 wellbeing services county reform creating: urgency to modernise as: previously independent municipal systems must be: consolidated into county-level platforms. Banking: Finnish banks running: core systems and: customer-facing applications built on: technologies that are: reaching end of life — Java 8, older .NET versions, and: monolithic architectures that: cannot support the API-driven, mobile-first services that customers expect. Insurance: Finnish insurance companies (OP's Pohjola, LähiTapiola, Fennia, If) operating: policy management and claims systems built: decades ago — systems that: encode complex Finnish insurance regulations but: cannot be easily extended for digital claims processing or AI-powered underwriting. Industrial: Finnish manufacturing companies running: production management and ERP customisations on: legacy platforms — critical operational systems that: work reliably but: cannot integrate with: modern IoT, AI, or cloud services. The modernisation challenge in Finland is compounded by: institutional knowledge embedded in code (Finnish regulatory logic — tax calculations, benefit eligibility rules, pension formulas — encoded in: legacy code with: minimal documentation. Modernising these systems means: extracting this encoded knowledge, understanding it, and: re-implementing it correctly in: modern technology — getting it wrong means: incorrect tax calculations, incorrect benefit payments, or: non-compliant financial processing), risk aversion in regulated industries (Finnish government, banking, and healthcare organisations: unable to tolerate: system downtime or data loss during modernisation. The modernisation approach: must guarantee: continuous service delivery, data integrity, and: regulatory compliance throughout the transition — which rules out: "big bang" replacements in favour of: incremental, risk-managed approaches), and Finnish talent market constraints (Helsinki's developer talent market: competitive. Legacy technology skills (COBOL, older Java, legacy .NET): scarce among younger developers. Modern technology skills: in demand across: every Finnish employer. Modernisation projects needing: both legacy expertise (to understand: what the current system does) and modern expertise (to build: the replacement) — a skill combination that is: hard to assemble).
Helsinki's legacy modernisation demand comes from government, healthcare, banking, insurance, and industrial sectors. Government legacy modernisation addresses ageing public sector systems: central government systems (Finnish central government agencies — KELA, Vero, DVV, Migri — operating: systems built during: Finland's progressive e-government push of the 2000s. These systems: transformed Finnish public services at the time but are now: 15-20 years old, built on: Java EE application servers (WebLogic, WebSphere, JBoss), Oracle or PostgreSQL databases, and: custom frameworks that: predated modern web development. The systems encode: Finnish regulatory logic that: has been amended dozens of times — each amendment: implemented as code changes layered over previous implementations, creating: complex codebases where: understanding why a specific calculation works the way it does requires: archaeological excavation through: years of change history), municipal system consolidation (the 2023 wellbeing services county reform transferring: healthcare and social service responsibility from 309 municipalities to 21 counties. Each municipality: had its own systems — some shared platforms (Lifecare, Pegasos), some custom. The counties now: needing to consolidate: multiple systems into: unified county-level platforms — a massive legacy modernisation challenge that: defines Finnish public sector IT for the next decade), and AuroraAI integration (Finland's AuroraAI programme requiring: legacy government systems to expose data and services through: modern APIs — enabling AI-powered citizen services. Legacy systems: not designed for API access — modernisation required to: either retrofit APIs onto legacy systems or: replace legacy systems with: API-native modern platforms)). Healthcare legacy modernisation: patient information system migration (Finnish healthcare: transitioning from: legacy patient information systems (some: 20+ years old) to: modern platforms that: integrate with Kanta (national health data) and: support modern clinical workflows. The migration: complicated by: decades of patient data in: legacy formats, custom clinical workflows encoded in: legacy system configurations, and: integration with: hundreds of medical devices, laboratory systems, and: pharmacy systems that: communicate through: legacy interfaces), and clinical decision support modernisation (older clinical systems providing: basic decision support (drug interaction checking, allergy alerts) through: legacy rule engines. Modern clinical AI requiring: integration with: these systems or: their replacement with: platforms that support: modern clinical AI while: maintaining: the validated clinical rules that: patient safety depends on)). Banking and insurance legacy modernisation: core banking modernisation (Finnish banks considering: Temenos, Mambu, or Thought Machine as: replacements for: legacy core banking platforms — but: the migration from: a legacy core to a modern core being: one of the most complex technology programmes in: any industry. Finnish specifics: Finnish payment infrastructure (SEPA, NAPS-equivalent domestic clearing), Finnish regulatory reporting, and: Finnish product specifics (ASP savings accounts, PS savings, and: Finnish pension-linked products)), and insurance policy system replacement (Finnish insurance companies: replacing: legacy policy administration systems with: modern platforms. The challenge: Finnish insurance products encoding: decades of Finnish insurance regulation, Finnish pricing models (based on Finnish actuarial data), and: Finnish claim handling procedures. Migration: requiring: careful extraction and: re-implementation of: this Finnish-specific business logic).
Our Helsinki legacy modernisation methodology manages risk while delivering measurable progress toward modern architecture. Assessment and strategy determines what to modernise and how: legacy system assessment (comprehensive analysis of the legacy system: technology inventory (languages, frameworks, databases, infrastructure), dependency mapping (what other systems depend on this system? what does this system depend on?), business logic extraction (what Finnish-specific rules, calculations, and workflows are encoded in the code?), data assessment (data volume, data quality, data relationships, and: Finnish-specific data formats), and: risk assessment (what happens if this system fails? what is the cost of downtime? what regulatory exposure exists?)). Modernisation strategy selection (for each legacy system: selecting the appropriate strategy from: rehost (lift-and-shift to modern infrastructure — lowest risk, lowest benefit — appropriate for: systems that work well but: run on unsupported infrastructure), replatform (move to modern platform with minimal code changes — moderate risk — e.g., migrating from: WebLogic to: containerised deployment), refactor (restructure code for modern architecture — extracting services, implementing APIs, improving maintainability — moderate-to-high effort but: preserving: existing tested business logic), and: replace (build new system — highest effort and risk but: appropriate when: the legacy system is: too brittle to refactor or: the business requirements have changed so significantly that: the legacy system's architecture is fundamentally misaligned)), and phased roadmap (modernisation spread over: multiple phases — each delivering: measurable value while: managing risk. Phase priorities determined by: business urgency (which capabilities are most needed?), risk (which legacy components are most likely to fail?), and: dependency (which components must be modernised first to enable: subsequent phases?)). Incremental modernisation executes safely: strangler fig pattern (the primary modernisation pattern for: Finnish enterprise systems — new functionality built in: modern technology alongside the legacy system. New features: routed to the modern system, existing features: gradually migrated from legacy to modern. The legacy system: "strangled" as: more functionality moves to the modern system — eventually: the legacy system handles: nothing and can be: decommissioned. The pattern: ensuring continuous service delivery — the legacy system remains: operational throughout, and: if any modern component fails: traffic routes back to: the legacy system), API facade (exposing: legacy system functionality through: modern REST APIs — enabling: modern frontends, mobile apps, and: integration with other modern systems, while: the legacy backend continues to: operate. The API facade: often the first modernisation step — providing: immediate integration capability without: changing the legacy system's internals), and data migration (the most sensitive aspect of modernisation — migrating: decades of Finnish business data from: legacy database schemas to: modern data models. Our approach: parallel data synchronisation (data written to both: legacy and modern databases simultaneously — ensuring: both systems have: current data throughout the transition), validation (automated comparison of: legacy and modern data — every record verified), and: rollback capability (the ability to: revert to: the legacy database if: any data issue is discovered))). Finnish compliance preservation ensures regulatory requirements survive modernisation: business logic extraction and testing (before modernisation: extracting and documenting: all Finnish-specific business logic — tax calculations, benefit rules, regulatory formulas, compliance checks. Creating: automated tests that: verify these calculations produce: correct results. The tests: run against both: legacy system (confirming: the tests capture current behaviour) and: modern system (confirming: the modern implementation produces: identical results)), compliance continuity (during modernisation: maintaining: all regulatory compliance — Finnish financial reporting, Finnish data protection, Finnish sector-specific regulations. The modernised system: meeting the same: compliance requirements as the legacy system — verified through: regression testing against: known correct outputs), and audit trail preservation (Finnish regulations requiring: audit trails — financial transactions, administrative decisions, data changes. Modernisation preserving: historical audit data (migrated to: modern storage) and: maintaining: audit trail continuity (no gap between: legacy system audit trail and: modern system audit trail)).
Government / Public Sector
A Finnish central government agency (processing: 280,000 applications annually for: a specific category of government permits and registrations — the exact agency anonymised for: confidentiality) operated a core processing system built in 2007 — a Java EE application on: Oracle WebLogic, with: an Oracle 11g database, custom JSP frontend, and: integration with: 8 other government systems via: SOAP web services and: file-based data exchanges. The system encoded: 19 years of Finnish regulatory amendments — each amendment: implemented as code changes, often by: different development teams (3 different vendors had: maintained the system over its lifetime — each with: different coding standards and: different architectural approaches). Current state: technology risk (Oracle WebLogic 12c approaching: end of extended support. Oracle 11g: already out of: premier support. Java 8: the system's runtime — security patches: available but: migration to newer Java versions: blocked by dependencies on: WebLogic-specific APIs and: legacy libraries. The agency's IT team: unable to apply: security patches without: extensive regression testing because: the system's behaviour was: unpredictable when: any component was updated), developer availability (the system's codebase: 450,000 lines of Java code, 120,000 lines of JSP/JavaScript, and: 2,800 stored procedures in Oracle. Documentation: minimal (the last comprehensive documentation: written in 2009 — the system had changed: substantially since then). The 2 remaining developers who understood the system: both over 55 and: planning retirement within 3 years. The agency: unable to hire: replacements because: younger developers: refused to work with: 2007-era Java EE and: Oracle stored procedures), citizen experience (the system's frontend: a 2007 JSP application — functional but: not mobile-responsive, not accessible (WCAG non-compliant), and: not integrated with: Suomi.fi authentication (citizens using: a separate, system-specific login). The citizen experience: significantly below: modern Finnish e-government standards set by: Suomi.fi), performance limitations (the system: processing well during normal periods but: struggling during: peak application periods (seasonal peaks: application volume increasing 3x during: specific regulatory deadlines). Peak processing: causing: 30-60 second page load times and: occasional timeouts — citizens: resubmitting applications, creating: duplicates that: required manual de-duplication), and integration brittleness (the 8 government system integrations: built using: SOAP web services and: overnight file transfers. When: an integrated system changed its interface (which: happened 2-3 times per year): the integration: broke, requiring: emergency patches. The agency: spending 40% of its development budget on: integration maintenance rather than: feature development).
We modernised the system over 24 weeks using a strangler fig approach — building the modern system alongside the legacy system, migrating functionality incrementally. Modern architecture design (weeks 1-4): planning the target state. Architecture: microservices on: Kubernetes (hosted on: CSC — Finland's IT Center for Science — providing: government-grade cloud hosting within Finnish jurisdiction). Services: application intake (receiving and validating applications), case processing (workflow engine for: application processing), decision engine (Finnish regulatory logic for: eligibility and decision rules), notification (citizen communication — email, SMS, and: Suomi.fi messages), integration hub (modern API-based integration with: other government systems), and: citizen portal (Next.js — responsive, accessible, Suomi.fi-authenticated). Database: PostgreSQL (replacing Oracle). Each service: independently deployable, independently scalable, and: independently maintainable — addressing: the monolithic architecture that: made the legacy system brittle. Business logic extraction (weeks 2-8): understanding what the legacy system actually does. Regulatory logic archaeology: working with the agency's legal and policy teams: mapping every regulatory rule encoded in the system — eligibility criteria, processing rules, fee calculations, deadline calculations, and: exception handling. The extraction: discovering: 847 distinct business rules — many: undocumented (implemented in code without: corresponding policy documentation). 23 rules: found to be incorrect (implementing: superseded regulatory versions) — the legacy system: producing wrong results for: certain edge cases that: hadn't been noticed because: the volume was low. Automated test creation: every extracted rule: converted into: an automated test case with: known inputs and expected outputs. The test suite: 3,400 test cases covering: the 847 business rules — the tests: runnable against both the legacy and modern systems to: verify identical behaviour. Citizen portal (weeks 4-12): modern frontend replacing the 2007 JSP interface. Suomi.fi authentication (citizens: authenticating with Finnish bank credentials or mobile ID — the same authentication used across: all Finnish government services — replacing: the legacy system-specific login). Responsive, accessible design (WCAG 2.1 AA compliant — mobile-responsive, keyboard-navigable, screen-reader-compatible. Finnish and Swedish languages supported natively). Smart forms (application forms: pre-populated with: data from DVV (population registry) and: other government systems — citizens not re-entering: information that the government already has — reducing: form completion time and: data entry errors). Real-time status (citizens: checking application status in real-time — "Your application was received on X, is currently being processed, estimated decision date: Y" — replacing: the legacy "your application is in process" with: no further detail). The citizen portal: deployed as the first strangler fig component — new applications: entering through the modern portal but: processing continuing in the legacy backend. Integration modernisation (weeks 6-16): replacing SOAP and file-based integrations with modern APIs. API gateway (a modern API gateway: providing standardised REST APIs for: all government system integrations. Each legacy SOAP integration: replaced with: a modern REST API — the API gateway handling: authentication, rate limiting, logging, and: error handling. The modernised integrations: more reliable (retry logic, circuit breakers), more visible (API monitoring and: alerting), and: easier to maintain (standard REST patterns rather than: custom SOAP implementations)). Decision engine migration (weeks 10-20): migrating the core business logic. Rule engine (the 847 business rules: migrated from Java code and Oracle stored procedures to: a modern rule engine — rules: expressed declaratively (readable by: policy staff, not just developers), testable independently, and: version-controlled (each regulatory amendment: a tracked change in the rule base)). Automated testing: every rule: tested against: the 3,400 test suite — any deviation from: legacy system behaviour: investigated (is it a modernisation bug, or: a legacy bug that should be fixed?)). Parallel processing (for 8 weeks: every application: processed by both legacy and modern systems in parallel — results compared. Any discrepancy: investigated and resolved before: traffic migrated to the modern system exclusively)). Data migration (weeks 14-22): moving from Oracle 11g to PostgreSQL. Schema modernisation (the legacy Oracle schema: denormalised, with: cryptic column names and: undocumented relationships. The modern PostgreSQL schema: normalised, clearly named, and: documented. The migration: mapping 340 legacy tables to: 180 modern tables — merging redundant tables, normalising denormalised data, and: establishing: proper foreign key relationships). Data validation (every migrated record: validated — counts, sums, checksums, and: spot-check comparisons — ensuring: no data lost or corrupted during: migration). Historical data (19 years of application data: migrated in full — maintaining: audit trail continuity and: enabling: historical analysis that: the agency hadn't been able to perform on the legacy system).
The modernisation completed in 24 weeks with zero downtime — citizens never experienced: service interruption. The legacy system: decommissioned 4 weeks after: the last functionality migrated (kept available as: read-only reference during: the transition). Technology risk: eliminated. The modernised system running on: current technology (Kubernetes, PostgreSQL, modern Java) with: standard security patching, no vendor end-of-life concerns, and: a codebase that: multiple developers can maintain. The agency: no longer dependent on: 2 near-retirement developers for: system continuity. Performance: peak-period response time: from 30-60 seconds to: under 2 seconds (15-30x improvement). The Kubernetes deployment: auto-scaling during: peak periods — handling 3x volume increases without: performance degradation. Citizen timeouts: eliminated. Citizen experience: Suomi.fi authentication: citizens using: the same login as: all other Finnish government services. Mobile-responsive: 34% of applications now submitted from: mobile devices (previously: 0% — the legacy JSP not usable on mobile). Application form completion time: reduced from: average 28 minutes to: 14 minutes (50% reduction) due to: pre-populated data from government registries and: improved form design. Accessibility: WCAG 2.1 AA achieved — the first time the system met: Finnish accessibility requirements. Regulatory accuracy: the 23 incorrect legacy rules: corrected during modernisation — the system now producing: correct results for all regulatory scenarios. The automated test suite: 3,400 tests running: on every deployment — preventing: regression. Integration reliability: integration incidents: from average 8 per quarter (legacy SOAP/file) to: 0.5 per quarter (modern API). Integration maintenance effort: reduced 70%. New integrations: deployable in: 1-2 weeks (vs: 3-4 months in the legacy architecture). Development velocity: new feature delivery: from 1 feature per quarter (legacy — limited by: code complexity and: testing difficulty) to: 4-6 features per quarter (modern — modular architecture, automated testing, and: CI/CD enabling: faster, safer releases). The agency: able to respond to: regulatory changes in: weeks rather than: months. Staff situation: the modernised codebase: maintainable by: standard developers (TypeScript, React, modern Java) — the agency: successfully hiring 3 junior developers (recent Aalto graduates) who: became productive within: 4 weeks (vs: 6-12 months learning the legacy codebase). Financial impact: eliminated Oracle licensing: €180,000 annually. Reduced infrastructure costs (cloud vs. legacy hardware): €120,000 annually. Development efficiency (4-6 features/quarter vs 1): estimated €400,000 in value. Integration maintenance reduction: €160,000 annually. Citizen time savings (50% faster forms × 280,000 applications): estimated societal value of €1.2 million. Total annual benefit: €2.06 million. Implementation cost: €165,000. Monthly operating cost: €4,800. First-year ROI: 11.5x.
Modernize one module at a time — reducing risk, delivering value early, and keeping the business running throughout.
We extract and document the business rules embedded in legacy code so nothing gets lost in the new system.
Migrate from legacy databases (Access, FoxPro, SQL Server) to modern PostgreSQL or cloud-managed databases.
Build modern REST or GraphQL APIs that let the new system talk to legacy components during the transition period.
Create comprehensive test suites that verify the new system behaves identically to the old one for every critical workflow.
Deploy the modernized application on AWS, Azure, or Vercel with CI/CD pipelines, monitoring, and auto-scaling.
Helsinki's legacy modernisation market includes large Finnish IT service providers, global consultancies, and specialist modernisation firms. CGI Finland: the largest IT service provider in Finland — extensive government and enterprise experience, legacy system knowledge. Large engagement capacity but: premium pricing. Gofore and Solita: Finnish digital consultancies with growing modernisation practices — understanding Finnish public sector and enterprise context. Accenture Finland and TietoEVRY: large-scale modernisation capability — resources and methodology, but: can be slow and expensive for mid-size projects. The challenge: most large providers recommending platform replacements (SAP, Salesforce, ServiceNow) rather than custom modernisation — platform replacements: sometimes appropriate but: often more expensive and disruptive than: targeted modernisation of existing systems. ZTABS provides: incremental modernisation (strangler fig, API facade) preserving business logic, Finnish compliance expertise, and: right-sized engagements (not requiring: 50-person teams for: focused modernisation projects).
Legacy modernisation in Helsinki ranges by system complexity and approach. Assessment and strategy (4-6 weeks): €20,000-45,000. API facade (exposing legacy via modern APIs, 6-10 weeks): €30,000-70,000. Incremental modernisation (strangler fig — multiple phases, 12-24 weeks per phase): €80,000-200,000 per phase. Full system replacement (14-28 weeks): €120,000-300,000. Data migration: €20,000-60,000. Monthly modern system operation: €2,000-6,000.
Verified reviews from real client engagements — sourced from our public testimonial archive and Clutch profile.
My experience is throughout positive. Communication, service, the short response times and the flawless execution of a challenging topic was absolutely great. ZTABS is definitely my first choice again.
Christian Neff
Bank Software Advisory · Bank Software Advisory
Fintech
Fantastic Agency! I couldn't fault them even if I tried. They always go above and beyond to meet your expectations and always produces quality work. Thank you ZTABS.
Stephanie Kal
CEO · Beauty Finder Australia
Marketplace
It has been great working with ZTABS. They bounce off the ideas along the way. Amazing Experience.
Joel Rowe
CEO · Drill Quoter
Marketplace
We don't just contract. We ship and operate our own software. 23 products in production.
Common questions about legacy app modernization for Helsinki businesses
Yes — that's the core principle. The strangler fig pattern: new system built alongside legacy, functionality migrated incrementally, legacy decommissioned only after modern system is proven. Citizens and users never experience downtime. Parallel processing validates identical results before cutover.
ZTABS is a remote-first legacy app modernization agency serving Houston businesses — including incremental modernization, business logic preservation, data migration. We work with Energy & Oil/Gas, Healthcare & Biotech, Aerospace & Defense companies in Houston, TX via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Legacy App Modernization in New York, NYZTABS is a remote-first legacy app modernization agency serving New York businesses — including incremental modernization, business logic preservation, data migration. We work with Finance & Fintech, Media & Advertising, Fashion & Retail companies in New York, NY via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Legacy App Modernization in Los Angeles, CAZTABS is a remote-first legacy app modernization agency serving Los Angeles businesses — including incremental modernization, business logic preservation, data migration. We work with Entertainment & Media, E-commerce & DTC Brands, Gaming & AR/VR companies in Los Angeles, CA via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Development in Helsinki, FinlandZTABS is a remote-first web development agency serving Helsinki businesses — including full-stack development, progressive web apps, api development. We work with Gaming, AI & Deep Tech, CleanTech companies in Helsinki, Finland via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Design in Helsinki, FinlandZTABS is a remote-first web design agency serving Helsinki businesses — including ui/ux design, responsive design, custom interfaces. We work with Gaming, AI & Deep Tech, CleanTech companies in Helsinki, Finland via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
AI Development in Helsinki, FinlandZTABS is a remote-first AI development agency serving Helsinki businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with Gaming, AI & Deep Tech, CleanTech companies in Helsinki, Finland via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Legacy App ModernizationLearn more about our legacy app modernization services nationwide.
Partner with ZTABS for expert legacy app modernization in Helsinki. Get a free consultation today.
