# Faster Claims Batches During Replatforming

> TechSupport Team supported Harborline’s migration from WebLogic and Oracle to Spring Boot and PostgreSQL. Over eight months, client Azure DevOps records show batch runtime falling from 5.2 hours to 48 minutes.

- Publisher: TechSupport Team
- Canonical page: https://techsupport-team.com/case-studies/insurance-claims-java-replatforming/
- Updated: 2026-11-16

Client: Harborline · DevOps, SRE & Cloud · US insurance software provider (240 staff)

## Client and engagement facts

- **Client:** Harborline
- **Industry:** DevOps, SRE & Cloud
- **Business context:** US insurance software provider (240 staff)
- **Delivery model:** Replatforming support
- **Application:** Insurance claims platform on legacy Java
- **Supplied geography:** US
- **Company size in source:** 240 staff

## Application stack and tools

### Application stack

- Java 8→17
- WebLogic→Spring Boot
- Oracle→PostgreSQL
- Azure

### Tools used

- Azure DevOps
- Datadog
- Azure billing
- client status page

Related services: [Software maintenance](https://techsupport-team.com/services/software-maintenance/)

## Why Support Was Needed

The client required continuity during the migration and retained change control. The team moved batch, API and web workloads in waves with two-week observation periods.

## Technical Work

- Migrated batch, then API, then web tier, in waves with soak periods.
- Rewrote each EJB as a Spring Boot service.
- Added the missing Oracle index as the equivalent PostgreSQL index.

## Representative Incident

A missing equivalent database index caused one batch to overrun by 40 minutes in month five. The team added the index and reran the job that day. Customer-facing systems kept running.

## Results and how they were measured

Table: Reported results and their measurement scope

| Metric | Baseline | Result | Units | Measurement window | Source and scope |
| --- | --- | --- | --- | --- | --- |
| Batch runtime | 5.2 h | 48 min | Baseline: h; Result: min | 8 months | Client Azure DevOps |
| Unplanned downtime | 0 h | 0 h | h | 8 months | Client status page; Scope: Scheduled maintenance was excluded. |
| Infra cost | — | -22% | Result: % | 8 months | Client Azure |

## Evidence and Limitations

The client status page recorded zero unplanned downtime at both comparison points. Scheduled maintenance was excluded. Infrastructure cost is reported as a relative change.

## Availability and Change Control

The migration moved in waves with two-week observation periods. Harborline owned change control.

## Scope a Similar Engagement

Share the parts of your application that must remain available during a runtime or database migration. [Request a support plan](https://techsupport-team.com/contact/) or explore [software maintenance](https://techsupport-team.com/services/software-maintenance/).

## Related pages

- [Software maintenance](https://techsupport-team.com/services/software-maintenance/): The related service for this engagement.

## Contact

Request engineers from TechSupport Team or ask a question: https://techsupport-team.com/contact/
