SQL Server 2016/2017 Integration Services Migration

• SQL Server Integration Services options remain strong, and there’s no immediate need to migrate away from SQL Server.
• Azure-based options exist: some support SSIS, but others require significant rework that’s equivalent to adopting a product from a competitor.
• This milestone event should be used to assess long-term ETL requirements and determine whether to stay on-premises or move to a cloud solution.

SQL Server 2016 and 2017 are leaving Extended support (in July 2026 and Oct. 2027, respectively), and customers need to plan migrations for integration workloads using SQL Server Integration Services (SSIS). The main challenge when upgrading SSIS is the disruption to business operations during migration and the inevitable impact to downstream applications and users that rely on the transformed data.

This report is the fourth in a series that covers the migration and upgrade options for each of SQL Server’s main workloads, highlighting possible destinations, comparing the longevity of each, the level of migration effort, and where the opportunities and risks are.