# MT to MX migration notes

> SYNTHETIC / TRAINING ONLY. Apply the governing scheme, market-infrastructure, bank, and product rules before implementation.

Reviewed: 2026-07-19

- Treat translation as semantic transformation, not tag replacement.
- Baseline field cardinality, option-letter semantics, code sets, character sets, identifiers, structured parties and remittance data.
- Identify MX data that cannot survive an MT leg; define reject, repair, truncation and disclosure policy explicitly.
- Preserve UETR and business correlation where the governing profile requires them.
- Validate against the exact market-practice profile, then test business rules that XSD validation cannot express.
- Prove serial and cover routing, sanctions transparency, charges, FX, account posting, reporting and investigation continuity.
- Run reconciliation across old and new channels during coexistence and retain the original message plus transformation evidence.