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
27 claim records from 18 vendors across 2 hubs. The registry table holds 208 vendor profiles: 28 verified and 180 unverified.
180 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 |
|---|---|---|---|---|---|---|---|
| 10Clouds | Legacy Application Modernization | Replatform or re-architect on AWS | Official capability documentation | 10Clouds lists AWS lift-and-shift migration and re-architecting of legacy systems for AWS, with a cloud transition strategy and continuing support. | Service description with no customer, source technology, timeline or measured result. It is not a PHP-to-Laravel, .NET Framework or React-to-Next.js migration. | Seamless application migration to AWS | 2026-10-07 |
| 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. It does not mention React. | Ruby on Rails upgrades | 2026-10-07 |
| 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 |
| 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-10-07 |
| 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 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 |
| 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 |
| 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 |
| 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 |
| 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 |
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 27 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, 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 and changelog
Version 1.0.0. Data as of 2026-10-07. 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.
| Version | Date | Change |
|---|---|---|
| 1.0.0 | First release: claim records and registry attributes, with CSV and JSON downloads. |
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.0.0, data as of 2026-10-07. 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.