Novuz

Learn

Conversion is not migration

Converted code is a draft until it runs in the target, runs on its schedule, gives the same numbers as the original and the old platform is switched off. Converters, rule-based or AI, finish the first step. A migration is finished when the business stops paying for two platforms.

6

Parts of a complete migration

Conversion is one of them

Every object

Reconciled on the same inputs

Before cutover

2 months

A 6-month program, closed early

Media analytics case study

$100,000+

Saved on parallel running

Same case study

The difference

What is the difference between conversion and migration?

Conversion translates code from one dialect to another. Migration moves a working system: the code, the schedules, the data and the proof, ending with the old platform switched off.

Conversion

The code is translated

  • One file or object at a time
  • Checked that it compiles and reads right
  • Schedules and dependencies left for later
  • No evidence the numbers match
  • Both platforms still running

Migration

The system is moved and proven

  • Every object, with its lineage
  • Runs in the target on its schedule
  • Reconciled against the original
  • Signed off with evidence
  • The old platform switched off

The six parts

What does a complete data warehouse migration include?

Six parts, in this order. A plan that prices only the second one is pricing a sixth of the work.

  1. 01

    Know the scope

    Inventory

    Count every object, find the dead code and map the lineage.

  2. 02

    The code

    Convert

    Translate tables, views, procedures, packages and scripts to the target.

  3. 03

    The schedules

    Rebuild orchestration

    Recreate the jobs, schedules and dependencies so it runs unattended.

  4. 04

    The data

    Move the data

    Load history and set up the incremental feeds.

  5. 05

    The proof

    Prove equivalence

    Run original and converted on the same inputs and compare, object by object.

  6. 06

    Done

    Cut over and switch off

    Move users, retire the old platform and stop paying for it.

Ready test

When is a migrated object ready?

Five tests. An object that fails any of them is converted, not migrated.

It runs in the target

It executes on the new platform, with no runtime from the old one.

It runs on schedule

Its job, dependencies and timing are rebuilt, so nobody starts it by hand.

It reconciles

On the same inputs it gives the same results as the original: schema, row counts, aggregates and sampled rows.

Someone signed it off

The owner of the numbers has read the evidence and accepted it.

The original is retired

Nothing still reads from the old object, and it can be switched off.

Where tools stop

Where do converters usually stop?

At the same four places, whichever converter ran first. They are the hardest work in the estate and the reason projects stall after a good first month.

Procedural logic

Stored procedures with cursors, dynamic SQL, error handling and control flow.

Packages and orchestration

SSIS packages, BTEQ control flow, SQL Agent jobs and the dependencies between them.

The data path

Loads, incremental feeds and the history the reports depend on.

Proof

Evidence, object by object, that the new platform gives the same numbers.

If the plan ends at “converted”, the bill does not.

Every object left unproven keeps the old platform running, and every month of that is paid twice.

With Novuz

How does Novuz finish the migration?

One engine for all six parts, inside your environment. A full estate includes 90 days of post-migration fixes, with parallel-run and cutover support and knowledge transfer.

  1. 01

    3-day assessment

    Discover

    Every object counted and banded, dead code found, lineage mapped.

  2. 02

    ~95% by rule

    Converge

    Fixed, versioned rules convert code and schedules to native target code.

  3. 03

    Engineer-approved

    Resolve

    The resolver proposes fixes for the edge cases; an engineer approves each one.

  4. 04

    Every object

    Validate

    Every object reconciled against the original on the same inputs.

  5. 05

    Your platform

    Deploy

    Code, schedules and pipelines live in your target, ready for cutover.

Questions to ask

What should we ask before we call a migration done?

  • What does “done” mean in the contract: converted, deployed, reconciled or switched off?
  • Which objects will the tool not convert, and who converts them, at what price?
  • Who rebuilds the schedules and dependencies?
  • How is equivalence proven, per object, and what does the auditor receive?
  • How long will both platforms run, and who pays for that time?

Next question

Where to read next

What will the whole migration cost, before it starts? The cost page shows how to get one number you can hold a vendor to.

FAQ

Frequently asked questions

Is code conversion the same as data warehouse migration?

No. Conversion translates code to the target dialect. Migration also rebuilds the schedules, moves the data, proves each object gives the same results and switches off the old platform. A migration is done when the business stops paying for two platforms.

Why do migrations stall after the code is converted?

Because the hard parts come after: procedures and packages the converter did not handle, schedules that must be rebuilt, and proof that the numbers match. Until those are done, both platforms keep running.

How do we shorten the time we pay for two platforms?

Prove objects as they are converted, not at the end, and cut over domain by domain. A media analytics company closed a program planned for six months in two, saving more than $100,000 on parallel running.

What does Novuz include after go-live?

A full estate includes 90 days of post-migration fixes, with parallel-run and cutover support and knowledge transfer. The converted code is native to your target, with no Novuz runtime in it.

How we measure: Methodology

Written by 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