Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A useful SSIS inventory is a decision aid, not proof that packages will migrate or run unchanged. It should show what each package depends on, what might block its use, which Fabric path is plausible, and how you will verify the result. Microsoft documents an SSIS execution option in Fabric, but its Invoke SSIS Package activity is currently in preview; Microsoft also marks Data Migration Assistant (DMA) as deprecated.
What an inventory needs to help you decide
Microsoft recommends assessing source SSIS packages because the findings can reveal issues that would prevent a successful migration. Its migration overview separates findings into migration blockers and informative issues. Treat those categories as a starting point for triage: a blocker needs a resolution before the proposed path can work, while an informative issue still deserves review because it may affect operations or validation.
The checklist below is a proposed working inventory, not a Microsoft-prescribed schema. Record one row per package, then link related project, job, configuration, and orchestration details where a package cannot be understood in isolation.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →| Inventory area | Record | Why it matters |
|---|---|---|
| Identity and location | Package name, project, source location, and storage type: file system, Package Store, or SSIS catalog, as applicable. | Establishes what is in scope and where assessment or migration work must start. |
| Files and settings | Package and configuration files; parameters, environment references, and connection settings that affect execution. | Surfaces dependencies and settings that may need to be recreated or changed. |
| Execution context | SQL Server Agent job or other scheduling and orchestration relationships, including upstream and downstream dependencies. | A package is only one part of the workload; migration planning must account for how it is invoked and what consumes its output. |
| Assessment findings | Issue, severity or category, affected feature, and proposed resolution; distinguish blockers from informative findings. | Turns a scan or review into a remediation queue rather than a pass/fail label. |
| Destination and path | Intended Fabric destination, whether the existing package may be run through the SSIS activity, or whether package or pipeline redesign is expected. | “Fabric migration” can mean different execution and modernization choices. |
| Validation | Development test environment, expected outputs, row-count checks, schema comparisons, and business-rule checks. | Defines how the team will establish that the migrated or invoked workload behaves correctly. |
How to build the inventory
1. Establish package scope and storage
Gather the package and project names, their locations, and how they are stored. Microsoft’s migration overview describes DMA batch assessment coverage for packages in File System, Package Store, and SSIS catalog storage in DMA v5.0 and later. However, Microsoft also says DMA is deprecated. Verify the tool’s current availability and support for your environment before making it part of a new operational process; do not treat the documented coverage as an endorsement of DMA for new deployments. Microsoft’s SSIS migration overview explains the assessment context.
#1 Best Overall
2. Capture dependencies and runtime assumptions
For each package, map its connections, configuration files, credentials or authentication method, schedules, and upstream or downstream relationships. Keep secrets out of the inventory itself: note where a credential is managed and who owns it, not its value. Also identify assumptions tied to the current SQL Server, network, identity, or destination so they can be checked against the intended Fabric design.
3. Classify issues and assign remediation
Record assessment findings at the package or feature level, then assign an owner and a concrete next action. Separate migration blockers from informational findings as Microsoft’s assessment guidance does. A finding is not resolved merely because a model summarizes it: someone must determine whether the issue applies, how it will be addressed, and what evidence will show the fix worked.
Rank #2
4. Select a target path for each workload
Do not assume every package has the same destination. Some organizations may seek to run an existing SSIS package through Fabric’s Invoke SSIS Package activity; others may need to remediate packages, rebuild surrounding orchestration, or choose a different supported destination. The right choice depends on compatibility, connectivity, authentication, operational maturity, and validation effort. Microsoft’s documentation does not establish a universal best path for every package estate.
5. Define validation before implementation
Set expected results before changing the workload: representative inputs, output schemas, row counts, and relevant business rules. Microsoft recommends validating AI-assisted migration work in development and using automated checks such as row counts, schema comparisons, and business-rule checks. These checks should be tied to package-specific expectations, not treated as a guarantee simply because they pass once.
Choose the assessment method with lifecycle status in view
Microsoft’s overview documents DMA assessment and batch coverage in DMA v5.0 and later, while also marking DMA deprecated. That makes it historical and documented guidance rather than an uncomplicated recommendation for a new assessment program. Confirm what tooling is supported in your organization’s environment and at the time you begin; the cited overview does not establish a replacement tool for every scenario.
Regardless of the scanner, preserve findings in a reviewable form: package, finding, impact, decision, remediation owner, and validation evidence. Automated assessment can identify likely issues, but the inventory still needs a human decision about relevance and target architecture.
Rank #4
Running existing SSIS packages in Fabric is a separate decision
Microsoft documents an Invoke SSIS Package activity for running SSIS packages in Fabric Data Factory. The page explicitly labels the activity as preview, so its status and limitations may change. The documentation requires packages to be stored in OneLake and describes additional prerequisites, configuration, monitoring, and limitations; placing a package in OneLake alone does not establish compatibility or successful migration. Review the current Invoke SSIS Package activity documentation before choosing this route.
Running a package is not the same as modernizing all orchestration around it. If the wider workload includes ADF pipelines or other coordination, assess those separately against the intended Fabric design. Microsoft’s ADF-to-Fabric migration best practices cover broader pipeline migration considerations; they do not make every SSIS package a direct conversion.
Best Value
Pay particular attention to connections and identity
Connection details can determine whether a package is portable. For a Fabric Data Warehouse destination, Microsoft’s tutorial discusses Microsoft Entra ID authentication for users and service principals and shows adapting package authentication and connection settings. Inventory the authentication mode and connection assumptions per destination, then plan any required changes rather than copying credentials or connection strings into an AI prompt. See Microsoft’s SSIS and Fabric Data Warehouse tutorial.
Where a Claude Skill can help—and where it cannot
A Claude Skill may help turn package documentation or sanitized metadata into a consistent draft inventory, suggest questions about dependencies, or organize findings for human review. Microsoft names Claude among the LLMs that can assist with migration tasks such as refactoring expressions, converting ADF JSON to Fabric syntax, drafting MERGE statements, connection templates, and validation scripts. That is evidence for AI as an aid on specific tasks, not evidence that a particular inventory Skill is complete, accurate, or tested.
Keep proprietary packages, credentials, connection strings, and sensitive data out of AI tools unless your organization has explicitly approved the data handling arrangement. Microsoft advises avoiding sensitive information in AI tools and validating generated work in development. Treat generated inventory entries as leads to verify against the package, its runtime configuration, and the team that owns it. Microsoft’s migration best practices provides the privacy and validation guidance.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
