What is the actual reason for migrating?
← All services
Fabric Migration Readiness
Should you move to Fabric — and if so, what should actually move first?
A practical readiness assessment before migration starts consuming budget, attention and credibility.
DOES THIS SOUND FAMILIAR?
Start with what is actually happening.
- Leadership wants Fabric, but the business case is still broad.
- The current platform works, although not always elegantly.
- Different teams expect different things from the migration.
- Nobody agrees which workloads should move first.
- A technology decision is in danger of becoming the migration strategy.
WHAT WE NEED TO ANSWER
Good work starts with better questions.
Which workloads are good candidates now?
Which should stay where they are?
What dependencies, skills or governance gaps could slow the move down?
WHAT I REVIEW
The scope follows the problem.
I do not force every engagement through the same checklist. These are the areas that may matter; the agreed scope determines how deep we go.
Current architecture and workloads
Data volumes and refresh patterns
Dependencies and integration points
Capacity and licensing implications
Team capability and operating model
Governance and environment strategy
Deployment approach and migration risk
WHAT YOU GET
Something you can use after the conversation ends.
The output should help you make a decision, change a practice or move the work forward. It should not exist simply to prove that work happened.
Readiness Assessment
Where you are genuinely ready and where preparation is still needed.
Migration Candidate Map
Workloads grouped by suitability, value and dependency.
Migration Waves
A practical sequence rather than a big-bang move.
Risk & Dependency Register
What could derail the migration if ignored.
Roadmap
A clear starting direction for the next phase.
HOW IT WORKS
Enough structure to make the work clear. Not so much process that the process becomes the work.
Context
We start with a short conversation about what is happening, what matters and what has already been tried.
Review
I analyse the relevant parts of the solution or operating model at the depth agreed for the engagement.
Prioritise
I organise observations around impact, risk and usefulness — not around how many issues I can find.
Walkthrough
We go through the findings together, challenge assumptions and discuss trade-offs.
Next step
You decide what happens next: implement internally, continue together or stop because the focused engagement was enough.
YOUR TIME COMMITMENT
I keep the client-side time demand deliberately light. A focused assessment usually needs a kickoff conversation, access or materials, and a final review session. We agree the exact involvement before we start.
A GOOD FIT WHEN
This is likely to help if...
- You are considering Fabric but want to avoid migrating by fashion.
- You need to prioritise workloads before starting a programme.
- You want architecture, people and operating constraints considered together.
IT MAY NOT BE THE RIGHT FIT IF
- The migration scope and architecture are already fully decided and you only need delivery capacity.
- You need a procurement-only licensing comparison.
If the problem is real but the format is wrong, that is useful to know early. I would rather redirect the conversation than force the challenge into the wrong service.
FABRIC MIGRATION READINESS
Should you move to Fabric — and if so, what should actually move first?
Bring me the problem, not a polished brief. A few sentences about what is happening and what you would like to change are enough to start.
Tell me what's happeningPREFER TO WRITE?
Send me a message.
You do not need a polished brief. Whether the topic is Power BI, Fabric, AI, team training, mentoring, coaching or simply a challenge that needs untangling, leave a few details and we can start from there.
SIGNALMESSAGECONVERSATION