Services
Four ways in, depending on what you already know about your estate.
Most teams arrive with one of four problems: nobody knows what is in the estate, the server it runs on is going away, the nightly batch keeps failing, or the person who understood it all has left. Each of those has a different first engagement.
SSIS Estate Assessment
Start here if nobody can tell you how many packages you have.
We inventory every package, connection manager, Script Task, third-party component, SSISDB project and SQL Agent job; map the dependencies and the data lineage; and classify each package as retire, lift-and-shift, or rewrite. The deliverable is a risk register and a sequenced migration plan your team can execute — or hand back to us.
Assessment is a standalone piece of work with a standalone output. It does not commit you to a migration, and it is deliberately the kind of document you can take to a vendor who is not us.
Lift-and-Shift to Azure
Start here if the SQL Server instance is the problem, not the packages.
We move packages onto the Azure-SSIS integration runtime or SQL Managed Instance: resolving the third-party components and Script Task blockers that assessment tooling flags but does not fix, migrating the SSISDB catalog, re-mapping SQL Agent schedules to triggers, running both estates in parallel with row-count and checksum reconciliation, and then cutting over.
The packages keep working the way they work today. That is the point.
Selective Rewrite to ADF or Microsoft Fabric
Start here if specific loads are failing, slow, or changing every quarter.
We rebuild the packages that deserve it as metadata-driven Azure Data Factory or Microsoft Fabric pipelines, add logging, alerting and restartability, retire the flows nothing consumes, and leave the rest on SSIS.
The word doing the work in that sentence is selective. In most estates the packages worth rewriting are a minority carrying a majority of the pain.
SSIS Run and Maintain
Start here if the estate works and nobody owns it.
Ongoing ownership for teams with no SSIS engineer: nightly failure triage, package and query performance tuning, schema-drift fixes, upgrade and patch work, and documentation of what each job actually does. Available on its own, or after a migration, and available as staff augmentation alongside your team.
How engagements are priced
Hourly time and materials. Senior US engineers billed by the hour, as project engagements or staff augmentation; scope, staffing and timeline are agreed through an initial conversation. We do not quote a package migration by the package before we have read the packages.