ZTABS modernizes legacy applications for Helsinki enterprises in government, banking, insurance, healthcare and industrial sectors. Finnish government agencies operate systems built during the early 2000s e-government wave on Java EE, .NET Framework and custom PHP platforms. Banks run core systems reaching end of life. Insurance companies operate policy management and claims systems built decades ago. ZTABS is remote-first by design from our Houston, Texas office.
Helsinki legacy modernization demand spans Finnish central government system upgrades, banking core modernization for Finanssivalvonta-supervised institutions, healthcare patient information system migration for wellbeing services counties, and insurance platform replacement.
Legacy app modernization in Helsinki at a glance
| Need | What we build | Key requirement |
|---|
| Government | Agency system modernization | Suomi.fi, DVV, GDPR |
| Banking | Core system migration | Finanssivalvonta, SEPA |
| Healthcare | Patient system consolidation | Kanta, Findata, wellbeing counties |
| Insurance | Policy system replacement | Solvency II, Finnish products |
| Industrial | ERP and MES upgrades | IoT, AI integration |
Finnish government system modernization
Finnish central government agencies including KELA, Vero, DVV and Migri operate systems built during Finland's progressive e-government push. These systems are 15 to 20 years old, built on Java EE application servers (WebLogic, WebSphere, JBoss), Oracle or PostgreSQL databases and custom frameworks that predated modern web development.
Regulatory logic complexity. Systems encode Finnish regulatory logic that has been amended dozens of times. Each amendment implemented as code changes layered over previous implementations creates complex codebases requiring archaeological excavation through years of change history.
Suomi.fi integration. The OIDC test environment is scheduled for 3 December 2026 with production on 28 January 2027 and SAML transition ending by 1 June 2028, per the 7 October 2026 DVV schedule. Actual per-service rollout and testing timelines apply. Legacy systems modernized for OIDC compatibility per the published transition timeline.
API integration. Government systems increasingly expose data and services through modern APIs. Legacy systems not designed for API access require either retrofit or replacement with API-native platforms.
Modernizing Finnish government or banking systems?
Tell us about your legacy platform, Suomi.fi integration requirements and regulatory logic complexity. We start with assessment covering business rule extraction, data analysis and modernization strategy.
Municipal system consolidation
The 2023 wellbeing services county reform transferred healthcare and social service responsibility to 21 wellbeing services counties. Helsinki organises its own social and healthcare services, and HUS provides specialist care under the Uusimaa arrangement. Previously municipalities had their own systems, some shared platforms like Lifecare and Pegasos, some custom. Counties now need to consolidate multiple systems into unified county-level platforms.
Patient information migration. Decades of patient data in legacy formats. Custom clinical workflows encoded in legacy system configurations. Integration with hundreds of medical devices, laboratory systems and pharmacy systems communicating through legacy interfaces.
Kanta integration. National health data repository. Legacy patient systems modernized for Kanta integration and modern clinical workflows.
Banking and insurance legacy modernization
Finnish banks operate core systems and customer-facing applications on technologies reaching end of life. Insurance companies operate policy management and claims systems encoding complex Finnish insurance regulations.
Core banking. Finnish payment infrastructure including SEPA and domestic clearing. Finnish regulatory reporting. Finnish product specifics including ASP savings accounts, PS savings and pension-linked products. Temenos, Mambu or Thought Machine considered as replacements for legacy core banking platforms.
Insurance policy system. Finnish insurance products encoding decades of regulation, pricing models based on Finnish actuarial data and claim handling procedures. Migration requires careful extraction and re-implementation of Finnish-specific business logic. IFRS 17 reporting capabilities enabled.
Finnish regulation
GDPR. Roles, bases, transfers and Finnish sector-specific data processing requirements assessed per system.
Findata. The permit authority for secondary use of health and social data. Individual-level data permits are granted for scientific research, statistics, public authority planning, reporting and education. Anonymous aggregated statistical data is also available for development and innovation, knowledge management, and steering and supervision purposes. Own-register planning and evaluation may not require a separate Findata permit. Findata does not control all underlying clinical data, and not all clinical system migrations require a Findata permit.
Vero. 25.5% standard VAT from September 2024 and 13.5% reduced rate from January 2026 with categories and dates assessed where relevant.
Finnish and Swedish. Language requirements assessed per product, audience and regulatory context under the Language Act. Government services have specific obligations; private-sector requirements depend on the actual audience and applicable rules.
Automated administration. Scope assessed per system and decision type. Irreversible payment and clinical decisions warrant additional rollback review.
Strangler fig for Finnish systems
Seam selection. Government seams: citizen services, regulatory processing, reporting, integration. Banking seams: accounts, payments, lending, regulatory reporting. Healthcare seams: patient records, clinical workflows, pharmacy, laboratory. Each function extracted independently.
Single authoritative write. One system authoritative for each transaction type and period during coexistence. Government dual-write dangerous for regulatory processing. Banking dual-write dangerous for settlement reporting. CDC with versioning and conflict detection.
Reconciliation. Idempotency keys enforced by receiving side. Finite retries with DLQ. Unknown outcomes require reconciliation before replay, especially for tax calculations, benefit payments, SEPA settlements and clinical records.
Data migration methodology
Government data. 15 to 20 years of accumulated regulatory data migrated with verification. Finnish-specific data formats including personal identity codes handled per privacy requirements. Audit trail continuity maintained with no gaps between legacy and modern audit trails.
Banking data. Account records, transaction history and regulatory data migrated with agreed reconciliation tolerances and domain-owner sign-off. Finnish regulatory reporting data maintained. Multi-product portfolio data preserved.
Healthcare data. Patient records, clinical data, laboratory results and pharmacy records migrated with clinical verification. Kanta integration data maintained. Multiple predecessor municipal system data consolidated.
Data type mapping. Types, nulls, time zones, currency, rounding, identifiers, encoding, history and crosswalks reconciled. Finnish-specific: personal identity code handling, EUR currency precision, Finnish date conventions, character encoding for Finnish and Swedish characters.
Cutover rehearsal. Observable acceptance with measurable RTO, RPO and latency targets. Government cutover timed to avoid peak citizen service periods. Banking cutover timed for settlement cycles.
Inventory and discovery
Helsinki enterprise modernization begins with complete inventory: applications, users, scheduled jobs, database procedures, reports, file and API dependencies, vendor contracts, supported versus end-of-life versions.
Business rules discovered with domain experts through representative transaction analysis. Government rules validated against regulatory requirements. Banking rules validated against Finanssivalvonta requirements. Healthcare rules validated against clinical standards.
Illustrative Example
Hypothetical: Finnish government agency modernizing 2007-era Java EE processing system
A Finnish central government agency operates a Java EE application on Oracle WebLogic with Oracle database processing hundreds of thousands of applications annually. The system encodes 19 years of regulatory amendments. Two remaining developers who understand the system are approaching retirement. The JSP frontend is not mobile-responsive and not integrated with Suomi.fi authentication.
Strangler fig modernization would create a modern citizen portal with Suomi.fi OIDC authentication first while the legacy backend continues processing. Business rules extracted and converted to automated test suites. Integration hub replacing SOAP web services with modern REST APIs. Decision engine migrating regulatory logic from Java code and Oracle stored procedures to a declarative rule engine.
Assumptions: Java code accessible for analysis, regulatory staff available for rule validation, Suomi.fi OIDC timeline confirmed, and parallel processing feasible for validation periods. Residual risks include undiscovered business rules in decades of code, integration dependencies with other government systems, staff transition and regulatory amendment pace. No guarantee of specific processing speed, cost reduction or citizen satisfaction outcome.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
Integration and dependency management
Government integrations. DVV population registry, Suomi.fi authentication, Vero tax systems, KELA benefits systems and inter-agency data exchange.
Banking integrations. Finanssivalvonta regulatory reporting, SEPA payment networks, Finnish domestic clearing and correspondent bank connections.
Healthcare integrations. Kanta national health data, Findata research access, laboratory systems, pharmacy systems and medical device interfaces.
Modernization approach selection
Helsinki enterprises need clear criteria for choosing between approaches.
Rehost. Lift and shift to modern infrastructure. Lower risk than rewrite but benefits are limited. Appropriate for systems that work well but run on unsupported infrastructure; risk depends on actual dependencies and configuration.
Replatform. Move to modern platform with minimal code changes. Moderate risk. Example: migrating from WebLogic to containerised deployment.
Refactor. Restructure code for modern architecture. Moderate to high effort. Preserves existing tested business logic.
Replace. Build new system. Highest effort and risk. Appropriate when legacy system is too brittle to refactor.
Regression and testing
Representative business-critical paths: government citizen service processing with Suomi.fi authentication, banking transaction lifecycle, healthcare patient record with Kanta integration. Meaningful integration, performance and manual UAT with domain expert approval.
Cost and timeline
Legacy system modernization follows the published cost guide.
| Tier | Range | Timeline | Example |
|---|
| UI Modernization | $40K to $100K | 8 to 16 weeks | New frontend, API wrapper, improved UX |
| Re-Platforming | $100K to $250K | 16 to 32 weeks | Modern stack, containerization, cloud, data migration |
| Re-Architecture | $250K to $400K | 8 to 14 months | Decompose monolith, event-driven, modern data layer |
| Full Rebuild | $400K to $500K+ | 12 to 18+ months | Ground-up rebuild, agreed availability and cutover rehearsal |
Vendor comparison
Ranges reflect re-platforming a 10 to 15 year old business-critical system using a strangler fig approach, modern stack, API wrappers, phased data migration and regression harness.
| Vendor type | Typical cost | Timeline |
|---|
| Freelance or dev collective | $40K to $130K | 5 to 12 months |
| Offshore systems integrator | $60K to $200K | 8 to 14 months |
| Boutique modernization specialist (ZTABS tier) | $100K to $280K | 6 to 12 months |
| Big 4 consultancy | $300K to $1M+ | 10 to 18 months |
| SaaS replacement vendor | $50K to $200K implementation | 4 to 9 months |
Ranges are 2026 US-buyer guide-based planning benchmarks. Where applicable to the agreed migration, parallel-running infrastructure, senior-staff knowledge transfer and compliance revalidation for actual SOX, HIPAA or FDA requirements can add a planning allowance of $100K to $500K or more across vendor paths. Scope covers agreed engineering and revalidation support; any independent assurance engagement is scoped separately. These are engagement planning allowances, not an empirical market survey or an automatic surcharge for every system.
Proposal evaluation criteria
When evaluating vendor proposals for legacy modernization, assess these areas with named role responsibilities:
- Scope and system discovery. What applications, databases, integrations and scheduled jobs are inventoried? Who performs code archaeology, business-rule documentation and gap analysis? What is included versus excluded from the engagement scope?
- Integration and migration acceptance. What are the agreed data migration tolerances, reconciliation method and domain-owner sign-off criteria? Who builds and validates migration scripts? How are legacy formats, encoding and data quality exceptions handled?
- Security and data rights. Who owns source code, data and deployed infrastructure after handover? What are data retention, deletion and portability terms? How is GDPR compliance responsibility allocated between customer and vendor?
- Verification, rollback and operations. What regression, performance and UAT methodology is proposed? What is the rollback plan after schema and data changes? Who monitors production post-cutover and for how long?
- Delivery ownership and cost dependencies. What is fixed-scope versus time-and-materials? What are infrastructure, licensing and parallel-running cost responsibilities? What triggers change orders? Are independent CPA SOC 2 opinions scoped separately from readiness preparation?
- Training, validation, support and working arrangements. Who trains end users, in what agreed working languages, and with what approved translated materials? Who provides ongoing support and at what SLA? What on-site arrangements are separately agreed if required? What customer staff participation is needed for domain validation and UAT?
Need help modernizing Finnish enterprise systems?
Share your legacy system landscape, regulatory requirements and modernization constraints. We provide a scoped estimate based on system complexity.
How delivery works
ZTABS is remote-first by design from our Houston, Texas office. Overlap with Helsinki business hours for coordination and review.
When ZTABS is not the right fit
- The system still works and nobody is asking for changes. Wait for a real forcing function before committing to modernization.
- Core banking platform vendor selection for this engagement. Licensed vendor selection and implementation is a separately engaged scope.
- On-site embedded team required for this engagement. ZTABS is remote-first by design. On-site staffing is a separately agreed arrangement.
- Finanssivalvonta or DPA regulatory advisory for this engagement. Regulatory advisory is a separate engagement from platform engineering.
White-label AI products
ZTABS builds custom white-label AI products for clients to brand and resell. Helsinki technology companies can commission white-label AI platforms for distribution under their own brand.
Industrial legacy modernization
Finnish manufacturing companies operate production management and ERP customizations on legacy platforms. Critical operational systems work reliably but have limited integration paths to modern IoT, AI or cloud services depending on actual version, licence and interfaces.
ERP modernization. SAP R/3 with Finnish customization for Finnish accounting standards, payroll and statutory reporting migrated to current versions. Custom developments analysed for migration or replacement.
MES modernization. Manufacturing execution systems modernized for Industry 4.0, IoT sensor integration and real-time quality analytics. Legacy SCADA integration preserved during transition.
Logs and retention
Logs minimise and redact secrets and regulated payloads with actual retention and legal holds. Finnish statutory accounting records retained per Kirjanpitolaki requirements. Healthcare records retained per Kanta and patient data requirements. Not all logs same retention period. Personal identity codes minimised where full identifier unnecessary.
Assessment methodology
Application archaeology for Helsinki systems covers Java EE programme analysis for government business rule extraction, core banking programme analysis for transaction rules, healthcare system analysis for clinical workflow extraction and regulatory reporting analysis for Finanssivalvonta compliance verification.
Data type mapping for Helsinki industries
Helsinki industry data has unique types requiring careful migration planning. Government: Finnish personal identity code handling per GDPR assessment, regulatory reporting fields, Suomi.fi authentication session identifiers. Banking: SEPA payment identifiers, Finanssivalvonta regulatory reporting fields, Finnish product identifiers. Healthcare: Kanta patient record identifiers, clinical data formats, laboratory result coding systems and pharmacy data exchange formats.
Cutover rehearsal detail
Observable acceptance with measurable RTO, RPO and latency targets. Government cutover timed to avoid peak citizen service periods such as tax filing deadlines. Banking cutover timed for settlement cycles. Healthcare cutover planned around clinical schedule gaps.
Rollback feasibility assessed after schema, data and contract changes. Government regulatory submissions, banking payments and clinical records may not be automatically reversible. Compensations can require regulatory, financial or clinical review.
Risks and mitigations
Finnish regulatory logic preservation. Rules extracted, documented and tested with agreed fixtures and tolerances. Automated test suites run against both legacy and modern systems; exact-match tests verify covered scenarios but cannot prove completeness of every business rule. Domain-owner acceptance required.
Suomi.fi transition. OIDC migration tracked against published timeline. SAML fallback maintained during transition.
Government integration dependencies. Each government system integration documented and migration coordinated with partner agencies.
Handover
Modernization handover includes runbooks, data lineage, licensing, support contacts and accountable owners. Government handover includes regulatory compliance documentation and Suomi.fi integration specifications. Banking handover includes Finanssivalvonta reporting specifications.
Ready to modernize your Helsinki legacy systems?
Share your legacy system landscape, Suomi.fi requirements and modernization constraints. We start with assessment covering application archaeology, compliance mapping and modernization strategy.