Get Support
Blog
SSIS Catalog Migration Wizard SSRS Reports Migration Wizard Azure Elastic Jobs Manager
About Us Get Support
View Categories

Prerequisites

0:00 1:46

Review these requirements before running SSIS Catalog Migration Wizard for the first time.

Prepare the Target Catalog #

  • Ensure that the target SQL Server has an SSIS Catalog (SSISDB). If it does not, create the catalog under Integration Services Catalogs on the target SQL Server before migrating.
  • Avoid restoring an existing SSISDB backup over the target as a substitute for preparing the catalog. This can lead to unexpected errors during or after migration.

Permissions #

  • The Windows user running the wizard must have the ssis_admin role on the source SSISDB.
  • The user must also have the ssis_admin role on the target SSISDB.
  • When connecting to a SQL Server SSIS catalog, the wizard uses Windows Authentication.
  • For Azure SSIS IR endpoints, provide the Azure SQL Server administrator credentials requested by the wizard. The Azure SQL Server connection in this workflow uses SQL authentication.

Connectivity and Compatibility #

  • Confirm that the computer running the wizard can connect to the source and target endpoints.
  • If you can connect to the SQL Servers from a client such as SQL Server Management Studio, the wizard should generally be able to use the same connectivity.
  • Supported SQL Server versions include 2012, 2014, 2016, 2017, 2019, 2022, and 2025. Azure Data Factory SSIS Integration Runtime, Azure SQL Managed Instance, and SCMW files are also supported endpoints.
  • Prefer migrations from lower to higher SQL Server versions. SSIS features may not be compatible when moving backward to an older version.

Recommended Pre-Migration Checks #

  1. Run the catalog inspection operation and review any reported issues or warnings.
  2. Review source and target catalog contents and decide whether to migrate the entire catalog or selected items.
  3. Identify environment variables and parameter values that must change for the target environment.
  4. Confirm whether target environment variables should be retained or overwritten.
  5. If using SCMW export files, plan how the file will be transferred and stored securely.

Continue to Getting Started.

Images and screenshots will be added in a later pass.