ssis-to-dbt-replatform-migration

To deploy converted SSIS packages to dbt and Snowflake tasks, the Skill validates SnowConvert AI Replatform output, remediates placeholders, and executes phase-gated dbt project deployment alongside TASK and PROCEDURE orchestration SQL in dependency order.

Migrating SSIS ETL packages to dbt on Snowflake involves scanning converted Replatform output, validating missing files and broken references, fixing hard-coded environment specifics, and deploying dbt projects with automated table stubs and rollback-safe dry-run previews.

Yes, you can validate SnowConvert Replatform output before deploying to Snowflake. The Skill enforces pre-deploy validation checks for placeholder values, missing files, broken references, and hard-coded environment specifics with guided fixes.

Yes, the SSIS to dbt migration workflow requires manual approval. It enforces a phase-gated workflow with explicit user confirmations for each deployment stage, ensuring safe, traceable, and repeatable Snowflake operationalization.

When operationalizing Snowflake tasks after SSIS conversion, limitations include resolving placeholder values and broken references before deployment. The workflow handles etl_configuration, dbt projects, and orchestration inventory checks but requires explicit user approval at each phase gate.

Yes, you need SnowConvert AI Replatform output to use this Skill. It is specifically designed to scan, validate, and deploy projects converting SSIS packages into dbt projects and orchestration SQL stored within the Replatform output directory structure.