Have Any Questions?
Get in Touch
Have Any Questions?
Get in Touch
Data Platform Migration

Know the cost and architecture before you commit to the build.

Moving from a legacy data platform to Microsoft Fabric or Databricks is a significant commitment. Every engagement starts with a 2-week Blueprint Sprint that gives you the architecture design, TCO model, risk register and phased plan your board needs to approve it.

📈
Migration Blueprint Sprint
2 weeks • Fixed price

Everything your board needs to approve the migration.

Before a single line of migration code is written, you will have a complete picture of what the migration involves, what it costs and what could go wrong.

What you receive
  • Current state assessment — platform inventory, schema complexity, dependency map
  • Target architecture design on Fabric or Databricks — medallion layers, ingestion patterns
  • 3-year TCO comparison — legacy cost vs. cloud cost, payback timeline
  • Risk register — complexity scoring, data quality risks, dependency risks
  • Phased implementation plan — milestones, resource requirements, cutover approach
The Blueprint output is yours — a board-ready document that removes every blocker to getting the migration approved.
How the Engagement Works

Two stages. One clear path. No surprises at either end.

Stage 1 is where you get certainty. Stage 2 is where you get the platform. You don’t commit to Stage 2 until Stage 1 gives you everything you need to make that decision confidently.

 
Stage 1

Migration Blueprint Sprint

The board-ready business case for your migration, architecture, cost model, risk register and phased plan, in 2 weeks. Whether or not you proceed to Stage 2, this document is yours.
  • Current state assessment — full platform inventory and dependency map
  • Target architecture design on Fabric or Databricks — medallion layers, not a lift-and-shift
  • 3-year TCO comparison — legacy cost vs. cloud cost, payback timeline
  • Risk register and phased implementation plan — milestones the board can track
🕒 2 weeks • Fixed price
Stage 2

Migration Build

Scope, timeline and price confirmed from the Blueprint. Your legacy platform migrated to Fabric or Databricks using medallion architecture. Your team owns it at go-live.
  • Bronze → Silver → Gold medallion build — raw ingestion through to certified, business-ready datasets
  • Parallel running with validation gates — the business never loses access to its data during migration
  • Knowledge transfer built into every sprint — your team co-delivers and owns the platform at go-live
  • Full documentation handover — data lineage, pipeline runbooks, architecture decision records
🕒 8–26 weeks (complexity-dependent)
Migration Blueprint Sprint

Six sections. Six questions your board will ask, answered.

Most migration projects stall at the approval stage, not because the business case is weak, but because nobody has produced a document that answers the board’s questions with enough specificity to approve budget. The Blueprint Sprint is designed to produce exactly that document in 2 weeks. Every section exists for a reason. Every question it answers is one that will otherwise delay the migration by months.

Current State Assessment
Platform inventory, schema count, data volume, pipeline complexity and full dependency map. Most organizations significantly underestimate their estate complexity. This section surfaces what will actually drive scope and timeline, before the build starts.
Target Architecture Design
Full reference architecture on Microsoft Fabric or Databricks using medallion principles. Data zones, ingestion patterns, transformation framework, security model. A lift-and-shift recreates your legacy problems at cloud speed. The Blueprint designs the target state properly from the start, so the platform you migrate to is better than what you left.
 
3-Year TCO Comparison
Total cost of ownership comparison: legacy platform (license, infrastructure, support, engineering) vs. cloud platform (consumption, engineering, upskilling). The CFO needs a number and a payback timeline before approving migration budget. This section provides both, modeled against your specific platform and usage profile, not a generic benchmark.
 
Risk Register
Complexity scoring by workload. Data quality risks. Dependency risks. Migration sequencing risks. Mitigation approach documented for each. Every migration failure we have seen had a root cause that was visible before the build started and was not addressed. The risk register forces that conversation to happen in week 2, not month 6.
Phased Implementation Plan
Migration approach, phase boundaries, parallel running strategy, cutover plan and resource requirements per phase. The board needs milestones they can track and a clear end state they can commit to. This section gives them both. It also defines what the business needs to provide; access, stakeholders, validation time, so internal resourcing can be planned before the build begins.
Platform Recommendation
If you are undecided, the Blueprint includes a structured platform recommendation based on your specific workload profile, existing Microsoft investment, team capability and long-term roadmap. Platform indecision is one of the most common reasons migration projects stall for 6–12 months. This section removes that blocker with a clear, defensible recommendation, not a vendor pitch.
 
