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

Faster Claims Batches During Replatforming

By TechSupport Team. Published November 16, 2026. Updated .

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.

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

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

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Batch runtime5.2 h48 minBaseline: h; Result: min8 monthsClient Azure DevOps
Unplanned downtime0 h0 hh8 monthsClient status page; Scope: Scheduled maintenance was excluded.
Infra cost—-22%Result: %8 monthsClient 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 or explore software maintenance.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.