Skip to content
QuorlyticTalk to a Data ExpertContact
Menu

Capability / Migration assessment

Fixed-Scope Data Warehouse Migration Assessment

A data warehouse migration assessment is a fixed-scope engagement that establishes what a legacy warehouse actually does before anyone commits to moving it. Quorlytic inventories objects and consumers from query logs and lineage, scores translation complexity, defines reconciliation and acceptance rules, and delivers a costed, phased migration plan with the evidence behind every estimate.

By QuorlyticUpdated

Most migration estimates are estimates of the easy half. The assessment exists to find the stored procedures nobody owns, the extracts nobody documented and the reports that will break, while changing course is still cheap.

Evidence

  • Query logsWho reads what
  • SchedulesWhat runs when
  • CatalogueWhat logic does
  • LineageWhere data flows

Disposition

  • MigrateMove as it is
  • RedesignRebuild on target
  • RetireNo reader, on evidence

Complexity score per workload

  1. SimpleSQL and views
  2. Moderatedialect and functions
  3. Complexprocedures and state
  • Costed, phased migration planWaves · cost per phase · rollback position

Agreed before anything moves — what must match, at what tolerance, signed off by whom

Migration assessment: query logs, job schedules, the catalogue and lineage feed a migrate, redesign or retire disposition and a complexity score per workload, which become a costed, phased plan with acceptance rules agreed in advance. A typical shape, not a client implementation.
01

The business problem

A migration estimated before its dependency set is known is a guess about the visible part of the estate. Query logs routinely reveal consumers the platform team has never met, and procedural logic routinely turns out to hold business rules nobody wrote down. The assessment converts those unknowns into a scoped, costed plan before budget is committed to the move.

02

What we build

The inventory is built from query history, job schedules, lineage and the warehouse catalogue rather than from interviews alone. Each object is classified as migrate, redesign or retire, and retirement is recommended only on evidence that nothing reads it.

03

The outcome

A costed, phased migration plan with the evidence behind each estimate

Assessment register

Every workload classified, scored and owned before the plan is written.

The assessment's working surface is a register: one row per workload, with the disposition the evidence supports, the complexity that drives its effort and the person who signs it off. The plan is built from this register, so every estimate can be traced back to a row.

Assessment register
  • Legacy warehouse estate
  • Disposition review
  • Owners named
Workloads in the assessment register, with their state, disposition, complexity driver and owner
WorkloadStateDispositionComplexity driverOwner
Finance reporting martsScoredMigrateProcedural logic in month-end jobsFinance data owner
Customer extractsOwner to confirmRedesignConsumers outside the platform teamCRM lead
Legacy sales historyEvidence attachedRetireNo reader in the measured periodSales operations
ETL mappingsBeing scoredMigrateWorkflow state and reject handlingIntegration lead
Access rolesDecision neededMigrateRow-level policies per regionSecurity owner
The access row needs a decision before the plan is final, so it is listed as an open decision with an owner, not buried in a footnote.

What it answers

  • Which objects does anyone actually read?
  • What makes this workload hard to move?
  • Who signs off that the new numbers are right?
Talk to a Data Expert about a migration assessment

When this is the right engagement

Symptoms that bring teams here.

These are the situations in which a migration assessment pays for itself. If none of them describe your estate, a direct migration plan may be enough.

  • The migration estimate came from an object count

    Tables are the easy half. The effort sits in procedural logic, extracts and consumers nobody listed.

  • A licence or support end date is driving the timeline

    The deadline is fixed, so the plan has to be built from evidence rather than optimism.

  • Nobody can say who reads the warehouse

    Without the consumer set from query logs, every cutover risks breaking a report someone depends on.

  • Stored procedures carry business rules nobody owns

    Undocumented logic is the largest single source of migration risk and the hardest to estimate.

  • The board wants a number before the project starts

    A defensible budget needs a complexity score per workload, not a figure from a vendor demonstration.

  • Two vendors gave estimates that differ wildly

    Each estimated a different scope. An assessment fixes the scope so estimates become comparable.

Capability model

What the assessment establishes.

The assessment answers five questions before any budget is committed to the move. Select one to see what it involves and what it produces.

01 — Inventory

Establish what the warehouse actually contains and who actually uses it, from query history rather than from documentation.

What it produces

An object and consumer inventory with a named owner per critical consumer.

Warehouse migration playbook

What usually goes wrong

  • Extracts and applications reading tables directly
  • Reports built outside the platform team
  • Objects nobody has read in a year still counted as scope

