ZTABS modernizes legacy applications for Zurich enterprises in banking, insurance, pharmaceutical and manufacturing. Swiss banks operate legacy core banking systems managing trillions in assets. Insurers run legacy policy administration across multiple product lines. Pharma companies headquartered in Basel operate validated systems across global operations. ZTABS is remote-first by design from our Houston, Texas office.
Zurich legacy modernization demand spans Swiss banking core system modernization for FINMA-supervised institutions, insurance platform migration, pharma manufacturing system upgrades and industrial manufacturing ERP modernization.
Legacy app modernization in Zurich at a glance
| Need | What we build | Key requirement |
|---|
| Banking | Core system modernization | FINMA, SIX |
| Insurance | Platform migration | FINMA, Solvency, SST |
| Pharma | MES and ERP upgrades | GMP, Swissmedic |
| Manufacturing | ERP modernization | SAP S/4HANA, Swiss accounting |
| Wealth management | Platform modernization | FINMA, cross-border |
Swiss banking core system modernization
Swiss banks operate legacy core banking systems accumulated over decades of private banking, retail banking and institutional operations. Avaloq, Temenos and custom COBOL systems managing client assets and regulatory compliance.
Core banking migration. Account management, portfolio management, transaction processing, general ledger and client information modernized. FINMA supervisory expectations addressed at each migration phase. Direct EU DORA applies only to actual EU entity or contract scope; Swiss operations governed by FINMA institution and function rules. Multi-currency wealth management capabilities preserved.
Wealth management. Legacy portfolio management systems modernized for real-time portfolio analytics, automated reporting, risk management and client advisory tools. Cross-border wealth management regulatory requirements preserved.
SIX integration. SIX Swiss Exchange, SIX Interbank Clearing, securities settlement and market data connections addressed at each migration phase.
TWINT integration. TWINT actual capabilities and merchant integration requirements. Mobile payment system integration maintained in modernized banking systems.
Temenos and Avaloq. Actual module, version and licence requirements. Custom integrations and extensions analysed for migration compatibility.
Modernizing Swiss banking or insurance systems?
Tell us about your core banking platform, FINMA requirements and modernization constraints. We start with assessment covering business rule extraction, data analysis and modernization strategy.
Insurance platform modernization
Swiss insurers operate legacy policy administration, claims and actuarial systems serving domestic and international markets.
Policy administration. Life, health and P&C insurance policy lifecycle modernized. Actuarial calculations for pricing, reserving and regulatory reporting preserved. FINMA SST requirements addressed. Multi-language support for German, French, Italian and Romansh.
Claims processing. Claims workflow modernized for digital submission, automated assessment and faster settlement. Swiss-specific auto insurance and health insurance claims requirements preserved.
SST reporting. Swiss Solvency Test reporting requirements addressed in modernized actuarial and risk management systems.
Pharma manufacturing modernization
Roche and Novartis are Basel-headquartered, providing sector context for Swiss pharma but not claimed as ZTABS clients. Swiss pharma manufacturers operate validated MES and ERP systems requiring modernization while maintaining regulatory compliance.
MES modernization. Manufacturing execution systems modernized for real-time production monitoring, batch record management and quality analytics. Swissmedic and EU GMP requirements addressed. GAMP 5 risk-based approach.
ERP upgrades. SAP and custom ERP systems with Swiss pharma customisation migrated to current versions. Actual module, version and licence requirements assessed per product.
Swissmedic. Swiss health authority requirements for pharmaceutical manufacturing, distribution and clinical trials. Distinct from EU EMA requirements.
Swiss regulation
FADP. Actual purpose, roles, security and foreign disclosure requiring adequate country or qualifying safeguards or applicable derogations. Not GDPR-identical. Swiss-specific requirements assessed.
GDPR Article 3. Applies when establishment context, or offering to individuals in the Union, or monitoring behaviour in the Union. Not generic EU clients or citizens or any monitoring. Swiss companies assess GDPR applicability alongside FADP per actual processing scope.
FADP Article 21. Solely automated decision with legal or significant effect requires practical information, viewpoint opportunity and human review. Exceptions: contract with direct connection and request granted, or explicit consent to automated decision. Not all automated processing triggers Article 21. Not any contract alone.
FINMA. Actual supervised entity, materiality and outsourcing requirements. Material outsourcing notification, governance, inventory, contract, audit access and legal notification or approval triggers. Direct EU DORA applies only to actual EU entity or contract scope. Swiss operations governed by FINMA institution and function rules. Not all outsourcing requires universal pre-approval. Not all insurers covered by bank circular; proportionality applies.
Swiss qualified signature. Actual recognised qualified certificate and qualified timestamp, distinct from advanced electronic signature and legal use-case requirements. Not all digital steps require qualified signature. Modernized systems implement appropriate signature levels per actual legal requirements.
No general 14-day withdrawal right. No Swiss online withdrawal right equivalent to EU consumer rights directive. Swiss consumer protection assessed per actual law.
Federal languages. Federal publication requirements in German, French, Italian and Romansh where applicable. Not all private Swiss applications require four languages. Actual customer journeys, staff languages and documentation agreed per engagement.
Strangler fig for Swiss systems
Seam selection. Banking seams: accounts, portfolio management, payments, wealth management, regulatory reporting. Insurance seams: policy administration, claims, actuarial, SST reporting. Pharma seams: production, quality, distribution, regulatory. Each function extracted independently.
Single authoritative write. One system authoritative for each transaction type and period during coexistence. Banking dual-write dangerous for FINMA regulatory reporting and client asset management. Insurance dual-write dangerous for SST 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 securities settlements, insurance premium settlements, SIX clearing transactions and pharma batch records.
Data migration methodology
Banking data. Account records, portfolio holdings, transaction history, client information and regulatory reporting data migrated with reconciliation against agreed record totals, tolerances and exception register with owner acceptance. Multi-currency data with CHF, EUR, USD, GBP and other currencies. Cross-border wealth management data with jurisdiction-specific regulatory requirements.
Insurance data. Policy records, claims history, actuarial data and SST reporting data migrated with actuarial verification. Multi-language policy documents preserved.
Pharma data. Batch records, quality data, validation documentation and regulatory submission data migrated with GMP compliance.
Data type mapping. Types, nulls, time zones, currency, rounding, identifiers, encoding, history and crosswalks reconciled. Swiss-specific: AHV number handling, multi-currency precision for CHF and cross-border currencies, Swiss date and number formatting, federal language encoding.
Cutover rehearsal. Observable acceptance with measurable RTO, RPO and latency targets. Banking cutover timed for settlement cycles and SIX clearing windows. Insurance cutover timed for renewal cycles. Pharma cutover planned for production schedule gaps.
Inventory and discovery
Zurich enterprise modernization begins with complete inventory: applications, users, scheduled jobs, database procedures, reports, file and EDI dependencies, vendor contracts, supported versus end-of-life versions.
Business rules discovered with users through representative transaction analysis. Banking rules validated against FINMA requirements. Insurance rules validated against FINMA and SST requirements. Pharma rules validated against Swissmedic and GMP requirements.
Illustrative Example
Hypothetical: Swiss bank modernizing legacy internet banking and wealth management for digital client experience
A Zurich private bank operates legacy core banking and internet banking systems serving wealth management clients across multiple jurisdictions. The system manages portfolios, processes transactions, generates regulatory reports and provides client reporting. Legacy internet banking cannot support modern digital advisory tools and mobile-first experience.
Strangler fig modernization would create modern API layer for client-facing services first, then progressively migrate portfolio management and transaction processing. Digital advisory platform enabled while legacy continues processing. Each jurisdiction migrated independently starting with Swiss domestic operations.
Assumptions: legacy code accessible for analysis, wealth management staff available for rule validation, FINMA notification requirements understood, and parallel processing feasible for validation periods. Residual risks include undiscovered business rules in legacy wealth management, cross-border regulatory complexity, multi-currency data migration and staff transition. No guarantee of specific processing speed, cost reduction or regulatory outcome.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
Integration and dependency management
Banking integrations. FINMA regulatory reporting, SIX Swiss Exchange, SIX Interbank Clearing, SWIFT, correspondent bank connections, TWINT.
Insurance integrations. FINMA regulatory reporting, SST submissions, reinsurance connections.
Pharma integrations. Swissmedic reporting, EU GMP reporting, supply chain connections, quality management systems.
Logs and retention
Logs minimise and redact secrets and regulated payloads with actual retention and legal holds. Swiss OR 10-year retention for accounting books, records and annual management or audit reports from financial-year-end, not all business records or logs. FINMA record retention for regulated entities. FADP personal data retention principles. Foreign transfer requires adequate country or qualifying safeguards or applicable derogations, not only adequate countries. Not all logs same retention period. AHV number minimised where full identifier unnecessary.
Assessment methodology
Application archaeology for Zurich systems covers core banking programme analysis for business rule extraction, Temenos and Avaloq extension analysis for migration compatibility, SAP custom ABAP analysis for S/4HANA readiness and regulatory reporting analysis for FINMA compliance verification.
Regression and testing
Representative business-critical paths: banking transaction lifecycle with SIX settlement and TWINT, insurance policy lifecycle with SST reporting, pharma production batch record with Swissmedic compliance. 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 target, rehearsed staged cutover |
Vendor comparison
Ranges are 2026 US-buyer guide-based estimates for 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 |
| ZTABS | $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 |
Parallel-running infrastructure, senior knowledge-transfer time and where applicable compliance revalidation can add a combined scope-dependent $100K to $500K+ planning allowance. The guide's examples are SOX, HIPAA and FDA; actual applicable regime depends on the engagement.
Proposal evaluation criteria
Evaluate any vendor proposal against these six criteria regardless of price tier.
| Criterion | What to verify |
|---|
| Strategy, deliverables and acceptance | Defined modernization phases with measurable acceptance criteria at each stage |
| Data source-of-truth and reconciliation | Which system is authoritative per object and period, agreed reconciliation tolerances and exception register |
| Rehearsal, cutover and rollback | Rehearsed cutover with RTO and RPO targets, documented rollback feasibility after schema and data changes |
| Security, privacy, compliance and approval scope | Applicable regulations identified with actual approval authority and scope |
| Full recurring costs | Licensing, parallel-run infrastructure, support, monitoring and decommission costs beyond initial build |
| Human roles and responsibilities | Provider and customer trainer-validator-support split, agreed working languages, translated materials review and on-site responsibilities where needed |
Need help modernizing Swiss enterprise systems?
Share your legacy system landscape, FINMA 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 Zurich 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.
- Core banking platform vendor selection. Core banking platform licence selection, vendor-led configuration and FINMA notification are the licensed vendor's and customer's scope. This engagement modernizes the surrounding integration, data migration and regulatory reporting connections.
- On-site programme office and multi-vendor coordination. This engagement delivers application modernization. Separately contracted programme governance, on-site management and advisory retainers have different scope and responsibilities.
- On-site embedded team. ZTABS is remote-first by design. On-site staffing, training and support retainers for this engagement are separately agreed.
- FINMA or FDPIC regulatory advisory. This engagement builds platforms, not regulatory advice. Regulatory advisory is separately engaged.
White-label AI products
ZTABS builds custom white-label AI products for clients to brand and resell. Zurich technology companies can commission white-label AI platforms for distribution under their own brand.
Cutover rehearsal detail
Observable acceptance with measurable RTO, RPO and latency targets. Banking cutover timed for SIX settlement cycles and clearing windows. Insurance cutover timed for renewal cycles and SST reporting periods. Pharma cutover planned for production schedule gaps.
Rollback feasibility assessed after schema, data and contract changes. Securities settlements, insurance premium settlements, SIX clearing transactions and pharma batch records may not be automatically reversible. Compensations can require regulatory, actuarial, settlement or quality review.
Data type mapping for Zurich industries
Zurich industry data has unique types requiring careful migration planning. Banking: IBAN formats with Swiss bank codes, SIX security identifiers, portfolio valuation dates with multi-currency precision, FINMA regulatory reporting fields, wealth management client identifiers. Insurance: Swiss policy identifiers, SST reporting fields, actuarial valuation dates, multi-language policy document references. Pharma: batch record identifiers, GMP validation record identifiers, Swissmedic registration codes.
Modernization approach selection
Zurich enterprises need clear criteria for choosing between approaches.
Targeted remediation. Adding specific capabilities. Example: adding modern digital advisory frontend to legacy wealth management system while keeping legacy for portfolio management.
Re-platforming. Moving to modern infrastructure while preserving logic. Example: migrating legacy insurance processing to cloud while preserving actuarial algorithms.
Re-architecture. Decomposing monolith into services. Example: extracting portfolio management, client reporting and regulatory as independent services.
Full rebuild. Ground-up development for systems where legacy code is unmaintainable. Example: replacing end-of-life internet banking platform.
Industrial manufacturing modernization
Swiss precision manufacturing and industrial companies operate legacy ERP and MES systems with Swiss-specific customisation.
Abacus ERP. Swiss ERP system actual module, version and licence. Custom integrations analysed. Migration to current versions or replacement assessed per actual system complexity.
Precision manufacturing. Swiss precision manufacturing MES with quality tolerances and traceability requirements. ISO 13485 medical device manufacturing where applicable.
Risks and mitigations
FINMA regulatory continuity. All regulatory reporting addressed at each migration phase. Material outsourcing notification where required.
Cross-border complexity. Each jurisdiction migrated independently with jurisdiction-specific regulatory validation and data protection assessment per FADP and GDPR.
Multi-currency precision. CHF and cross-border currency precision addressed at each migration phase. SIX settlement reconciliation validated. Wealth management portfolio valuations reconciled across all currencies after each phase.
Fintech and insurtech modernization
Zurich fintech and insurtech companies operate legacy platforms requiring modernization for scale and FINMA regulatory compliance.
Fintech platform modernization. Legacy payment and wealth management platforms modernized for FINMA regulatory compliance, open banking requirements and real-time processing capabilities.
Insurtech platform modernization. Legacy insurance technology platforms modernized for digital distribution, automated underwriting and claims processing. FINMA requirements for insurance intermediary and distributor systems addressed.
Blockchain and DLT. Swiss regulatory framework for DLT and blockchain. Legacy systems integrating with or replacing DLT-based solutions where applicable. SIX Digital Exchange context.
Handover
Modernization handover includes runbooks, data lineage, licensing, support contacts and accountable owners. Banking handover includes FINMA compliance documentation, SIX integration specifications and TWINT integration documentation. Pharma handover includes validation documentation and Swissmedic compliance records. Industrial handover includes Abacus configuration documentation.
Ready to modernize your Zurich legacy systems?
Share your legacy system landscape, FINMA requirements and modernization constraints. We start with assessment covering application archaeology, compliance mapping and modernization strategy.