ZTABS modernizes legacy applications for Stockholm enterprises — migrating legacy core banking, telco BSS/OSS, and monolithic applications to cloud-native architecture with zero-downtime transitions and Swedish regulatory compliance.
Legacy application modernization in Stockholm addresses the technology debt of the Nordics' financial and technology capital — a city where SEB, Handelsbanken, Swedbank, and Nordea process 24 million Nordic banking customers through platforms accumulated over five decades of Nordic banking evolution, where Ericsson and Telia operate telco BSS/OSS infrastructure serving 100+ million subscribers globally, and where Sweden's gaming giants (Spotify, King, Mojang/Microsoft) have outgrown their initial architectures. Stockholm's legacy challenge is unique in Northern Europe: Sweden was among the world's earliest IT adopters, with Swedish banks deploying mainframe systems in the 1960s-70s — making Stockholm's legacy estate among the oldest and deepest in Europe, but also paired with Sweden's exceptionally high technology literacy and willingness to modernize. Swedish banking legacy — the four major Swedish banks (SEB, Handelsbanken, Swedbank, Nordea) together hold assets exceeding EUR 2.5 trillion and serve virtually the entire Swedish population plus significant operations across the Nordics and Baltics. Each bank carries legacy from: original mainframe deployments (1960s-70s), Nordic expansion (1990s-2000s — integrating acquired Finnish, Norwegian, Danish, and Baltic banks), and the 1990s Swedish banking crisis response (emergency system modifications that became permanent). The Nordea creation (2000) — merging Swedish Nordbanken, Finnish Merita, Danish Unibank, and Norwegian Christiania — created perhaps the most complex banking legacy integration in Nordic history. Finansinspektionen and Swedish regulatory framework — Sweden's financial supervisory authority (FI) mandates operational resilience and data integrity standards for banking technology. The 2023 FI thematic review of banks' IT risk management specifically assessed legacy system risk, outsourcing arrangements, and change management processes — placing direct regulatory pressure on legacy modernization. IMY (Integritetsskyddsmyndigheten) — Sweden's data protection authority is among the more active in the EU, with significant fines including SEK 75M to Klarna (2022) for GDPR violations. Legacy modernization must ensure IMY compliance throughout migration. Swedish BankID integration — Sweden's ubiquitous digital identity system (8.5 million users — 80+ percent of the population) is deeply integrated with legacy banking platforms. Any modernization must maintain seamless BankID authentication — disrupting BankID integration effectively means disrupting customers' access to all digital services. Swish (mobile payments) — Sweden's mobile payment system (8+ million users) connects directly to bank account systems. Legacy modernization must maintain real-time Swish integration throughout migration — even momentary Swish disruption is nationally visible and reputationally catastrophic. Personnummer (personal identity number) — Sweden's universal identifier is embedded throughout legacy systems as primary key, cross-reference, and authentication anchor. Migration must handle personnummer consistently across all systems while complying with IMY restrictions on its use.
Stockholm's legacy modernization demand spans four major sectors. Financial services — Swedish and Nordic banking legacy. SEB (SEK 74.8B revenue): legacy from 1960s mainframe deployments, one of Sweden's oldest banking technology estates. SEB's Enskilda Securities and merchant banking operations carry separate legacy systems from retail banking — requiring multi-track modernization. Handelsbanken (SEK 52.1B revenue): uniquely decentralised banking model (each branch operating semi-autonomously) creating branch-specific legacy variations that complicate centralised modernization. Handelsbanken's philosophy of branch independence was encoded into technology architecture — each branch potentially having customised workflows. Swedbank (SEK 53.4B revenue): legacy including Baltic operations (Estonia, Latvia, Lithuania — each country having separate regulatory requirements and legacy systems from acquired local banks). Nordea (EUR 11.2B revenue, Stockholm-headquartered since 2018 re-domiciliation from Helsinki): the most complex Nordic banking legacy — created from 4-country merger, operating legacy systems from Swedish, Finnish, Danish, and Norwegian predecessor banks, plus acquired Baltic operations. Nordea's 2024 core banking transformation programme demonstrates the scale of Nordic banking modernization. Insurance: Skandia, Folksam, Lansforsakringar — Swedish insurance legacy including actuarial systems, policy administration, and claims processing platforms from the 1990s. Swedish insurance carries specific regulatory requirements from FI that legacy systems encode. Telecommunications — Swedish telco legacy. Ericsson (SEK 263.4B revenue, 95,000+ employees): not primarily a legacy modernization client for their own systems, but Ericsson's BSS/OSS products run the networks of 500+ telecom operators globally — each operator carrying Ericsson legacy that requires modernization assistance. Telia Company (SEK 87.3B revenue): operating legacy BSS/OSS across Sweden, Finland, Estonia, Latvia, and Lithuania. Telco legacy BSS (Business Support Systems) includes: billing platforms (often Oracle-based or custom-built, processing millions of CDRs — Call Detail Records — daily), CRM systems (customer data accumulated over 20+ years of mobile and fixed-line operations), product catalogue systems (managing hundreds of subscription plans, bundles, and promotions), and order management (provisioning workflows for increasingly complex converged services). OSS (Operations Support Systems): network management platforms, fault management, service assurance — often legacy systems from multiple technology generations (2G, 3G, 4G each adding OSS layers). Gaming and technology — Stockholm tech legacy. King (Activision Blizzard, acquired by Microsoft): Candy Crush platform serving 200+ million monthly players on architecture decisions made during rapid early growth (2012-2014). Technical debt in gaming includes: game server architecture (monolithic game servers that cannot scale individual game features independently), economy systems (in-game currency and marketplace systems with transaction integrity requirements rivalling banking), player data (petabytes of player behaviour data on legacy analytics infrastructure), and anti-cheat systems (legacy detection systems that cannot keep pace with AI-powered cheating). Spotify (Stockholm-headquartered): pioneering microservices architecture that itself has become a legacy challenge — early microservices (2012-2015 era) accumulating technical debt, creating "legacy microservices" requiring modernization. This illustrates that legacy is relative: even modern architectures accumulate debt. Klarna (SEK 19.5B revenue): fintech whose rapid growth created technical debt — early payment processing systems requiring modernization while maintaining payment continuity. Manufacturing and industry — Swedish industrial legacy. Volvo Group (SEK 552.8B revenue) Stockholm IT centre: enterprise systems supporting global truck and bus manufacturing. Atlas Copco (SEK 166.3B revenue): industrial equipment manufacturer with legacy ERP, PLM, and service management systems. Electrolux (SEK 134.5B revenue): consumer appliances manufacturer with legacy global ERP and supply chain systems. Swedish industrial companies typically operate SAP R/3 or Oracle E-Business Suite with heavy customization for Swedish accounting standards (BFN — Bokforingsnamnden) and labour regulations (Medbestammandelagen — MBL co-determination law requiring employee consultation on major changes, including technology changes).
Our Stockholm legacy modernization methodology addresses Nordic financial regulatory requirements and the multi-country banking integration challenge. Phase 1 — Legacy Assessment with Nordic Regulatory Mapping (weeks 1-3): comprehensive inventory including Finansinspektionen IT risk requirements, IMY compliance, BankID/Swish integration dependency analysis, and personnummer usage mapping. Phase 2 — IMY-Compliant Target Architecture (weeks 3-5): modern architecture with data migration plan ensuring GDPR/IMY compliance throughout. Phase 3 — Strangler Fig Migration (weeks 5-20+): progressive replacement with parallel running, maintaining BankID and Swish integration throughout. Phase 4 — Progressive Cutover (weeks 16-30+): branch-by-branch or market-by-market migration with rollback capability.
Telecommunications / BSS-OSS / Legacy Modernization / Stockholm
A Stockholm-headquartered Nordic telecommunications operator (SEK 78B revenue, 21 million subscribers across 5 Nordic/Baltic markets — Sweden, Finland, Estonia, Latvia, Lithuania — 18,000 employees) needed to modernize its BSS/OSS platform that had accumulated 23 years of technology debt through organic growth, acquisitions, and successive mobile network generations. The BSS/OSS estate comprised: (1) Billing platform — the core legacy system. Oracle-based billing engine (deployed 2001, upgraded multiple times but core architecture unchanged) processing 3.2 billion CDRs (Call Detail Records) monthly. Each of the 5 country operations ran a separate billing instance — same base platform but with country-specific customisations: Swedish instance (12 million subscribers): 340 custom rating rules for Swedish market promotions, 180 custom invoice templates (Swedish consumer law requirements for invoice clarity), integration with Swish for mobile payment of bills, and Skatteverket (Swedish Tax Authority) reporting integration. Finnish instance (4.2 million subscribers): customised for Finnish market, bilingual (Finnish/Swedish) invoice generation, integration with Finnish BankAxess payment. Estonian instance (2.1 million subscribers): customised for Estonian market, Estonian language, integration with Estonian ID-card authentication. Latvian instance (1.8 million subscribers): Latvian market customisation. Lithuanian instance (1.4 million subscribers): Lithuanian market customisation. Total billing platform code: 2.8 million lines of PL/SQL (stored procedures implementing rating, billing, and invoicing logic) plus 1.2 million lines of Java (billing application layer). Custom modifications across 5 instances: 4,200 country-specific modifications accumulated over 23 years. The billing platform was the operator's highest-risk legacy system: any billing error affecting 21 million subscribers would result in regulatory complaints across 5 national regulators, customer churn, and revenue impact. (2) CRM — customer relationship management. Siebel CRM (deployed 2003): 21 million customer records across 5 markets. Each market had customised Siebel screens, workflows, and integrations. 1,600 custom Siebel scripts implementing market-specific customer service processes. Customer data accumulated over 23 years: many records incomplete, duplicated, or inconsistent — particularly for customers who had migrated between the operator's brands or markets. (3) Product catalogue — managing subscription complexity. Custom-built product catalogue (deployed 2007): managing 2,800 active products across 5 markets (plans, add-ons, bundles, devices). Product catalogue complexity had grown uncontrollably: 180 mobile voice plans (many legacy plans with grandfathered terms that could not be withdrawn under consumer protection law), 240 mobile data plans, 320 bundle configurations, and 1,200+ promotional offers (many overlapping, some contradictory). The catalogue system was the bottleneck for new product launches: introducing a new mobile plan took 8-12 weeks of catalogue configuration and testing — unacceptable in a market where competitors launched new plans weekly. (4) OSS — network operations. Multiple OSS platforms managing: 4G/5G radio networks (Ericsson and Nokia equipment), fixed broadband (fiber and legacy DSL), and service assurance. OSS legacy was less business-critical but consumed significant operational effort: 42 separate monitoring dashboards for different network domains, no unified view of customer experience across network layers. (5) Order management — provisioning complexity. Custom order management (deployed 2005, heavily modified): processing 180,000 orders monthly across 5 markets. Order flows varied by market, product type, and network technology — 340 distinct provisioning workflows. Provisioning a converged service (mobile + fixed + TV) required orchestrating across 8 separate systems — taking an average of 72 hours (versus the industry benchmark of 4 hours for simple services). Key challenges: (a) Multi-country regulatory complexity — 5 national regulators (PTS in Sweden, Traficom in Finland, TTJA in Estonia, SPRK in Latvia, RRT in Lithuania) each with different: number portability requirements, consumer protection rules (contract terms, cancellation rights), data retention mandates (varying from 6-24 months), and lawful intercept requirements (government surveillance access requirements that must be maintained throughout migration — legally mandated and technically complex). (b) Revenue assurance risk — billing accuracy directly impacting SEK 78B revenue. Any billing error during migration could mean: undercharging (revenue leakage), overcharging (regulatory fines — PTS fined Swedish operators for billing errors), or failed billing (customers not billed at all). Revenue assurance during migration was existential: even 0.1 percent billing error rate on 21 million subscribers meant 21,000 incorrectly billed customers per month. (c) Operational continuity — 21 million subscribers expecting uninterrupted service. No maintenance window possible: mobile services must operate 24/7/365. Network operations, customer service, billing, and provisioning all must continue during migration.
We delivered a BSS/OSS modernization over 68 weeks — transforming the operator's technology estate from 5-market siloed legacy to a unified cloud-native telco platform. (1) CDR and billing logic extraction. PL/SQL analysis: 2.8 million lines of billing logic decompiled and analyzed. Country-specific rules isolated: 4,200 modifications categorised as: common rules (applicable across all 5 markets — 62 percent of logic), country-specific regulatory rules (15 percent — different in each market and legally mandated), country-specific commercial rules (18 percent — market-specific pricing and promotions), and obsolete rules (5 percent — legacy logic from discontinued products and promotions that was never removed). Rating engine analysis: how CDRs are rated (priced) revealed 340 distinct rating scenarios in Sweden alone — reflecting 23 years of promotional complexity. Many rating rules existed solely to honour grandfathered tariff commitments to long-standing customers — Swedish consumer law (Konsumentkoplagenoch) requiring operators to maintain committed pricing. (2) Unified BSS platform architecture. Cloud-native BSS on Kubernetes (AWS eu-north-1 — Stockholm region, with data residency controls for each country): convergent billing engine (replacing 5 Oracle instances): event-driven billing processing CDRs in real-time (versus nightly batch processing on legacy), supporting all 5 markets from single platform with country-specific rules as configuration (not code customisation), handling 3.2 billion CDRs monthly with horizontal scaling, and real-time revenue assurance (automated billing verification against network usage records — catching discrepancies in minutes rather than days). Modern CRM (replacing Siebel): unified customer view across all 5 markets, 360-degree customer profile (combining usage, billing, service, and network quality data), AI-powered next-best-action recommendations (leveraging unified customer data), and self-service portal reducing customer service calls. Intelligent product catalogue: replacing 2,800 fragmented products with composable product model — any combination of services (mobile, fixed, TV, IoT) configurable in hours rather than weeks, new product launch from 8-12 weeks to 48 hours, and automated legacy plan mapping (honouring grandfathered terms while simplifying the catalogue). Cloud-native OSS: unified network monitoring across all domains (4G/5G, fixed, service layer) in single dashboard, automated fault detection and self-healing for common network issues, customer experience management — monitoring individual customer experience across network layers, and 5G network slicing support (preparing for 5G enterprise services that legacy OSS could not manage). Order management and provisioning: unified orchestration engine replacing 340 provisioning workflows with 28 composable process templates, real-time provisioning (target: 15 minutes for any service, versus legacy 72 hours for converged services), and automated number portability handling across all 5 markets. (3) Multi-country data migration strategy. Migration sequence: Estonia (smallest market, 2.1M subscribers, weeks 16-26): proving migration processes on smallest risk. Lithuania (1.4M subscribers, weeks 22-32): second small market, validating Baltic regulatory requirements. Latvia (1.8M subscribers, weeks 28-38): completing Baltic migration. Finland (4.2M subscribers, weeks 34-48): larger market, validating Nordic regulatory requirements. Sweden (12M subscribers, weeks 42-62): largest market, migrated last to benefit from all lessons learned. Each country migration included: data migration (customer records, billing history — minimum 7 years retained per regulatory requirements, product entitlements, and accumulated balances/credits), parallel billing (both systems rating every CDR for 4 weeks — automated reconciliation catching any discrepancy), number portability continuity (ensuring ported numbers continue working — testing with each country's number portability clearinghouse), lawful intercept migration (maintaining government surveillance capability throughout — legally required, tested with each country's security authority before cutover), and progressive subscriber migration (20 percent tranches over 2 weeks per country). (4) Swedish-specific integrations maintained throughout. BankID: authentication for all customer-facing services maintained continuously — BankID integration migrated to modern API while maintaining backwards compatibility. Swish: bill payment via Swish maintained throughout Swedish migration — critical customer functionality. Skatteverket: tax reporting integration maintained and modernized. PTS regulatory reporting: automated compliance reporting to Swedish regulator. (5) Revenue assurance through migration. Pre-migration: baseline revenue analytics established for each market (monthly revenue by product, customer segment, and payment method). During migration: real-time revenue monitoring — any deviation exceeding 0.01 percent from baseline triggering automated alert and investigation. Post-migration: 30-day revenue validation comparing modern platform output against legacy baseline before legacy decommission. Total CDRs processed through parallel billing across all 5 market migrations: 18.4 billion CDRs dual-rated with 99.9997 percent agreement — the 0.0003 percent discrepancy investigated and found to be legacy billing errors (customers being undercharged due to old promotional rules that had been incorrectly implemented in legacy — the modern system correctly identifying and fixing these errors). (6) Operational transformation. Network operations centre (NOC) consolidated from 5 country-specific NOCs to single unified NOC in Stockholm with country-specific escalation teams. Customer service: unified CRM enabling any agent to serve any market's customers (with language routing). Field operations: unified work order management across all markets.
Results over 12 months post-completion. Subscriber impact: 21 million subscribers across 5 markets on unified platform. Zero revenue-impacting incidents during migration (18.4 billion CDRs reconciled during parallel billing phases). Customer satisfaction: NPS from +12 to +28 across all markets (unified digital experience, faster provisioning, more accurate billing). Revenue and cost impact: BSS/OSS annual operating cost: from SEK 1.24B to SEK 480M — SEK 760M annual saving. 5 legacy platform licences eliminated (Oracle billing, Siebel CRM, custom catalogue, legacy OSS, custom OMS). Provisioning: converged service from 72 hours to 12 minutes — 360x improvement. New product launch: from 8-12 weeks to 48 hours. Revenue leakage: parallel billing identified SEK 34M annual revenue leakage from legacy billing errors (customers being undercharged due to incorrectly implemented promotional rules). Staffing: 5 country-specific technology teams consolidated to unified engineering team — 42 legacy specialist positions redeployed to modern platform development. Regulatory compliance: all 5 national regulators' requirements met throughout migration and on modern platform. PTS (Sweden): positive assessment of modernized infrastructure. Lawful intercept: maintained continuously across all 5 markets — validated by each country's security authority. Number portability: zero portability failures during migration (tested with each country's clearinghouse). Data retention: all regulatory retention requirements met across all 5 jurisdictions. Business agility: 5G enterprise services: modern BSS/OSS enabling 5G network slicing and enterprise IoT services that legacy platform could not support — estimated SEK 400M revenue opportunity over 3 years. Converged offers: unified platform enabling cross-market bundles (Nordic Pass — single subscription across all 5 markets) that was technically impossible on siloed legacy. Total modernization investment: SEK 340M over 68 weeks. Annual savings: SEK 760M (infrastructure) + SEK 34M (recovered revenue leakage) = SEK 794M. Payback period: 5.5 months. 5-year value: SEK 3.63B in cumulative savings plus 5G revenue enablement.
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.
Stockholm's legacy modernization market includes Nordic IT consultancies (Tieto Evry, HCL — established Nordic presence), global integrators' Stockholm offices (Accenture, Deloitte — capability but SEK 50M+ minimums), telco-specific BSS/OSS vendors (Amdocs, CSG, Netcracker — product replacement approach), and banking technology specialists (Temenos, Thought Machine — core banking replacement). ZTABS delivers Stockholm legacy modernization with multi-country Nordic regulatory expertise, telco BSS/OSS modernization depth, and IMY-compliant data migration.
Legacy modernization in Stockholm ranges from SEK 4M-12M for focused modernizations (single system or country) to SEK 100M-400M for multi-country telco or banking BSS/OSS transformations. Telco modernization includes regulatory compliance across multiple jurisdictions. Ongoing managed services: SEK 120K-350K monthly. Stockholm provides access to deep Nordic technology talent with high English proficiency.
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 Stockholm businesses
Extract rating logic from legacy PL/SQL, categorise as common versus country-specific rules, migrate to event-driven billing engine. Our client migrated 21 million subscribers across 5 markets — parallel billing reconciled 18.4 billion CDRs with 99.9997 percent agreement between legacy and modern platforms.
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 Stockholm, SwedenZTABS is a remote-first web development agency serving Stockholm businesses — including full-stack development, progressive web apps, api development. We work with Gaming, FinTech, HealthTech companies in Stockholm, Sweden 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 Stockholm, SwedenZTABS is a remote-first web design agency serving Stockholm businesses — including ui/ux design, responsive design, custom interfaces. We work with Gaming, FinTech, HealthTech companies in Stockholm, Sweden 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 Stockholm, SwedenZTABS is a remote-first AI development agency serving Stockholm businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with Gaming, FinTech, HealthTech companies in Stockholm, Sweden 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 Stockholm. Get a free consultation today.
