Developer Releases CLI Tool to Validate Drupal Migration Mappings Before Deployment
Drupal migration errors often surface only after data imports fail silently. In a recent devlog, Victor Jimenez, also known as VictorStackAI, introduced a command-line utility designed to validate migration mappings before execution and flag configuration mistakes early.
The tool parses migration YAML files, resolves plugin chains, and validates mappings against both declared source keys and destination field definitions. Instead of discovering problems through incomplete imports or log inspection, developers receive explicit, line-level error messages during validation.
Example CLI usage:
drupal-migrate-validate --migration user_profiles --strictConfiguration options allow strict validation and field type checks:
validator:
strict: true
allow_missing_sources: false
field_type_checks: trueSample output illustrates how the validator reports conflicts:
[validate] migration=user_profiles
[ok] source keys: 18
[error] mapping: field_bio -> source:bio_text (missing)
[error] field type mismatch: field_age expects integer, got stringThe approach shifts failure detection from runtime to configuration time. While it does not replace migration testing, it offers deterministic validation that can reduce debugging cycles in complex migration projects.
The code is available on GitHub, and the post also references related operational lessons, including hosting metrics visibility, CSS aggregation edge cases, and recent discussion around algorithmic bias in tooling recommendations.
View the repository: drupal-migration-mapping-validator on GitHub. The original devlog is available on VictorStackAI’s blog.

