How much you are moving
The number of packages, pipelines, stored procedures and reports in scope, and how tightly they depend on each other.
S, M, L or XL? The assessment decides.
Two things set the size, and both come out of the estate assessment: how much of your estate you are moving, and how complex those assets are. Company size plays along as nuance, not as the driver.
The size
One wave, or the whole estate.
S, M and L each size a single wave: a scoped slice of your estate, documented, built, tested and handed over. XL sizes the estate as a whole, run as a programme of waves.
The size is a direction, not a box. The scope is fixed per size; the content we tune to your estate.
- ± 15 days of our team one wave
The foundations are there and the slice is manageable.
Your target platform is already standing and the assets in scope run mostly straightforward logic. Almost every day goes into the migration itself, so you get proof of value fast.
- One workload or a small, coherent set of assets
- Built, tested and running on Fabric or Databricks
- Knowledge base, lineage and tests for everything in scope
- ± 28 days of our team one wave
A heavier slice, or a few gaps from the assessment.
More assets, more interdependencies, or foundations that are not quite there yet. You get a production-ready wave plus the groundwork the next waves build on.
- A full workload, or several smaller ones with shared dependencies
- Standards, CI/CD and the test harness set up alongside the build
- Handover so your team can run and extend what was delivered
- ± 55 days of our team one wave
A complex estate section, or gaps across several areas.
Heavy legacy logic: custom script tasks, undocumented behavior, tangled dependencies. The build goes as far towards production as is responsible, and we help build the way of working around it.
- A complex estate section, migrated and reconciled against the legacy run
- Platform standards, DevOps and governance built with your team
- Enablement, so your engineers own the new platform when we leave
- 200+ days of our team one programme
The full estate, run as a programme rather than a project.
Hundreds of assets across several source systems, migrated in waves instead of one push. The fleet runs continuously, your team takes over more of it with every wave, and the legacy platform is decommissioned at the end.
- The whole estate, sequenced into waves and prioritized by risk
- Parallel run and reconciliation before anything legacy is switched off
- Legacy decommissioning and a team that can run the platform without us
What sets the size
The scorecard decides, not a hunch.
Before anything is quoted, the Surveyor documents a representative slice of your estate and hands back a complexity scorecard and a risk map. These are the things it measures, and they are what move you along the matrix.
How complex those assets are
Nested and dynamic logic, custom script tasks, behavior nobody documented, and dependencies that only show up at runtime.
What is already in place
Whether the target platform, DevOps process and data ownership are standing, or whether the first wave has to build them too.
The assessment is gate 1: your leads sign off the scorecard before a size is agreed.
Fixed and tuned
The scope is fixed. The content is yours.
Each size buys a known amount of our team, so the commercial side is predictable from the start. What we point that effort at is decided with you, against your estate and your priorities.
- Fixed per size: the effort, the gates, and the artifacts you get back
- Tuned to you: which assets go first, ranked by risk and business value
- Tuned to you: Microsoft Fabric or Databricks, dbt or your own framework
- Always included: the knowledge base, lineage, tests and living docs
Before you commit
Three steps to a number.
- Discovery call. A short conversation about your SSIS, ADF, Synapse or T-SQL landscape and what a good outcome looks like.
- Estate assessment. The Surveyor documents a representative slice and returns a complexity scorecard and risk map.
- Quote. A size, a scope and a prioritized plan, based on what the assessment actually found.
Good questions
What teams ask about sizing.
Do we have to commit to a size up front?
No. The estate assessment comes first and it's what sets the size, so you pick a size knowing what's actually in your estate rather than guessing at it. Until the assessment is signed off, nothing is committed.
What exactly is a day of your team?
A day of the fleet plus the people steering it: the agents do the documenting, building and testing, and our engineers set them up, review their output and prepare the evidence your experts sign off at each gate. You are buying delivered assets, not seats.
Why does XL jump so far above L?
Because it changes unit. S, M and L each size a single wave, a scoped slice of your estate delivered end to end. XL sizes the whole estate as a programme of waves, including parallel run and decommissioning the legacy platform, so it is a roadmap of engagements rather than a bigger one.
Can we start small and grow?
That is the usual path. Most teams start at S or M on a slice that matters, keep the knowledge base, standards and tests that come out of it, and let the next wave run faster because the foundations are already there.
Does company size change the price?
Only as nuance. What drives the size is how much you are moving and how complex it is, not how many people work at your company. A mid-sized business with a tangled twenty-year-old estate can easily size above a large one with a tidy landscape.
Let's talk
Want a size and a number for your estate?
Tell us what you are running today. We start with the assessment, then quote a size against what it finds, so the number is grounded in your estate rather than an average.
Request a quoteA short form, no spam. We usually reply within one business day.