Skip to main content

Reverse Engineering a DTSX into Biml

Why Convert an Existing Package​

A common question when adopting Biml is whether existing SSIS packages can be turned back into Biml. The answer is yes. The Package Importer in BimlStudio reads a dtsx file (or an entire SSIS project) and generates equivalent Biml. The result is useful in two situations: migrating an existing solution to a metadata driven workflow, and learning how to express a specific SSIS feature in Biml without reading the dtsx XML by hand.

When to Use the Importer​

The importer is the right tool when an unfamiliar SSIS task needs to be expressed in Biml. Build the smallest possible package in SSDT that contains only the task in question, save it, then import that file. The resulting Biml will be focused and easy to read. Importing a large production package works too but produces a much larger Biml document that takes longer to study.

Two practical considerations apply before uploading or importing:

  • Strip embedded passwords and other sensitive values from the dtsx file. The importer has to read the file in clear, and any uploaded copy may persist.
  • Keep the input package minimal. A package with one Data Flow and one task generates Biml that is easy to compare against documentation. A package with twenty tasks produces Biml that is correct but harder to digest.

Using the Package Importer​

In BimlStudio, open the Package Importer from the project menu. Choose the dtsx file (or the project file for a complete import) and start the import. The tool produces a preview of the generated Biml together with the option to add it to the current project or create a new one. From there the Biml file can be saved, edited, and reused like any other Biml asset.

That is the whole workflow. The technique turns the import once, study the output approach into a reliable way to learn Biml syntax for unusual SSIS features, and provides a starting point for converting an existing solution into a Biml driven build.