Data governance · Embedded in live programmes
Project DG: data governance for ERP, migration and AI programmes
A senior data lead embedded in your programme while the data can still be saved: critical data profiled before migration scope is priced, source-to-target mapping governed and logged, rehearsals passed on measured thresholds and day two ownership designed before go-live. Working alongside your systems integrator, on your side of the table. From £22,000 + VAT per month, three to nine months, matched to the programme.
Project DG at a glance
Definition
What is data migration governance?
Data migration governance is the discipline that stops a live programme discovering its data too late: profiling the critical data before migration scope is priced, governing the source-to-target mapping and cleanse decisions with an owner and a log, setting rehearsal pass criteria as measured thresholds, preventing cutover workarounds becoming permanent debt, and designing who owns the data in the new system before go-live rather than after.
Intelance delivers it as Project DG: a senior data lead embedded in ERP, migration, analytics and AI programmes from £22,000 + VAT per month for three to nine months, working alongside your systems integrator rather than for them. The integrator runs the loads. Project DG governs what they load, what passes rehearsal and who owns the result on day two.
Planning the wider cloud or ERP programme around the data? EA for Cloud & ERP Transformation maps every stage and its published fee, with Project DG carrying the data through it. The wider practice is described under data governance consulting, and our guide to why data governance is the foundation of safe AI explains why AI programmes inherit exactly the same risk.
Profile before pricing
Migration scope cut from measured data, before the contract fixes it.
The mapping has an owner
Every source-to-target decision governed, logged and yours.
Rehearsals on thresholds
Pass criteria as measured numbers per data set, set in advance.
Owners before cutover
Ownership in the new system settled before cutover.
The failure modes
Six places programme data goes wrong
Every data crisis a programme board meets traces back to one of these six. Project DG is built against each one, and every card says what gets protected.
Discovery at rehearsal
The data gets profiled for the first time when the first migration load fails, with the go-live date already public.
ProtectedThe critical data profiled and measured before migration scope is priced.The mapping nobody owns
Source-to-target lives in the integrator’s spreadsheet, understood by contractors who leave at go-live.
ProtectedMapping decisions governed, logged and owned on your side.Quality assumed
Cleanse effort budgeted on optimism, then discovered mid-flight as weeks of business time nobody planned.
ProtectedCleanse sequenced from measured defect rates, owned by named people.The ownership vacuum
Nobody decides who owns the customer record in the new system, so the old arguments migrate with the data.
ProtectedDay two ownership designed before cutover.Cutover data debt
Interim loads, manual fixes and “temporary” workarounds that quietly become permanent.
ProtectedEvery workaround logged with an expiry date and an owner.Day two blindness
The programme ends, the SI leaves, and the new system’s data governance was never anyone’s deliverable.
ProtectedThe day two running routine handed over as part of the engagement.How it works
The five stages from screen to handover
Five stages, matched to the programme. The decisive one is rehearsals: the go or no-go decision is earned from measured thresholds agreed in advance.
The programme screen
Where the data decisions are being made, what has been profiled and how much rehearsal risk is already priced in. Pre-contract is ideal. Mid-programme rescue is common.
The data baseline
Critical data profiled, quality measured, migration scope re-cut against evidence and the cleanse plan sequenced by defect rate. The number the whole programme argues from.
In the meetings
Mapping decisions governed and logged, cleanse tracked, integrator designs challenged from your side of the table. They run the loads. We govern what they load.
Rehearsals on thresholds
Pass criteria set as measured thresholds per data set, failures triaged by evidence, and the go or no-go decision earned from the numbers.
Day two ownership
Go-live data verified against the baseline, workarounds closed or dated, and the new system’s data rhythm handed to named owners. The programme ends. The data does not.
Larger and multi-entity programmes need a bigger data workstream, and we say how much at scoping. If the programme has not started yet, the Data Governance QuickScan prices the data risk in ten working days, before any contract fixes the assumptions.
Published fees
The services around Project DG
Every route is priced before you choose it.
Data Governance QuickScan
Ten working days of profiled evidence: ownership, quality, lineage, access, law and AI readiness, scored and costed before any programme is priced.Best whenThe programme has not started and the data is unmeasured. FeeFrom £14,500 + VAT10 working days 02
ProjectEA
The architecture side of the same programme: the target set, vendor designs challenged and day two protected, stage by stage.Best whenThe whole programme needs an architect, beyond the data. FeeFrom £45,000 + VATfixed by tier 03
Virtual CDO
Day two owned for the long term: senior data leadership two to four days a month, running the rhythm the programme handed over.Best whenThe programme is done and the data needs an owner. FeeFrom £7,500 + VAT / month 04Delivery Assurance
The independent check on the programme itself: status verified against evidence rather than the steering pack.Best whenThe board wants arm’s length proof the programme is where it says it is. FeeReviews from £8,500 + VATThe alternatives
How Project DG compares with the alternatives
Three ways programmes handle the data risk. The difference is whose interest gets protected when the first load fails.
The SI maps your data to their template and calls the gaps business decisions
Migration surprises surfacing at rehearsal, priced at panic rates on the critical path
The vendor’s timeline, protected efficiently
Free, then very expensive
A data workstream with no data leader: a swim lane on the plan rather than a capability
Status green until the first load fails, then a quality crisis nobody owns
A RAID log entry with nobody’s name on it
Cheap, and it changes nothing
A senior data lead in the meetings: profiling early, governing the mapping, owning day two, from £22,000 + VAT per month
A measured baseline, a governed mapping, rehearsals on thresholds, day two owned
The systems you run on day two, contractually and explicitly
A fixed monthly fee matched to the programme, agreed in writing
Scope
What this covers and what it leaves out
You get
The critical data profiled and measured before migration scope is priced.
A governed mapping and cleanse log with named owners on your side of the table.
Rehearsal pass criteria as measured thresholds per data set, agreed before the rehearsal.
A workaround register with expiry dates, closed before it becomes permanent debt.
Day two ownership and the running routine handed to named people as a deliverable.
This is not
The migration itself. The integrator runs the loads. Project DG governs what they load and what passes.
A replacement for your SI. We work alongside the integrator, challenging designs with evidence in the meetings where they are made.
A paper workstream. Every deliverable is a measured artefact: baselines, logs, thresholds and registers.
Self-assurance. When a board wants arm’s length assurance of a programme Project DG works inside, that review goes to a team with no stake in the answer. If we built it, we do not assure it.
Where to start
How engagements usually begin
Four situations we are usually called into. If none of them fit, speak to us and we will point you at the right first step.
Why Intelance
What you can hold us to
On your side of the table
The integrator answers to their timeline. Project DG answers to you. Designs are challenged with evidence, in the meetings where they are made.
A fixed monthly fee matched to the programme
From £22,000 + VAT per month for three to nine months, agreed in writing. No day-rate drift on the critical path.
Evidence before assertion
The baseline is measured, the thresholds are numbers and the go or no-go decision is earned from them.
No products waiting at the end
No platform, no licences, no vendor commission, and no stake in any integrator’s timeline.
Independent of the integrator
If a board wants arm’s length assurance of a programme we work inside, that review goes to a team with no stake in the answer. If we built it, we do not assure it.
The team on your engagement
Every Project DG engagement is led by a senior data lead, supported by senior consultants and established delivery partners.
Programme data guides
All insights
Data GovernanceWhy data governance is the foundation of safe AI
Every property you want from an AI system is inherited from the data beneath it. Why the governing has to start with the data, the five foundations AI needs, and a ten minute readiness test to run before any AI project is approved.
9 July 2026 · 6 min read Read the guide
AI GovernanceEnterprise AI governance in 2026: a practical blueprint for CIOs and boards
9 July 2026 · 8 min read
AI GovernanceWhat is AI governance? The seven questions boards should ask
9 July 2026 · 9 min read
AI GovernanceEU AI Act ISO 42001: how they fit together in your architecture
7 December 2025 · 10 min readReady to talk?
Tell us about the programme
Thirty minutes with the lead who would sit in your meetings: what is migrating, who is running it and whether anyone has profiled the data it depends on. If the honest answer is not yet and go-live has a date, sooner matters.
FAQs
Questions about Project DG
What is data migration governance?
The discipline that stops a live programme discovering its data too late: the critical data profiled before migration scope is priced, source-to-target mapping and cleanse decisions governed with an owner and a log, rehearsal pass criteria set as measured thresholds, cutover workarounds logged with expiry dates, and day two ownership designed before go-live.
How much does embedded programme data governance cost?
Project DG runs from £22,000 + VAT per month with Intelance for three to nine months, fixed in writing and matched to the programme. For context, data problems found at rehearsal are priced at panic rates on the critical path, and UK data governance day rates run £1,100 to £2,400 per day, which is how unmanaged data workstreams quietly outspend governed ones.
Does the systems integrator cover data governance?
Not in your interest. The integrator maps your data to their template, prices cleanse effort on optimism and calls the gaps business decisions, because their incentive is the timeline. Project DG works alongside the integrator on your side of the table: they run the loads, we govern what they load and what passes rehearsal.
Why do ERP programmes fail on data?
Six failure modes account for most of it: data profiled for the first time at rehearsal, a mapping nobody on the client side owns, cleanse effort assumed rather than measured, no decision on who owns the data in the new system, cutover workarounds becoming permanent, and day two governance that was never anyone’s deliverable.
What are migration rehearsal pass criteria?
Measured thresholds per data set, agreed before the rehearsal: completeness, match and reconciliation rates the load must achieve to pass. Failures are triaged from evidence and the go or no-go decision is earned from the numbers, which makes the decision defensible.
When should Project DG start?
Before the integrator contract is signed, ideally: the programme screen prices the data risk while the migration scope can still be negotiated from evidence. Mid-programme rescue is common and works, but every month of delay moves the same problems closer to the critical path, where they cost more.
What is the difference between Project DG and ProjectEA?
Same programme, different risk. ProjectEA is the architecture side: the target set, vendor designs challenged and day two protected across the whole estate. Project DG is the data workstream: profiling, mapping, rehearsals and day two data ownership. Large programmes often run both, scoped separately.
What happens after go-live?
Day two is a deliverable in its own right: the data verified against the baseline, workarounds closed or dated, and the running routine handed to named owners. Where the estate needs ongoing leadership, the Virtual CDO from £7,500 + VAT per month or the Data Governance Office from £9,500 + VAT per month carries it from there.