Technologies in this stage

  • Query log analysis
  • Job schedules
  • Catalogue metadata
  • Lineage

Reference architecture

How evidence becomes a plan

The assessment narrows a large, uncertain estate into a small number of decisions. Four kinds of evidence feed one disposition register, which feeds the scored, phased plan.

  1. Query history

    Who reads what, and how often.

    • Consumers
    • Read frequency
    • Unused objects
  2. Job schedules

    What runs, when, and in what order.

    • Dependencies
    • Run windows
    • Failure history
  3. Catalogue and code

    What the logic actually does.

    • Procedures
    • Views
    • ETL mappings
  4. Lineage and access

    Where data flows and who may see it.

    • Lineage
    • Roles
    • Row policies
  5. Disposition and score

    Every object classified and every workload scored.

    • Migrate
    • Redesign
    • Retire
    • Complexity
  6. Costed, phased plan

    Waves, effort, cost and rollback per phase, with acceptance rules attached.

    • Waves
    • Cost per phase
    • Acceptance rules
    • Open decisions

Agreed before anything moves

  • Acceptance thresholds
  • Data owners named
  • Target recommendation
  • Risk register
Reference flow: query logs, schedules, catalogue and lineage feed a disposition register and a complexity score, which produce acceptance rules and a costed, phased migration plan. It shows a typical shape for discussion, not a prescribed stack or a client implementation.

The approach

  1. 01

    Why an assessment comes before the migration

    A migration estimated before its dependency set is known is a guess about the visible part of the estate. Query logs routinely reveal consumers the platform team has never met, and procedural logic routinely turns out to hold business rules nobody wrote down. The assessment converts those unknowns into a scoped, costed plan before budget is committed to the move.

    The sequencing logic is set out in the warehouse migration playbook, and the delivery itself is described on the Snowflake migration services page.

  2. 02

    Discovery from evidence, not from documentation

    The inventory is built from query history, job schedules, lineage and the warehouse catalogue rather than from interviews alone. Each object is classified as migrate, redesign or retire, and retirement is recommended only on evidence that nothing reads it.

    • Consumers identified from query logs, including unknown ones
    • Objects classified as migrate, redesign or retire
    • Retirement backed by read history, not opinion
  3. 03

    Source-specific complexity is scored, not assumed

    Teradata, Oracle, Netezza, SQL Server and Informatica estates each fail in different places: procedural logic, proprietary functions, physical design assumptions, identity and sequence behaviour, and orchestration. The assessment scores each workload against the source's known translation problems so the estimate reflects the estate you actually run.

    Source-specific detail is published for Teradata, Oracle, Netezza, Informatica PowerCenter to dbt and Cloudera to Databricks.

  4. 04

    Acceptance is defined before anything moves

    The assessment writes down what has to match between the old and new platforms, at what tolerance, and who signs off, so the later cutover decision is judged against an agreed standard rather than debated under time pressure. Access roles, row-level policies and service identities are inventoried at the same time, because they are the part most often discovered late.

  5. 05

    The deliverable is a phased, costed migration plan

    The output is a phased migration plan: waves ordered by dependency and risk, the effort and cost behind each phase, the reconciliation approach, the rollback position and the open decisions that still need an owner.

    • Waves ordered by dependency and business risk
    • Cost and effort stated per phase, with assumptions
    • Open decisions listed with a named owner
  6. 06

    Who the assessment is for, and who it is not for

    It suits organisations with a legacy warehouse or ETL estate they intend to move, where the dependency set, the procedural logic or the reconciliation burden is not yet understood. It is not the right first step when the estate is small and well documented, or when the target platform has not yet been chosen; that choice belongs in a data and AI advisory engagement first.

Delivery model

How the work is sequenced.

Four steps, each ending in an artefact you keep, not a status update.

Delivery phases: what happens, what gets decided, and the artifact each phase leaves behind
PhaseActivitiesDecisions made hereWhat you keep
InventoryFind every object and every consumer.
  • Read query history, job schedules and the catalogue
  • Trace lineage to downstream reports and extracts
  • Identify objects with no reader in the measured period
  • Which consumers are business-critical
  • Who owns each critical reporting area
Object and consumer inventory
Score complexityMeasure how hard each workload is to move.
  • Classify objects as migrate, redesign or retire
  • Score procedural and dialect-specific logic per workload
  • Recommend the target architecture with the options considered
  • Disposition per object
  • The target recommendation
