Insurers

Data warehouse migration for insurers

Insurers carry decades of actuarial and reporting logic in stored procedures and ETL packages, and every number has an auditor. Novuz converts that logic by fixed rules inside your environment, reconciles every object against the original on the same inputs, and lets you move one domain first with the threshold written down. For SOX change-control evidence, see /for-audit.

The problem

Why do insurance warehouse migrations overrun?

Because the price was set before anyone counted the logic. Reserving, reporting and finance procedures, the packages that feed them and the schedules that run them are the hard part, not the terabytes. Count every object first, remove the dead code, and fix the price after the estate has been read.

Proof

How does Novuz prove a converted number matches?

Each original object and its converted version run on the same inputs. The report compares schema, row counts, column aggregates and sampled rows, marks the object pass, fail or review, and lists every miss by line. It proves equivalence on the tested inputs, not that the original was correct.

Evidence

What goes into the audit trail?

Evidence per change, for every object:

  • what each object became;
  • the rule version that converted it;
  • any resolver proposal, with the engineer who approved it;
  • a reconciliation report on the same inputs.

Novuz does not certify compliance; your own controls do. It produces the evidence per change, and your compliance team maps it to the requirements that apply to you.

How to start

How should an insurer start?

Move one domain first, in 5 to 6 weeks, with the reconciliation threshold written into the First Domain charter: 95% of in-scope objects by default. If it is missed at the readout, after the cure period and the charter’s exclusions, the fee is waived or credited in full.

Next question

Where to read next

For SOX change-control evidence, see the audit page.

FAQ

Frequently asked questions

Which legacy platforms can an insurer move with Novuz?

SQL Server (T-SQL), SSIS, Teradata including BTEQ, Hadoop (Hive, Impala) and Snowflake, to Databricks, Microsoft Fabric, Snowflake, Apache Iceberg or Delta Lake. Oracle, mainframe, Informatica, DataStage, Netezza and Redshift are not covered today.

How is the price set?

By a $3,000 estate assessment, delivered in three business days and credited in full. It counts and bands every object, lists the dead code and fixes the price before work starts.

Does Novuz certify regulatory compliance?

Novuz does not certify compliance; your own controls do. It produces the evidence per change, and your compliance team maps it to the requirements that apply to you.

Sources and further reading

How we measure: Methodology

Written by Debjani Dhar, Co-founder and CEO, Novuz · Technical review: Ted Ghose, Co-founder and CTO, Novuz

Last reviewed:

Find out what your logic debt is costing you.

Every object counted, lineage, dead code and a fixed price in three business days. $3,000, credited.

Take the logic debt scorecard

Not sure which door? The scorecard takes ten minutes and tells you.

Scorecard