Character encoding maps textual characters to coded representations such as bytes. During a MySQL or MariaDB migration, assuming standard SQL compatibility can hide incompatible encodings and corrupt imports. section 10.3
Diagnosing an encoding mismatch
A PostgreSQL import can fail with `invalid byte sequence for encoding "UTF8": 0xe9` when a dump retains MySQL's latin1 bytes for é. Convert the dump with `iconv -f latin1 -t utf8` before retrying the import. section 10.3
Encoding problems can continue after byte conversion:
- MySQL's historical `utf8` supports only three-byte characters, whereas `utf8mb4` supports four-byte Unicode characters, including characters the older implementation cannot encode. section 10.3








