I am using SSMA for MySQL to migrate from MySQL to MSSQL and on several tables I am getting the 22018 error. After lots of mucking about I found that the error was being generated due to Russian characters being stored in these tables.

For example: `Бухгалтерский учет`

There are other non-English characters in the tables, such as `Profissão Jurídica` and they are coming through OK.

The error is to do with collation and the collation on the MySQL table is `latin1_swedish_ci` and the column that holds the "foreign" characters has `utf8_unicode_ci` collation on it and is a `varchar(255)`.

The recipient table in MSSQL uses the database default collation (`Latin1_General_CI_AS`) and the recipient column is a `nvarchar(255)`.

In SSMA the *charset mapping* for `latin1` is set to the default of `CHAR/VARCHAR` and I have tried having this set to `NCHAR/NVARCHAR` with no success. The *type mapping* for `varchar` is set to `nvarchar` for all instances.

The only thing close to an answer that I have found is [this posting](https://social.technet.microsoft.com/Forums/exchange/en-US/528e7363-fbba-4d0d-b2da-a326bf12e181/ssma-from-mysql-error-22018?forum=sqlservermigration). Unless I'm missing the point of the answer, I can't see that there is a missing conversion - or is there?