Forum Discussion
Migrating ~100 SSIS Packages to Azure: Acceleration Strategies & ADF vs. Fabric Guidance
Hi everyone,
Our team is currently planning to migrate approximately 100 SSIS packages (including several large and highly complex workflows) to Azure. We are evaluating two primary paths: a lift-and-shift using Azure Data Factory (ADF) SSIS Integration Runtime (SSIS-IR) vs. a full rewrite.
Current Architecture / Tech Stack: Azure, VMs, Azure SQL Managed Instance (SQL MI)
We would appreciate insights on the following:
Accelerated Rewrite Options: If we decide to rewrite, are there automation tools, frameworks, or best practices to expedite the transition rather than manually rebuilding every activity in ADF?
ADF vs. Microsoft Fabric: Given Microsoft’s strategic push toward Fabric, is ADF still the ideal migration target, or should we consider targeting Fabric Data Pipelines directly?
Thank you in advance for any inputs, advice, or shared experiences!
1 Reply
For roughly 100 packages, I would not choose a blanket rewrite first. Microsoft’s SSIS migration guidance starts with assessment, then migration, because dependencies and unsupported components determine the economical path. Inventory package storage, SQL Agent schedules, connection managers, custom components, file shares, and protection levels. Run the Azure-enabled SSIS assessment in SSDT across the portfolio, classify blockers, and test a representative complex package on Azure-SSIS Integration Runtime connected to SQL Managed Instance. Lift and shift compatible packages first; rewrite only where blockers or redesign justify it. No supported converter reliably turns arbitrary SSIS control and data flows into ADF or Fabric pipelines. Fabric Data Factory is Microsoft’s recommended starting point for new integration work, but that does not make ADF SSIS-IR an invalid migration target. Use source control, parameterization, Key Vault, performance tests, and scheduled IR start/stop.
