---
title: Home
description: "Migrate your SSIS Catalog between SQL Server, Azure SSIS IR, and SCMW files with SSIS Catalog Migration Wizard — fast, folder-aware, and fully automatable."
url: "https://azureops.org/docs/ssis-catalog-migration-wizard/scmw-home/"
updated: "2026-10-24"
category: SSIS Catalog Migration Wizard
---

# Home

# SSIS Catalog Migration Wizard

SSIS Catalog Migration Wizard helps you migrate all or selected items from one SQL Server Integration Services (SSIS) catalog to another. Use it for server upgrades, environment setup, backup and restore workflows, cross-network transfers, and repeatable deployments. The wizard is available as an extension for supported versions of Visual Studio and SQL Server Management Studio (SSMS), and as a standalone application.

[View SSIS Catalog Migration Wizard on Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=AzureOps.SSISCataloger2022)

## How to Migrate SSIS Catalog from One Server to Another

[How to migrate SSIS Catalog from one server to another](https://www.youtube-nocookie.com/embed/t2h6xNVFQkc)

## Start Here

1. Review [Prerequisites](https://azureops.org/docs/ssis-catalog-migration-wizard/scmw-prerequisites/) before your first migration.
2. Follow [Getting Started](https://azureops.org/docs/ssis-catalog-migration-wizard/scmw-getting-started/) to select a source, target, catalog items, and migration options.
3. For installation and licensing, see [Installation and Activation](https://azureops.org/docs/ssis-catalog-migration-wizard/scmw-download/).
4. For repeatable jobs, see [Automation](https://azureops.org/docs/ssis-catalog-migration-wizard/scmw-automation/).

## Supported Sources and Targets

- **SQL Server SSISDB:** SQL Server 2012, 2014, 2016, 2017, 2019, 2022, and 2025.
- **Azure Data Factory SSIS Integration Runtime (IR):** for SSIS packages hosted in Azure Data Factory.
- **SCMW export file:** an export format for moving catalog items between environments or networks.
- **Azure SQL Managed Instance:** supported as a migration endpoint.

For compatibility, prefer migrations from a lower SQL Server version to a higher version. SSIS features may not be backward-compatible.

## Features at a Glance

- Compare source and target catalogs and identify items that differ.
- Select folders, projects, environments, and other supported catalog content for migration.
- Map source folders to different target folder names.
- Replace environment variable and project/package parameter values using key-value rules and suggested replacements.
- Migrate project and package parameter defaults and server-side values, including connection-manager properties and sensitive values.
- Migrate folder, project, and environment permissions.
- Export, import, or delete selected SSISDB items in bulk using SCMW files.
- Inspect a catalog for configuration issues before migration.
- Validate migrated projects automatically.
- Automate migration and inspection tasks with the command-line utility.
- Migrate items on the same SQL Server into different folders.

## What Can Be Migrated?

- SSIS Catalog folders.
- SSIS project deployment files (.ispac).
- Environments and environment variables.
- Project and package parameter default values.
- Project and package parameter server-side values, including connection-manager properties and sensitive values.
- Folder, project, and environment permissions.

## Common Use Cases

- Move SSISDB content to a new or upgraded SQL Server.
- Copy selected projects or environments between development, test, and production.
- Prepare a parallel environment by replacing server names, database names, paths, or other configuration values.
- Transfer catalog items between networks or domains using an SCMW export file.
- Back up selected catalog content for later import.
- Automate routine migrations as part of scheduled jobs or CI/CD workflows.

### *Related*