Modernization Vendor Evidence Dataset
Claim-level, source-linked records of what public sources say about software modernization suppliers, plus the registry attributes of every vendor profile and whether it has been verified. Open data under CC BY 4.0.
What this dataset is
A table with one record per claim. Each record links a checked public source (a supplier case study, a customer-published confirmation or official capability documentation) to the migration task it describes, the starting and target systems the source names, what the supplier is recorded as responsible for, the date we checked the page and the limit of what the source shows.
A second table lists the registry attributes of every vendor profile on this site: supplier type, website domain, location, team-size band, the hubs the profile covers and whether the profile has been verified.
What it is not
- It is not a ranking, score or recommendation. A vendor with more records has more checked sources, not better delivery.
- It is not a list of customer outcomes. A supplier-reported case study is that supplier’s own claim; the limitation field states what each source does and does not establish.
- It is not complete. A vendor without claim records has not been checked yet. Unverified means no one has checked the profile against public sources; it is not a judgment of the supplier.
Contents
55 claim records from 32 vendors across 2 hubs. The registry table holds 208 vendor profiles: 58 verified and 150 unverified.
150 profiles are unverified: not checked against public sources. Attributes for unverified profiles come from the vendor file and may be incomplete or out of date.
Claim records
| Vendor | Hub | Migration task | Evidence kind | Claim | Limitation | Source | Checked |
|---|---|---|---|---|---|---|---|
| Accenture | Legacy Application Modernization | Monolith decomposition | Technology partner’s case study | vFunction reports that a US federal agency, working with Accenture and vFunction's platform, decomposed one monolithic Java application and extracted one service, and plans to reuse the method on 100+ Java applications. | Published by vFunction, the tool vendor, not by the agency or Accenture. The agency is unnamed, Accenture's role is not defined and no Accenture-specific outcome is given; the 10X and 33-hour figures are vFunction's self-reported numbers; only one service had been extracted at publication; undated. | US federal agency uses vFunction to successfully modernize apps for cloud mandate | 2026-11-12 |
| Accenture | Legacy Application Modernization | Application portfolio modernization | Official capability documentation | Accenture's AWS business group reports piloting AWS App2Container across multiple customers to containerize a legacy Java and .NET application portfolio with minimal remediation. | The scenario is explicitly a composite of several customer pilots, not a named or single client delivery; it is containerization (replatform), not a re-architecture of the code; the page says re-architecting can follow later at the customer's pace; no metrics beyond general statements. | Automating Containerization at Scale with AWS App2Container | 2026-11-12 |
| Arkency | Legacy Application Modernization | Ruby/Rails upgrades | Official capability documentation | Arkency describes a Rails upgrade service that analyses the repository, prepares two upgrade plans, and works in small iterations that it says succeed even with minimal test coverage. | Service description with an illustrative upgrade sequence, not a named customer upgrade. The zero-downtime and test-coverage claims are the supplier's own and no customer, duration or measured result is given. | Ruby on Rails Upgrade Services (Zero Downtime) | 2026-10-07 |
| Astadia | Mainframe Modernization | Replatform Unisys COBOL | Supplier-reported case study | Astadia reports replatforming the City of Miami dispatch system by converting Unisys COBOL to Micro Focus COBOL and moving DMSII data to SQL Server. | Supplier-published historical case with no explicit publication date; it demonstrates COBOL replatforming, not conversion to C# or deployment to Azure. | The City of Miami | 2026-10-07 |
| Astadia | Mainframe Modernization | Transform mainframe code | Official capability documentation | Astadia describes FastTrack tools for code transformation, data conversion, testing and DevOps, with Java and C# among the documented targets. | Capability description; it provides no customer-specific functional-equivalence percentage or guaranteed automation rate. | Astadia - The Migration Factory | 2026-10-07 |
| AWS Mainframe Modernization | Mainframe Modernization | Replatform or refactor to AWS | Official capability documentation | AWS documents replatforming with Rocket Software to preserve application language and artifacts, and refactoring with AWS Transform to produce a Java-based application stack. | Capability documentation, not customer delivery evidence; both classic managed and self-managed experiences are closed to new customers. | What is AWS Mainframe Modernization? | 2026-10-01 |
| AWS Mainframe Modernization | Mainframe Modernization | Check AWS onboarding eligibility | Official capability documentation | AWS records new-customer closure from 7 November 2025 for the managed experience and 30 July 2026 for the self-managed experience; existing customers may continue using them. | Closure dates differ from announcement dates; buyers must assess current alternatives rather than assume a new account can use these experiences. | Document history for the AWS Mainframe Modernization User Guide | 2026-10-01 |
| BigBinary | Legacy Application Modernization | Ruby/Rails upgrades | Official capability documentation | BigBinary says it has upgraded many Rails applications over 14 years and brought them to the latest version of Ruby on Rails. | Service description that names no customer, starting version, method or measured result. | Ruby on Rails upgrades | 2026-10-07 |
| Capgemini | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | Capgemini reports it has spent two years on service decomposition of legacy applications and detailed design of microservices for an unnamed Hungarian insurer's sales and product-lifecycle processes. | Supplier-hosted account for an unnamed client; undated on the page; the legacy language and platform are not stated; benefits are written as future ('will benefit'), with no delivery metrics; the page does not say Capgemini built the back-end services, only that it designed them. | Modernization of sales processes and improving customer experience for Hungarian insurer | 2026-11-12 |
| Capgemini | Legacy Application Modernization | Java version upgrades | Supplier-reported case study | Capgemini reports that its project team upgraded a global multi-brand restaurant company's platform domain services from JDK 11 to JDK 21, which it says improved performance, security and resource utilization. | Client unnamed; undated on the page; the JDK upgrade is one item in a wider platform overhaul, so no upgrade-specific effort, timing or tooling is given; benefits are self-reported for the whole programme. JDK 11 is not a legacy Java EE runtime, so this is a version upgrade, not a Java EE migration. | Stabilizing and upgrading a restaurant’s platform to meet future demands | 2026-11-12 |
| Cognizant | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | Cognizant reports that it re-architected the manufacturing customer's applications from a monolith to cloud-native microservices on AWS EKS and automated testing and deployment through DevOps pipelines. | Cognizant-published (AWS-branded, 'AWS + Cognizant solution') customer story, not confirmed by the customer. Customer unnamed; no dates, scale, application count, source language or quantified results; outcomes are qualitative. The start state is only called 'monolithic', so it is not shown to be Java. | Modernizing legacy applications for a leading manufacturing customer | 2026-11-12 |
| Evil Martians | Legacy Application Modernization | Ruby/Rails upgrades | Supplier-reported case study | Evil Martians reports that during a refactoring engagement of more than a year with Fund That Flip it upgraded the application to Ruby on Rails 6 and the latest stable Ruby version. | The upgrade is one sentence inside a broader refactoring and performance case; no starting version, upgrade method or duration is given, and the reported test-time and query-speed results are not attributed to the upgrade. Supplier's own account. | Big refactoring: Fix that app for Fund That Flip | 2026-11-12 |
| FastRuby.io | Legacy Application Modernization | Ruby/Rails upgrades | Supplier-reported case study | FastRuby reports that OmbuLabs worked with Procore on its Rails 5.0-to-5.1 upgrade, starting with issues on an existing Rails 5.1 branch. | Supplier-hosted account with a named client executive testimonial, not independently published customer confirmation. The 2020 case does not establish current delivery capability for later Rails versions. | Upgrading a Large Rails App From 5.0 to 5.1 | 2026-10-07 |
| FastRuby.io | Legacy Application Modernization | Ruby/Rails upgrades | Supplier-reported case study | FastRuby reports upgrading the Irish Chess Union's Rails application from 7.0 to 8.1 one minor version at a time using dual-booting with the next_rails gem, with the ICU webmaster quoted on the outcome. | Supplier-hosted account with a named client quote, not independently published customer confirmation. The client is a volunteer-run association with a small, conventional codebase, so it says little about large enterprise applications. | Irish Chess Union Upgrades to Rails 8.1 | 2026-10-07 |
| FastRuby.io | Legacy Application Modernization | Ruby/Rails upgrades | Official capability documentation | FastRuby offers Ruby and Rails upgrades and an application-specific roadmap that assesses dependencies and estimates effort per minor version jump. | Current service claim, not proof of a delivered upgrade to any particular version. Target versions and effort depend on the application assessment. | From technical debt to technical health | 2026-10-07 |
| HCLTech | Legacy Application Modernization | Java version upgrades | Official capability documentation | HCLTech reports a proof of concept in which AWS Q Developer upgraded the two applications to Java 21 in about 3.7 hours (KomiBank) and about 12 hours (Plasma, with manual fallback), tool runtime only. | A blog post by an HCLTech lead consultant describing a PoC, not a client delivery; applications are not tied to a named or described client. Timings exclude manual work; the post says transformation errors, hallucinated documentation and manual validation were needed. | Modernizing Java applications with AWS Q Developer: A journey from legacy to AI-powered development | 2026-11-12 |
| HCLTech | Legacy Application Modernization | Application portfolio modernization | Supplier-reported case study | HCLTech reports that its AI Force platform automated C++-to-Java conversion and test generation in a pilot for the client, with a productivity gain close to the 30-40% target, and that the client intends to proceed with the remaining applications. | HCLTech-authored case study; client unnamed and only the pilot phase is reported. Productivity figure is a self-reported estimate range. The output is described as needing customization. A language conversion of an application estate rather than a monolith or Java EE move. | Faster and efficient application migration and maintenance through HCLTech's AI Force | 2026-11-12 |
| Heirloom Computing | Mainframe Modernization | Replatform CICS COBOL to Java on AWS | Supplier-reported case study | AWS, Cognizant and Heirloom's CEO report that Venerable's agent-management application was replatformed to Java on AWS using Heirloom's compiler-based tooling in 16 months, in production since June 2020, with a quote from Venerable's CIO. | Published July 2021 on the AWS Partner Network blog and co-authored by Heirloom's CEO, so it is not independent of the supplier; the cost and schedule figures are the authors' own. | How Venerable Accelerated Growth by Modernizing its Mainframes on AWS | 2026-11-06 |
| IBM Consulting | Mainframe Modernization | Modernize on IBM Z | Official capability documentation | IBM Consulting describes services to modernize applications on z/OS and Linux for IBM Z, alongside services to migrate workloads to cloud or distributed platforms. | Service description; it does not identify a completed customer migration or establish a preferred platform for every workload. | End-to-end mainframe application modernization | 2026-10-07 |
| IBM Consulting | Mainframe Modernization | Enable mainframe API integration | Supplier-reported case study | IBM reports that BCC Iccrea connected existing core banking applications to external services using z/OS Connect while retaining IBM Z. | IBM-hosted customer story; this is API integration on IBM Z, not evidence of a mainframe exit or code conversion. | Seamless mainframe integration unlocks new opportunities | 2026-10-07 |
| IBM Consulting | Legacy Application Modernization | Application portfolio modernization | Technology partner’s case study | CAST reports that IBM Consulting used CAST Imaging output to ground AI agents for discovery, impact analysis and modernization planning on the manufacturer's large Java estate, with IBM-reported figures of up to 70% less documentation time and about 60% less impact-analysis time. | Published by CAST, the tool vendor, not by IBM or the client. Client unnamed. It documents analysis and planning, not completed refactoring or a cutover. The metrics are IBM-reported via CAST. Page undated. | IBM Consulting demystifies application modernization by grounding AI agents | 2026-11-12 |
| IBM Consulting | Legacy Application Modernization | Application portfolio modernization | Official capability documentation | IBM states that its application modernization services, powered by IBM Consulting Advantage for Cloud Transformation, determine a strategy per application portfolio using rehosting, refactoring, replatforming, rearchitecting, replacing or incremental enhancement, with generative AI for code refactoring. | IBM's own service page; it proves an offer, not delivery. No client, language or Java-specific claim. Mainframe modernization is listed on the same page but is outside this hub. | Application modernization services | 2026-11-12 |
| IBM watsonx Code Assistant for Z | Mainframe Modernization | Assist COBOL-to-Java transformation | Official capability documentation | IBM documents COBOL-to-Java transformation and generated unit tests comparing the Java service with the original COBOL; PL/I support includes analysis, explanation and refactoring. | Product capability description, not proof of a completed customer conversion; PL/I refactoring should not be read as documented PL/I-to-Java transformation. | IBM watsonx Code Assistant for Z | 2026-10-07 |
| IBM watsonx Code Assistant for Z | Mainframe Modernization | Understand COBOL before platform decisions | Supplier-reported case study | IBM reports that NOSI piloted the product on two COBOL applications for comprehension and documentation, then chose to modernize on IBM Z rather than exit the platform. | IBM-hosted customer story; it does not document production COBOL-to-Java conversion or an independent verification of the reported productivity gains. | Modernizing with IBM Z and watsonx Code Assistant for Z | 2026-10-07 |
| Infosys | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | Infosys reports re-architecting a US telecom provider's order orchestration platform into microservices on Amazon EKS, with a BPM solution, Spring Boot microservices and event-driven messaging. | Supplier-hosted case study for an unnamed client; undated; mixed case (mainframe components also involved, and the page does not say how the work split between them and Java); throughput, 99.99% availability and vulnerability figures are Infosys's self-reported numbers. | US Telco Modernizes Order Orchestration Platform from legacy Java and Mainframes to cloud-native microservices architecture | 2026-11-12 |
| Infosys | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | Infosys reports modernizing a US utility's monolithic on-premises applications into cloud-native microservices on AWS while keeping integration with existing mainframe, Oracle and DB2 systems. | Supplier-hosted case study for an unnamed client; undated; the source language is not stated; percentage gains (time to market, performance, downtime) are Infosys self-reported figures. | US Utility Cloud Transformation | 2026-11-12 |
| Infosys | Legacy Application Modernization | Java version upgrades | Supplier-reported case study | Infosys reports a pilot for an automotive manufacturer in which it used Anthropic Claude Code to modernize an application from JDK 11 through JDK 17 to JDK 21 with Spring 6 and remove its legacy workflow engine, with engineers responsible for review and validation. | Client unnamed; undated on the page; a pilot on a single application; the starting Spring version is not given; vulnerability, quality-issue, test-coverage and effort figures are Infosys's own. | AI-assisted Legacy Modernization for a Leading Automotive Manufacturer | 2026-11-12 |
| Kirschbaum | Legacy Application Modernization | Laravel development for legacy applications | Supplier-reported case study | Kirschbaum reports that it embedded senior PHP/Laravel engineers who modernized an unnamed subscription ecommerce company's application architecture, refactored core APIs, fixed security vulnerabilities and introduced automated testing. | Client unnamed; undated on the page; the starting stack is not stated, so it may already have been Laravel; no scope, duration or measured result. It describes modernization and refactoring, not a framework conversion. | Case Study: Modernizing an ecommerce Platform | 2026-11-12 |
| Kirschbaum | Legacy Application Modernization | Laravel development for legacy applications | Official capability documentation | Kirschbaum lists migrations and upgrades among its Laravel services, and modernization described as refactoring, audits and performance tuning for legacy systems. | Service description; it does not offer PHP-to-Laravel conversion by name, name starting frameworks or versions, or cite a client. | Laravel Development Services | 2026-11-12 |
| Nearform | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | Nearform reports that, after a three-day architecture workshop, it removed HTML rendering from Treedom's monolith and added a Node.js/Fastify BFF, with throughput up fourfold and deployments moving from weekly to several per day (Treedom's IT head is quoted on the deployment change). | Supplier-hosted page, though it names the customer and quotes Treedom's Head of IT. The work moved presentation out of the monolith rather than splitting the monolith into domain services; the monolith's language and size are not stated. Figures (400% throughput, 79% faster load, 1/10th latency) are Nearform's self-reported numbers. Page undated. | Combating climate change by helping a B Corp plant millions of trees | 2026-11-12 |
| OpenRewrite | Legacy Application Modernization | Java version upgrades | Official capability documentation | The guide documents recipes for selected API, dependency and build changes when upgrading Java 8 applications to Java 17. | Capability documentation, not a customer delivery record. The guide requires manual fixes for uncovered changes; compiled migration recipes are restricted to Moderne customers, with local compilation permitted for non-commercial use. | Migrate to Java 17 | 2026-10-01 |
| Persistent Systems | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | Persistent reports migrating a biotechnology client's monolithic Rails application to Python and Node.js microservices with its WingMate accelerators, and states an estimated 30% FTE time and cost saving. | Client unnamed; no visible publish date; the 30% figure is a self-reported estimate; scale (code size, number of services, duration) not stated; hosted on the supplier's own site. | Modernization of a Legacy App for a Global Biotechnology Firm | 2026-11-12 |
| Planet Argon | Legacy Application Modernization | Ruby/Rails upgrades | Supplier-reported case study | Planet Argon reports upgrading an unnamed client's Rails 5.2 application in phases to Rails 7.1, with Ruby moving from 2.6 to 3.2, while the app stayed online. | Anonymised, supplier-published account with no customer name, publication date, duration or independent confirmation. The Rails 8 step is described as a path, not a completed upgrade. | A Rails 8 Upgrade Story: Building Momentum Without a Rewrite | 2026-10-07 |
| Planet Argon | Legacy Application Modernization | Ruby/Rails upgrades | Official capability documentation | Planet Argon offers a full-service Rails upgrade and says it has completed dozens of upgrades of mature Rails applications. | Service description; no customer, version path or measured result is named, and the dozens-of-upgrades figure is the supplier's own. | Modernize Your Rails App | 2026-10-07 |
| Reinteractive | Legacy Application Modernization | Ruby/Rails upgrades | Official capability documentation | reinteractive describes an upgrade process that starts from the Gemfile, Gemfile.lock and rake stats output, gives a time and cost estimate, then upgrades Ruby and Rails and tests in staging before production rollout. | Service description with no named customer, version path or measured result. The all-versions claim is the supplier's own. | Ruby on Rails Version Upgrade Service | 2026-10-07 |
| Reinteractive | Legacy Application Modernization | Ruby/Rails upgrades | Supplier-reported case study | reinteractive reports upgrading three UCAR applications over several months, from Ruby 1.9 and Rails 3.1 at the oldest to the latest stable versions, finishing ahead of schedule and budget according to a UCAR engineer. | Supplier-hosted case with named UCAR quotes, not independently published. The page shows no date and does not give the target version numbers or the cost. | UCAR's Mission Critical Rails Upgrade | 2026-10-07 |
| Saeloun | Legacy Application Modernization | Ruby/Rails upgrades | Official capability documentation | Saeloun says it moves older Ruby and Rails versions to supported releases with deprecation cleanup, test stabilization, dependency upgrades and production rollout planning. | Service description. The only case study linked on the page, Haulhub, is a new e-ticketing build, so no customer upgrade is documented. | Ruby on Rails Upgrade Services | Rails 3 to Rails 8 | 2026-10-07 |
| Scalo | Legacy Application Modernization | Rebuild legacy .NET application | Supplier-reported case study | Scalo reports that its engineers worked alongside Wolters Kluwer on a new, cloud-first version of a legacy legal-software product, citing lower maintenance costs and a simplified architecture. | Supplier-published account with no dates, project size or measured results, and no independent confirmation; the legacy technology and the migration method are not disclosed. | Advancing law practice operations with a cloud-first modernization | 2026-10-07 |
| ScienceSoft | Legacy Application Modernization | Incremental .NET modernization | Supplier-reported case study | ScienceSoft reports replacing inventory and shipping module front ends with React while temporarily retaining the old back end, and assisting with separate .NET and Azure microservices. | Supplier report for an unnamed client, without independent confirmation. It describes selected modules and retained legacy components rather than a completed replacement of the whole application; the page says the collaboration began in 2019 and was continuing in January 2024. | Modernization of a Supply Chain SaaS Product Used by 3,000 Businesses Worldwide | 2026-10-07 |
| Slalom | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | Slalom reports that it assessed the legacy platform, broke down its monolith data flows and rewrote them as a microservices stack for a multinational retailer's business unit. | Slalom-authored insight article, not a customer-published account. Client unnamed (multinational retailer); no metrics, system size, languages, timeline or outcome measures given. The article does not say which language or framework the monolith used. | The right way to transition from a legacy platform to a modern application | 2026-11-12 |
| Slalom | Legacy Application Modernization | Application portfolio modernization | Official capability documentation | Slalom states on its service page that it modernizes application portfolios and selectively untangles monoliths, applying AI and agent-based tools to understanding legacy code, testing and refactoring. | Service page, so it shows an offer rather than delivery. Customer results quoted on the page (for example a 60% cut in refactoring time for a global technology leader) are unnamed, self-reported and not tied to a specific application type; they also span mainframe and data work. | Legacy modernization services | 2026-11-12 |
| SoftServe | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | SoftServe reports that a global financial institution's equities platform was moved from an internal data center to AWS and split into independent microservices, cutting calibration time by up to 90%. | Client unnamed; implementation language/stack of the legacy system not stated; no visible publish date; metrics are supplier-reported; page does not detail what SoftServe built versus the client. | How Modernization Helped a Financial Institution Cut Trade Latency by 90% | 2026-11-12 |
| SoftServe | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | SoftServe reports it migrated a client's payroll web application from an ASP.NET monolith to microservices on .NET Core and Go, moved it from Azure to AWS, and took part in the microservices design. | Client unnamed (a care-services marketplace); .NET stack, so partly overlaps the out-of-scope .NET area, though the substance is monolith-to-microservices; undated and the work appears older (.NET Core 2.0 era); no outcome figures tied to the decomposition itself. | Next Gen Micro Services Solution for Payroll Processing Application | 2026-11-12 |
| Spatie | Legacy Application Modernization | Laravel development for legacy applications | Official capability documentation | Spatie says its web development service accommodates legacy applications and builds Laravel codebases with automated tests. | Service description, not a documented PHP-to-Laravel migration or version upgrade. No customer, starting framework, migration sequence or measured result is given. | Web development | 2026-10-01 |
| TCS | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | TCS reports re-architecting a European bank's Java applications from EC2 into microservices, with Kafka on EKS, Terraform-built AWS accounts and automated DevSecOps pipelines. | Supplier-hosted case study for an unnamed bank; undated; the word monolith is not used (the page says 'legacy architecture'); no quantified outcomes; the page's headline is security and digital channels, and it is not clear how large the application estate was. | European bank secures banking services, goes digital | 2026-11-12 |
| TCS | Legacy Application Modernization | Java version upgrades | Official capability documentation | TCS lists a Java Modernization Toolkit on AWS Marketplace that offers automated discovery and dependency analysis, Java runtime and library upgrades for low-change applications, and re-architecting monoliths into microservices. | Product/offer listing, not a delivery record; no client, scale or outcome is named; undated on the page; listing contents are TCS-authored. | TCS Java Modernization Toolkit on AWS | 2026-11-12 |
| thoughtbot | Legacy Application Modernization | Ruby/Rails upgrades | Supplier-reported case study | thoughtbot reports that one of the first items it tackled for SumOfUs was upgrading the existing Rails application to a modern version of Ruby and Rails, reviewing the codebase for optimizations as part of that work. | Supplier's own account; undated; no Ruby or Rails version numbers, duration or measured result; the upgrade is one of several workstreams (CI/CD, team process). | Leveraging DevOps to optimize a Rails application and level up a team | 2026-11-12 |
| thoughtbot | Legacy Application Modernization | Ruby/Rails upgrades | Official capability documentation | thoughtbot lists Rails Upgrades as a service, alongside code audits and a part-time support and maintenance team, and says it has done hundreds of upgrades through the years. | Service description with no named client, version path or date; the hundreds-of-upgrades figure is the supplier's own. | Ruby on Rails Development and Consulting Services | 2026-11-12 |
| Thoughtworks | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | Thoughtworks reports working with a financial services company to replace a monolithic mainframe payments platform with AWS-hosted microservices and redesign its data models and workflows. | Supplier report for an unnamed client, without independent confirmation. It does not disclose a cutover sequence or establish that the project used the Strangler Fig pattern. | Fortune 500 financial services organization | 2026-10-07 |
| Thoughtworks | Legacy Application Modernization | Decommission legacy PHP monolith | Supplier-reported case study | Thoughtworks reports extracting features from Docebo's legacy PHP 7 monolith into a new microservices architecture on AWS, with a quoted Docebo executive and vendor-reported gains in database response time and throughput. | Supplier-hosted account with a named client executive's quote, not independently published customer confirmation; undated, and the performance figures are for specific queries and workloads. | Docebo: decommissioning legacy services to create a streamlined, scalable platform foundation | 2026-10-07 |
| Tighten | Legacy Application Modernization | Convert legacy PHP to Laravel | Official capability documentation | Tighten says its codebase upgrade service can convert a legacy PHP app to modern Laravel and Vue, and lists Laravel upgrades and tech stack modernization among its disciplines. | Service description aimed at small and mid-sized clients. No named PHP-to-Laravel conversion, starting framework, duration or result is given; a client quote from Blue Zebra Sports says its app was modernized front to back but does not state the starting stack. | Codebase Upgrades | 2026-10-07 |
| vFunction | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | vFunction reports Trend Micro used its platform to untangle circular dependencies and extract the Heartbeat service in under 3 months versus about a year for a comparable manual project, with deployment time cut from 24 hours to 1 hour. | Hosted by the vendor, no independent confirmation from Trend Micro; figures (4X, 12X deployment speed, 90% deployment-time decrease) are vendor-reported; only one service extracted, the rest of the suite remained monolithic; no visible publish date. | Trend Micro uses vFunction to refactor critical monolith for AWS | 2026-11-12 |
| vFunction | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | vFunction reports Intesa Sanpaolo converted its FVCB0 monolith into microservices (import, download and flow management) using the platform, with WebLogic licence reduction, over four months saved per application and a 3x increase in release frequency. | Vendor-hosted, no independent confirmation from Intesa; metrics are vendor-reported; one named application converted, 'a dozen applications' only mentioned for tooling; no visible publish date; compatibility tests for public cloud described as underway. | Intesa Sanpaolo transforms monoliths into microservices | 2026-11-12 |
| Wipro | Legacy Application Modernization | Monolith decomposition | Technology partner’s case study | vFunction reports that Correla engaged vFunction and Wipro to modernise the Gemini Java monolith, with Wipro and Correla architects refining service boundaries and one microservice extracted and deployed on Azure. | Published by vFunction, the tool vendor and a Wipro partner, not by Correla, National Grid or Wipro. Undated; scope is analysis plus the first microservice, with the full migration described as future; the 10-day analysis figure is vFunction's self-reported number. | Correla chooses vFunction and Wipro to modernise application | 2026-11-12 |
| Wipro | Legacy Application Modernization | Monolith decomposition | Supplier-reported case study | Wipro reports helping a financial-data and infrastructure provider break down a monolithic system into microservices and deliver containerized applications on Google Cloud, cutting customer onboarding from six months to hours. | Supplier-hosted PDF for an unnamed client; undated; source language not stated; the onboarding-time reduction is Wipro's self-reported figure. | A global data company reinvents its business model through app modernization | 2026-11-12 |
Downloads
Files are generated from the vendor files at build time and always match this page.
- Claim records (CSV) — One row per claim.
- Registry attributes (CSV) — One row per vendor profile, with verification status.
- Both tables (JSON) — Metadata, field dictionary and both tables in one file.
Field dictionary
Column names are identical in the CSV and JSON files.
/data/modernization-vendor-evidence.csv 55 records
| Field | Type | Description |
|---|---|---|
vendor_slug | string | Vendor identifier. It is the path of the vendor profile on this site and the join key to the registry table. |
vendor_name | string | Vendor name as written in the vendor file. |
hub_slug | string | Hub the claim is scoped to, as used in the hub URL. |
hub_name | string | Display name of that hub. |
task | string | Migration task the source evidence supports. |
claim | string | What the source says the supplier did or documents, in our words. |
evidence_kind | enum | One of supplier-case-study, partner-case-study (published by a technology partner in the engagement), customer-confirmation, official-capability or editorial-interpretation. |
source_system | string | Starting system named by the source. |
target_system | string | Target system named by the source. |
supplier_role | string | What the supplier is recorded as responsible for in this source. |
limitation | string | What the source does not establish. |
source_url | url | Public page that was checked. |
source_title | string | Title of that page or case. |
source_published_date | date | Date the source states it was published or updated, in YYYY-MM-DD. Empty when the source states none. |
checked_date | date | Date we last opened the source, in YYYY-MM-DD. |
/data/modernization-vendor-evidence-registry.csv 208 records
| Field | Type | Description |
|---|---|---|
vendor_slug | string | Vendor identifier and the join key to the claims table. |
vendor_name | string | Vendor name as written in the vendor file. |
vendor_type | enum | Agency (delivery firm), Platform or SaaS (product), as stated in the vendor file. Empty when not stated. |
website_domain | string | Domain of the vendor’s own website. |
location | string | Location text from the vendor file. It is not normalised and may name a headquarters, a region or both. |
team_size_band | enum | Boutique, Mid-size or Enterprise, as recorded. Empty when not recorded. |
hubs | string | Hub slugs for which the file holds a hub-scoped profile, separated by semicolons. |
verification_status | enum | verified when the file records a last-verified date, otherwise unverified. Unverified profiles have not been checked against public sources. |
last_verified | date | Date the profile was last verified, in YYYY-MM-DD. Empty for unverified profiles. |
confidence | enum | high, medium or low: our rating of how well public sources support the profile. Empty when not recorded. |
checked_source_count | integer | Number of public sources in the file that carry a checked date. |
claim_record_count | integer | Number of those sources that have a record in the claims table. |
Inclusion rules
- Claim records: one record per public source in a vendor file that has a checked date and a scoped comparison (hub, task, evidence kind, source and target system, claim, supplier role and limitation). A source recorded only as a provenance link, without a scoped claim, is counted in checked_source_count but has no claim record.
- Registry attributes: one row per vendor file in the registry at the time of the build. Presence in the registry is not an endorsement. A field is published only when the vendor file records it; an empty cell means not recorded.
- Verification: a profile is verified when its file records a last-verified date, and unverified otherwise. Confidence (high, medium or low) is our rating of how well public sources support the profile.
- Excluded: pricing, rates, contract terms, customer lists and any commercial relationship data such as listing tier, status, ownership, affiliate links or paid placement. The dataset contains no such fields.
Version
Version 1.1.0. Data as of 2026-11-12. The version number describes the published fields. The data-as-of date is the newest verification or check date in the records and moves as vendor files are checked.
License
This dataset is released under CC BY 4.0. You may copy, adapt and redistribute it, including commercially, if you credit Software Modernization Intelligence and link to this page. Linked sources remain the property of their publishers; the dataset links to them and records our description of them.
How to cite
Cite the dataset page, the version and the data-as-of date together:
Software Modernization Intelligence. Modernization Vendor Evidence Dataset, version 1.1.0, data as of 2026-11-12. https://softwaremodernizationservices.com/data/modernization-vendor-evidence/. Licensed under CC BY 4.0.
Methodology
How we collect, check and label evidence is described on the Methodology page.