What challenges did The Hartford face before AI implementation?

Modernize a critical claims-processing application built on .NET Framework 4.8. Reduce Windows licensing dependencies and improve scalability, agility, and performance for claims workflows.

What was the impact of the AI solution?

AWS Transform for .NET transformed 30% of the codebase automatically, including 7,870 lines of code from .NET Framework 4.8 to .NET 8 within hours. The work reduced months of manual effort to weeks and laid the foundation for broader modernization.

Source

Evidence: Low35/100

The Hartford accelerates modernization of claims systems using AWS Transform for .NET

Use case typeCode modernizationUpdated May 15, 2025

The Hartford used AWS Transform for . NET to modernize its Skylynx Vendor Management application, a critical system for claims processing. The effort ported . NET Framework 4.8 code to . NET 8, transformed synchronous patterns to async/await, updated dependency injection patterns, and planned Amazon ECS hosting for the transformed application.

Organization: The Hartford
Industry: Insurance
Location: United States
Published: May 2025

Reported outcomes

7,870 lines

lines of code transformedTime & speed

+30%code transformed automatically

Strategic outcomes

Innovation & cultureReduced modernization effort from months to weeksCost efficiencyReduced dependency on Windows licensingScale & capacityImproved scalability and workload handling

Why do we believe this?Outcome claims, sources, and evidence checks

Normalized claim

Code transformed automatically: 30% increase

AWS BlogMay 15, 2025Blog postExplicit claimLow evidence strength

AWS Transform for .NET transformed 30% of the Vendor Management application’s codebase automatically

Normalized claim

Lines of code transformed: 7,870 lines increase

AWS BlogMay 15, 2025Blog postExplicit claimLow evidence strength

converting 7,870 lines of code from .NET Framework 4.8 to .NET 8 within hours

Why do we believe this deployment?Customer identity, provider attribution, maturity, and source checks

Customer: The Hartford
Provider: AWS
Maturity: Unknown
Linked source: AWS Blog

No explicit deployment-stage evidence found.

Customer identity supportedSource describes one deploymentMaturity evidence evaluated

Primary read

Use case focus

Showing 2 of 2

1Code modernization
2Infrastructure modernization

Modernize a critical claims-processing application built on .NET Framework 4.8.
Reduce Windows licensing dependencies and improve scalability, agility, and performance for claims workflows.

Used AWS Transform for .NET agentic AI to analyze the codebase, create a transformation plan, and automate code conversions.
Planned container deployment on Amazon ECS with supporting AWS services for scalability and availability.

Technologies

AWS Transform for .NET Amazon ECS Amazon Fargate Amazon Aurora AWS IAM Identity Center AWS Toolkit

AWS Transform for .NET transformed 30% of the codebase automatically, including 7,870 lines of code from .NET Framework 4.8 to .NET 8 within hours.
The work reduced months of manual effort to weeks and laid the foundation for broader modernization.

Architecture

The Hartford’s Vendor Management application uses a multi-tiered architecture with presentation, service, and data layers. AWS Transform for .NET automatically analyzed the .NET Framework 4.8 codebase, created transformation plans, updated NuGet packages, replaced deprecated APIs, and ported service and data layers to cross-platform .NET 8. The article also describes a planned containerized deployment on Amazon ECS with AWS Fargate, Amazon Aurora, and an Application Load Balancer across two Availability Zones.

Sources & evidence1

Evidence: Low35/100Evidence strength