Disposition register and complexity scores
Define acceptanceDecide what proves the new platform is right.
  • Agree counts, aggregates, samples and business metrics to compare
  • Set the tolerances that block a cutover
  • Inventory roles, policies and service identities
  • Release thresholds
  • Who signs off each data product
Reconciliation and acceptance rules
Plan the wavesTurn evidence into an executable sequence.
  • Order waves by dependency and business risk
  • State effort, cost and assumptions per phase
  • Define the rollback position for each wave
  • Wave order
  • What is deferred or retired
Costed, phased migration plan

Technology fit

What each technology is here to do.

What the assessment reads, by role. The source platform decides most of the effort, so the assessment is always specific to it.

  • Source warehouses

    • Teradata
    • Oracle
    • Netezza
    • SQL Server
    • Redshift

    Procedural logic, proprietary functions and physical design assumptions drive the translation effort.

  • Source ETL

    • Informatica PowerCenter
    • Stored procedures
    • Scheduled scripts

    Orchestration and state handling are often the hidden half of a warehouse estate.

    Platform detail
  • Typical targets

    • Snowflake
    • Databricks
    • BigQuery
    • dbt

    The recommendation follows the workload, the team's skills and the cost model, and states the options set aside.

    Platform detail
  • Evidence

    • Query logs
    • Lineage
    • Catalogue metadata
    • Access logs

    Scope decided from what is actually used rather than from what people remember.

Technology marks belong to their respective owners. No partnership, certification or endorsement is implied.

Engineering concerns

What has to be answered before it is trusted.

What the assessment has to settle before a migration budget is defensible.

Scope from usage
Scope is set from query history, so objects nobody reads are retired on evidence rather than migrated by default.
Undocumented logic
Every stored procedure and ETL mapping in scope has an owner or a recorded decision about it.
Comparable estimates
Effort and cost are stated per phase with their assumptions, so any delivery estimate can be compared against the same scope.
Acceptance in advance
What must match, and at what tolerance, is agreed before anything moves, not argued at cutover.
Access parity
Roles, row-level policies and service identities are inventoried early, because they are the part most often found late.
Reversibility
Each wave has a stated rollback position, so the programme stays reversible until it deliberately is not.

What the assessment includes, and what it does not

Scope of the fixed-scope data warehouse migration assessment: what is included and what is explicitly excluded
DimensionIncludedNot included
InventoryObjects, jobs, stored procedures, extracts and downstream consumers, built from query logs and lineageMigrating any object or data
ComplexityA translation-complexity score per workload, with the source-specific behaviour that drives itRewriting or converting code
TargetA target architecture recommendation, with the options considered and why each was set asideBuying or provisioning the target platform
ReconciliationThe counts, aggregates, samples and business metrics that must match, and the thresholds that block a cutoverRunning the parallel period itself
PlanA phased migration plan with waves, dependencies, risks, a rollback approach and a cost estimate per phaseExecuting the migration waves

Questions

Questions worth asking.

What is a data warehouse migration assessment?

A fixed-scope engagement that maps what a legacy warehouse does, who depends on it and how hard each workload is to translate, then turns that into a costed, phased migration plan with reconciliation and acceptance rules. It happens before the migration is committed to, so the budget is set against evidence.

What does the assessment produce?

An object and consumer inventory built from query logs and lineage, a translation-complexity score per workload, a target architecture recommendation, reconciliation and acceptance rules, and a phased migration plan with effort, cost, risks and a rollback approach per phase.

Which source platforms do you assess?

Teradata, Oracle, Netezza, SQL Server and Redshift warehouses, Informatica PowerCenter ETL estates, and Cloudera or Hadoop platforms, with Snowflake, Databricks, BigQuery or dbt as typical targets. The source platform decides most of the effort, so the assessment is always specific to it.

How is the assessment priced?

As a fixed scope agreed in writing before it starts, so the cost does not grow with the number of surprises found. The fee depends mainly on the number of source systems and the volume of procedural and ETL logic in scope; tell us the platform and the rough size of the estate and we will quote it.

What do you need from us to start?

Read access to query history, job schedules and the warehouse catalogue, a list of the main source systems and consumers you know about, and a business owner for each critical reporting area. Production data itself is rarely needed for the assessment.

Next step

Scope your migration assessment.

Tell us the source platform, the target you are considering and roughly how many jobs and reports depend on it. That is enough to scope the assessment.

Scope your migration assessment