Example journey. This page shows how we run this type of migration. It is not a named client result. References from comparable projects are available on request.
This example journey shows how we would move an insurer from IBM Netezza and DataStage to Databricks: catalogue and rank workloads, convert SQL and procedures, rebuild DataStage jobs as tested pipelines, reconcile actuarial and claims reports, then add claims document AI.
| Type | Example migration journey |
|---|---|
| Industry | Insurance |
| Migration | IBM |
| Technologies | LakeBridge, Lakeflow Declarative Pipelines, Agent Bricks, Unity Catalog |
Starting point
An insurer runs its warehouse on IBM Netezza with DataStage ETL. The appliance is reaching end of life, licences are costly, and adding claims document AI is not practical on the current stack.
How we would approach it
- Assess: catalogue Netezza objects and DataStage jobs, and rank them by business value.
- Convert: convert SQL and stored procedures, and rebuild DataStage jobs as tested declarative pipelines.
- Reconcile: validate actuarial and claims reports with finance and actuarial owners.
- Extend: once migrated, add claims document extraction with Agent Bricks on the same platform.
Value the insurer should expect
- Exit from appliance renewal and ETL licence costs.
- Pipelines as code, with version control and tests.
- A direct path to claims triage and document AI.
What to measure
Licence and infrastructure cost, job failure rates, time to change a pipeline, and claims-reporting freshness.
Read the full IBM Netezza, Db2 and DataStage to Databricks guide →
