Skip to main content
SSIS .dtsx packages combine control flow (precedence constraints, containers, tasks) and data flow (sources, transformations, destinations). Planasonix maps data flow elements to pipeline nodes and control flow to orchestration constructs where supported.
Use Import and convert for batch uploads of .dtsx files and governance around draft pipelines.

​
.dtsx package parsing

1

Export packages cleanly

Save .dtsx from Visual Studio SSDT or export from SSIS catalog per your standards. Include project-level connection managers when the wizard asks for the ispac or companion files.
2

Resolve parent/child patterns

If execution uses parent packages or package parameters, include those .dtsx files in the same upload batch so parameter bindings resolve.
3

Choose SQL Server dialect

Select T-SQL semantics when your packages target SQL Server; choose the dialect matching your actual destination if packages were retargeted to Synapse or another warehouse.

​
Data flow to pipeline mapping

SSIS data flow componentPlanasonix direction
OLE DB Source / ADO.NET SourceSQL or table source nodes
Flat File SourceFile source with delimiter and encoding metadata
LookupJoin or lookup transform—verify cache and no-match behavior
Derived Column, Conditional SplitColumn transforms and branches
Aggregate, SortAggregation and sort nodes
OLE DB Destination / SQL Server DestinationDestination nodes with insert or merge options
Annotate Data Flow task names in SSIS before export (DF_Load_FactSales) so Planasonix subgraphs inherit readable titles.

​
Control flow translation

Control flow items outside data flow translate unevenly:
Precedence constraints map to ordered edges and sometimes conditions on success/failure/expression. Validate that expression constraints referencing SSIS variables became equivalent branch conditions or were flagged for manual work.
For Loop and Foreach containers may become parameterized runs or loop constructs when supported. Complex Foreach File enumerators may require file watcher triggers or scripted file lists instead.
Standalone Execute SQL tasks map to SQL nodes or pre/post hooks. Watch for temp table scopes that depended on a single SSIS session—databases without shared session semantics need redesign.

​
Script tasks and custom components

Script Task and Script Component code (C#/VB) does not execute in Planasonix.
Replace .NET logic with Python nodes, SQL, or stored procedures. Budget time for security review when script tasks touched filesystems or COM APIs.

​
Connection managers and parameters

Map OLE DB, ADO.NET, Flat File, and FTP connection managers to Planasonix connections. Use variables for package parameters and project parameters.
EncryptSensitiveWithUserKey packages are painful to migrate on a different host. Re-encrypt with EncryptSensitiveWithPassword or deploy via catalog project parameters before export when possible.

​
Validation

SSIS error outputs and row disposition (redirect rows) map to data quality or branch patterns inconsistently. Inspect every red or yellow item in the conversion report before scheduling production runs.

Control flow nodes

Containers, branching, and error paths after import.

Data quality

Recreate SSIS error outputs as explicit checks.