Wellington BarbosaData engineering & software

An ETL pipeline that brought the data back in-house

The end of dependence on an outsourced legacy system.

The problem

A health insurer paid high monthly fees to a vendor just to keep access to information that was its own. The only way to get the data was to export spreadsheet reports one by one: more than 100 report types, produced by hand every month.

Overview

  1. Sources

    • Outsourced legacy system100+ report types
    • Management system (ERP)Reference records
  2. Extraction

    • Automatic extractionReplaces the monthly manual run
  3. Transformation

    • Cleaning and treatmentFixes errors, recovers the unreadable
    • Cross-reference with the ERPFills in what was missing
  4. Validation

    • Check against the sourceTotals and samples before release
  5. Destination

    • Company databaseOracle and PostgreSQL
    • Reports and dashboardsPower BI

OrchestrationA scheduler logs every run and works outside peak hours. When a business rule changes, it is fixed in one place only.

From manual reports to data in-house: each pipeline stage, from source to destination.

What I built

  • I owned the project end to end, from analyzing the source data to loading it into the company environment.
  • Automatic extraction: replaced the manual production of the 100+ monthly reports and made the process repeatable, with no human effort needed.
  • Cleaning and treatment: cross-referenced the legacy data with the management system to fix wrong information, recover unreadable records and enrich incomplete ones before loading.

Under the hood

Data checked before it is released

Every new load is validated by comparing totals and samples against the source. Only when they match does the data reach the people who will use it.

No strain on the production system

Extraction queries go through performance analysis and run outside peak hours, so nobody notices the pipeline working.

A process that repeats itself

A scheduler handles orchestration and logs every run. When a business rule changes, the fix is made in a single place.

The result

  • The data came under the control of the company, and the dependence on the vendor ended.
  • Estimated savings of R$ 2 million in contract fees.

Have a similar problem?

Tell me the scenario and I will say, no strings attached, where I would start.

Get in touch

See also

Back to the projects