Data Estate and Fabric Readiness Assessment | Kilvora

Data estate and Fabric Readiness Assessment

Fabric won’t fix your data estate. It will expose it.

See what it will find before you commit. This assessment reviews the estate you have today and gives you an honest answer for each workload: adopt now, adopt selectively, or stabilise first.

For organisations considering Fabric, including those with fragmented systems, inconsistent reporting or an unresolved route to implementation. You do not need an existing Fabric environment.

Evidence-based recommendationsEmbedded day-rate or fixed-scope deliveryScope and timing agreed around your estateArchitecture through implementation

The recommendation

Proceed, adopt selectively, or stabilise first.

The recommendation follows the evidence. It can vary by workload, and it can conclude that Fabric should not be pursued for the requirements assessed.

Outcome 01

Adopt now

Suitable workloads are identified and the essential foundations are in place. Move into design and a controlled pilot with agreed success criteria.

Next step: confirm the design scope, validate material assumptions and agree the pilot gate.

Outcome 02

Selective adoption

Fabric fits part of the estate. Progress the suitable workloads while retaining other services or holding them for further investigation.

Next step: agree workload boundaries, coexistence dependencies and conditions for each phase.

Outcome 03

Stabilise first

Existing data, governance, security or operational gaps would put adoption at risk. Address the relevant foundations before committing the affected workloads.

Next step: establish prerequisite actions, accountable owners and evidence needed for reassessment.

An unresolved suitability decision is recorded as unresolved. Where a critical requirement is unmet, the report recommends deferring or declining adoption for that scope, with the reasons and further validation required.

What we examine

Six readiness domains.
One view of what adoption requires.

Discovery starts with the estate you have today. These six domains connect source systems, business needs, governance and operational capability to the proposed Fabric workloads.

01

Data estate and source systems

Sources, integrations, volumes, growth, data quality, business definitions and ownership. Establish where fragmentation or inconsistent data originates, and what needs attention before migration.

Source inventoriesExisting Power BI modelsData quality and definitions
Can the proposed workloads depend on the source data?
02

Governance and accountability

Data ownership, stewardship, classification, access responsibilities, retention and regulatory requirements. Identify gaps in decision authority and the controls needed to handle sensitive data.

Data ownershipSensitive data controlsClassification and Purview
Who owns the data, the decisions and the controls?
03

Integration and operational dependencies

Batch schedules, APIs, database connectivity, gateways, upstream dependencies and recovery requirements. Examine failure handling, reconciliation and the service expectations the new platform must meet.

Gateway dependenciesSource connectivityFailure and recovery paths
Can data arrive reliably and be recovered when it does not?
04

Workload suitability

Reporting, semantic models, analytical processing, latency, concurrency and security requirements. Assess Fabric fit for each candidate workload and identify assumptions that need technical validation.

Lakehouse and Warehouse needs · Semantic model requirements · Latency and concurrency

Does Fabric fit the workload and the business outcome?
05

Skills and operating model

Who will build, review, release, secure, monitor and support the platform. Examine skills, change control, incident ownership and reliance on individuals, alongside sponsorship and adoption capability.

Release controlsSupport ownershipMonitoring responsibilities
Can the organisation own and operate what it intends to build?
06

Commercial and migration readiness

Current cost baseline, licensing assumptions, anticipated workload demand and indicative capacity needs. Establish migration dependencies, transition costs, delivery constraints and a practical adoption sequence.

Current cost baselineCapacity assumptionsMigration dependencies
Is there a credible investment case and a manageable route forward?

Remediation priorities

What needs to change, and when?

A new platform does not resolve inconsistent definitions, unclear ownership or fragile source integrations on its own. Findings are prioritised by their effect on the proposed adoption.

Before implementation

Critical prerequisites

Resolve blockers before the affected implementation activity starts. Examples include an unapproved route to sensitive data, unavailable source access or no accountable owner for a critical dataset.

During design and delivery

Required delivery actions

Resolve issues through the Blueprint and implementation, with explicit checkpoints before go-live. Examples include release controls, monitoring coverage and agreed recovery procedures.

After initial adoption

Planned improvements

Sequence lower-priority improvements where they do not compromise the initial service. Examples include broader catalogue coverage or automation beyond the first agreed workloads.

The remediation register records the finding, evidence, impact, dependency, recommended owner and acceptance criteria. The assessment identifies and prioritises this work; remediation delivery is agreed as part of the engagement priorities.

Evidence and scoring

Six domains, on a single maturity spectrum

The same six domains are placed on a maturity spectrum from Ad Hoc to Mature using agreed evidence. For workload suitability, the maturity score reflects how clearly requirements are defined and validated; Fabric fit is assessed separately for each workload.

Scoring domain
Ad HocEmergingStructuredMature
Data estate and source systems
Governance and accountability
Integration and operational dependencies
Workload suitability
Skills and operating model
Commercial and migration readiness

Illustrative positions shown to demonstrate the scoring format. Actual markers are set from your assessment evidence; these are not client scores.

Ad Hoc

Practices rely on individuals. Ownership and controls are unclear or inconsistent.

Emerging

Some practices exist, with gaps in coverage, repeatability or accountability.

Structured

Defined ownership and repeatable practices support the proposed scope.

Mature