Start the Blueprint Sprint
2 weeks. Fixed price. Everything your board needs to approve the migration. No commitment to the build required, at any point during or after the Sprint.
 
0
Weeks to a complete board-ready architecture and business case
1
Year TCO model included in every Blueprint Sprint, legacy vs. cloud
%
Typical platform cost reduction moving from on-premise to Fabric or Databricks
8 +
Weeks for the Migration Build, scoped and priced from the Blueprint, no surprises
Stage 2 — Migration Build

Not a lift-and-shift. A properly designed cloud-native platform.

The Migration Build is scoped directly from the Blueprint output. Every build follows the same medallion architecture standard, Bronze, Silver, Gold,  so the platform you end up with is designed for performance, governance and extensibility from day one.

Bronze: Raw Ingestion

Every source system ingested exactly as-is. Full historical load plus incremental refresh. No transformation, the complete audit trail of your raw data, preserved.
 

Silver: Cleansed & Conformed

Standardized schemas, applied business rules, data quality framework. Deduplicated, validated and conformed across all sources. The trusted version of your data.

Gold: Business-Ready

Certified semantic models and business-ready datasets. The foundation for Power BI reporting, FastTrack products and self-service analytics. What the business actually uses.
Parallel running: legacy and new platform run simultaneously throughout the migration with validation gates at Bronze, Silver and Gold. The business never loses access to its data. Cutover only happens after sign-off.

The Migration Build follows the Blueprint exactly. Scope, timeline and price are fixed before the first sprint begins. The phased structure means you see working data in the new platform within the first two weeks of the build, not at the end of a 6-month waterfall project.

Your data engineering team co-delivers every sprint. Knowledge transfer is not a handover meeting at the end, it is built into every phase. By go-live, your team can extend the platform, add new sources and manage the pipelines independently.

Legacy platforms we migrate from:

  • Teradata
  • Greenplum
  • Azure Synapse
  • SSIS / Informatica
  • Netezza
  • Oracle DW
  • SQL Server / SSAS
  • Ab Initio

What the Migration Build does not include

  • BI and reporting layer — Power BI report migration and semantic model rebuild are covered by BI Modernization, typically sequenced after the platform migration
  • Application migration — ERP, CRM or operational system migrations are separate engagements
  • FastTrack product deployment — TrueFinance, TrueSCM and TrueRevenue FastTrack are deployed on the new platform after migration go-live
Data Platform Migration

The platform migration is the investment that makes everything else faster.

A FastTrack product deployed on a fragile legacy platform will not deliver the performance and reliability the business expects. Data Platform Migration removes that constraint,  then every TrueNorth product that follows deploys onto a clean, high-performance cloud-native foundation.

If legacy platform

Data Platform Migration first, then FastTrack on the new foundation

If greenfield

FastTrack first. No migration needed
 

Can overlap

Blueprint Sprints for Migration and FastTrack can run in parallel to compress the overall timeline
 
Natural follow-ons after migration go-live

Deploy on a foundation the business already trusts.

Once your platform is migrated and the Gold layer is live, FastTrack products deploy significantly faster, the data is already there, clean and certified.

TrueFinance FastTrack

P&L, Budget vs. Actual, Balance Sheet, Cash Flow — live in 3–5 weeks on the new platform

TrueSCM FastTrack

Sales, Inventory and Purchasing connected — live in 6–8 weeks on the new platform

BI Modernization

Migrate and rationalize your report estate to Power BI on the certified platform foundation
Start Here

Start with the Blueprint Sprint.

2 weeks. Fixed price. A board-ready architecture, TCO model, risk register and phased plan at the end. You have everything you need to get the migration approved, whether or not you proceed to the build with TrueNorth.

US Office

SA Office