Overview
Schema migrations fail in predictable ways: fields that exist in the source have no target mapping, data types that are compatible in one direction aren't in the other, business logic embedded in the source schema is lost in translation, and the migration is declared complete before anyone checks whether the data actually arrived correctly.
A defensible schema migration is not a column rename and type cast. It is a field-level transformation specification: every source field mapped to a target field with an explicit transformation rule, every unmapped field documented with a disposition decision, every type conversion validated for data loss, and a completeness check that verifies the migration preserved every record.
The Schema Migration & Data Transformation Cleaning Prompt generates a complete migration specification: source-to-target field mapping, transformation rules, conflict resolution, data loss risk assessment, validation queries, and a rollback plan.
What you get: - Complete source-to-target field mapping with transformation rules - Unmapped field disposition decisions - Type conversion data loss risk assessment - Conflict resolution for structural incompatibilities - Post-migration validation queries - Rollback strategy and success criteria
Built for: data engineers, database administrators, and analytics engineers executing schema migrations, data warehouse loads, or system consolidations.