Your situation
The company has chosen Fabric. Your SSIS packages did not get a vote.
A platform mandate arrives as a date and a license. The warehouse team inherits the hard part: hundreds of SSIS packages, SQL Server procedures and schedules that have to become Fabric pipelines, notebooks and warehouse objects, and still produce the same numbers. Novuz converts them by rule, proves each one, runs inside your Azure tenant, and prices the whole estate before work starts.
What is happening
What is actually happening?
An enterprise agreement, a Microsoft push, or a CIO decision has set the target and a window. The SSIS estate was built package by package over a decade and the control flow, variables, expressions and error handling in it are undocumented. The native tooling moves some of it; the rest is a rewrite nobody has sized.
The cost of waiting
What does waiting cost?
- License paid for a platform you are not yet using while the old one is still paid for.
- The mandate's date arriving with the hard part unplanned.
- Packages rebuilt by hand, differently each time, with no proof they match.
In three business days
What does the estate assessment give you?
- Every package, data flow, procedure and schedule counted and banded, with lineage.
- Which packages are dead or duplicated.
- A fixed price to Fabric and the first domain to move.
- Where the native tooling stops for your estate and where Novuz starts.
Honest fit
Who should not do this?
- Teams with no SQL Server or SSIS estate behind the mandate; a greenfield Fabric build is not a conversion.
- Estates under about 300 objects.
Related
Where to read next
FAQ
Frequently asked questions
Does the Microsoft tooling do this?
It covers part of the path; the comparison page sets out where each tool stops. Novuz converts the packages and procedures it does not, reconciles every object and runs in your tenant.
What does an SSIS package become?
Fabric Data Factory pipelines for control flow, notebooks or Dataflows for transformations, warehouse objects for the SQL, with schedules preserved and each package reconciled against its original output.
Does Novuz run inside our tenant?
Yes, as a container in your Azure account next to Fabric; nothing leaves.
Sources and further reading
- Microsoft Lifecycle, SQL Server 2016: extended support ended in July 2026
- Microsoft Lifecycle, SQL Server 2017: extended support ends in October 2027
- McKinsey & Company, "Tech debt: Reclaiming tech equity," October 2020: CIOs estimate tech debt at 20 to 40 percent of the value of their technology estate, and 60 percent say it has risen
Written by Debjani Dhar, Co-founder and CEO, Novuz · Technical review: Ted Ghose, Co-founder and CTO, Novuz
Last reviewed:
Find out what your logic debt is costing you.
Every object counted, lineage, dead code and a fixed price in three business days. $3,000, credited.
Not sure which door? The scorecard takes ten minutes and tells you.