---
title: "Security & Compliance"
description: "SSIS Catalog Migration Wizard transfers catalog objects and configuration values between supported endpoints. Review the guidance below before running a migration or creating an export file containing sensitive information. ## Access and Permissions - For SQL Server SSIS Catalog operations,…"
url: "https://azureops.org/docs/ssis-catalog-migration-wizard/scmw-security-compliance/"
updated: "2026-10-24"
category: SSIS Catalog Migration Wizard
---

# Security & Compliance

SSIS Catalog Migration Wizard transfers catalog objects and configuration values between supported endpoints. Review the guidance below before running a migration or creating an export file containing sensitive information.

## Access and Permissions

- For SQL Server SSIS Catalog operations, the account running the wizard must have the `ssis_admin` role on both the source and target SSISDB.
- Use the least-privileged account that satisfies the product's documented requirements and your organization's operational policies.
- Confirm that the source and target are the intended environments before running a migration.

## Sensitive Values During Migration

The wizard supports migration of sensitive environment variables and project/package parameter values, including connection-manager properties. Review replacement rules and target values before execution, especially when moving from development to test or production.

## SCMW Export Files

**Important:** SCMW export files are not encrypted. If **Export sensitive data** is enabled, sensitive information is written to the export file as readable text.

- Enable export of sensitive data only when necessary.
- Store SCMW files in an access-controlled location.
- Transfer files only through organization-approved secure channels.
- Restrict access to the file and delete temporary copies according to your organization's retention policy.
- Do not include SCMW files containing secrets in source control, public file shares, or unsecured email attachments.

## Migration Type: Copy or Move

**Copy** is the default operation. The **Move** option deletes the selected source catalog items after migration. Use Move only when source deletion is explicitly intended and approved. Consider taking a backup and validating the target before removing source items.

## Environment-Specific Configuration

Use replacement rules to update connection strings, server names, database names, paths, and other values that must differ in the target environment. Carefully review the **Overwrite environment variable values** option: it recreates target environment variables based on source values and can replace target-specific configuration.

## Operational Validation

- Inspect the source catalog and address reported issues before migration.
- Review the migration summary before selecting Finish.
- Review result messages, warnings, and errors after execution.
- Validate migrated projects and test package execution in the target environment before cutover.

This page provides product-specific operational guidance, not legal or regulatory certification. Follow your organization's security, privacy, and compliance requirements.

### *Related*