Practices are evidenced, monitored and improved as requirements change.

Insufficient evidence is marked as unverified rather than assigned a reassuring score. Workload suitability is assessed separately from organisational maturity. A strong overall profile does not override a critical security or operational blocker.

Outputs from the readiness phase

A clear starting point.
A practical route into delivery.

An Executive Summary Deck for leadership, supported by a Technical Assessment Document recording the evidence and reasoning behind the recommendation. The outputs below form this assessment package.

Executive Summary Deck and Technical Assessment Document

A leadership presentation setting out the recommendation, readiness scores and material risks, supported by a technical assessment document recording the evidence, reasoning, workload decisions and prioritised actions.

Workload suitability matrix

A view of each candidate workload against business fit, data and integration needs, security constraints, service expectations and commercial assumptions.

Prioritised remediation register

Prerequisites, delivery actions and later improvements, with dependencies, proposed ownership and acceptance criteria.

Design priorities

Recommended adoption boundaries, key constraints, design questions and areas requiring a pilot or further validation. Establishes the brief for subsequent architecture work.

Indicative investment and migration view

Cost drivers, licensing and capacity assumptions, delivery effort ranges and migration complexity. Includes confidence, exclusions and dependencies.

Phased adoption roadmap and readout

Suggested sequencing, readiness gates and evidence needed to proceed, discussed with executive and technical stakeholders.

What a finding looks like

Specific, evidenced and owned.

Every item in the remediation register follows the same format, so it can be planned, assigned and closed.

Illustrative example · not a client finding

Month-end finance reporting depends on a single gateway with no tested recovery.

Domain
Integration and operational dependencies
Evidence
Gateway configuration export, refresh history for the finance semantic models, and the support team walkthrough.
Impact
An outage could delay month-end reporting. If the proposed Fabric workload retains this gateway dependency, the recovery gap must be assessed against the agreed reporting deadline.
Classification
Prerequisite before finance go-live if the gateway dependency remains and recovery cannot meet the agreed service requirement. Check other workloads for shared dependencies.
Recommendation
Confirm the future connectivity path and recovery requirement. Where a gateway remains necessary, establish a resilient arrangement, document recovery and test it before finance go-live.
Owner
Platform team, with the finance data owner signing off.
Acceptance
Evidence that finance refresh can recover within the agreed reporting window, including tested node failover where a gateway cluster is used.

How the engagement works

Readiness first.
Then design and implementation.

The scope and timing of the initial readiness phase are agreed around your estate, priorities and access to stakeholders and evidence.

Scope the decision

A short introductory discussion establishes the problem, candidate workloads, boundaries, stakeholders and available evidence.

Discover and evaluate

Interviews and evidence review build the current state view. Readiness, workload fit, constraints and uncertainties are assessed.

Agree findings and read out

Validate factual findings, finalise the recommendation and present the roadmap, risks and decision gates.

Led by

Emmanuel Obikili

Lead Architect / Engineer, Kilvora

Over 10 years of data and analytics delivery, with recent work focused on Microsoft Fabric architecture and engineering.

From current estate assessment and architectural decisions through to implementation, governance and operational ownership. The readiness phase is led personally, with recommendations grounded in the agreed evidence.

What we need from you

People, context and evidence.

A named sponsor, technical and business stakeholders, candidate workloads, and agreed evidence such as system inventories, integration diagrams, governance policies, cost information and service requirements.

Access is agreed during scoping. Documentation and walkthroughs may be sufficient for some areas; others may require authorised read-only access or client-supplied exports. Evidence limitations are stated in the report.

Common questions

Before we start.

We have not chosen a platform. Is this relevant?

Yes, if Microsoft Fabric is one of the options you are considering. Much of the assessment, including source data, ownership, integration and operating model, is relevant whichever platform you choose. We then assess Fabric suitability for the agreed workloads. Comparing alternative platforms is outside the assessment’s scope.

Does the assessment require an existing Fabric environment?

No. Evidence can come from your current applications, databases, integrations and reporting services. Discovery is scoped to the systems and workloads relevant to the decision.

What if Fabric is unsuitable?

The report states that conclusion for the assessed scope, explains the evidence and identifies unmet requirements. Where evidence is incomplete, further validation is recommended before a platform commitment.

Will you fix the issues identified?

The readiness phase identifies, prioritises and defines acceptance criteria for remediation. Agreed changes can then be delivered within the engagement by Kilvora, working with your team.

How does this differ from the Transformation Blueprint?

The assessment establishes suitability, readiness and the brief for design. The Blueprint resolves the target architecture and documents the decisions and implementation specifications. Detailed workspace, layer, security and deployment designs belong in the Blueprint.

Can this be delivered as part of an embedded engagement?

Yes. Readiness is the initial phase of an embedded day-rate engagement or a fixed-scope delivery programme, with agreed outputs and review points before progressing into architecture and implementation.

Is the introductory call a paid assessment?

No. The introductory call establishes fit and enough context to propose a scope. Evidence collection, detailed analysis and recommendations form the initial paid phase of the engagement.

Start with the decision you need to make

What would you need to know
before committing to Fabric?

A short conversation establishes your objectives, the estate in scope and how Kilvora can support assessment, architecture and implementation.

readiness@kilvora.co.uk