Fixing ImportX Encoding and Field-Mapping Errors on CSV Imports

CSV imports become painful very quickly when the incoming file encoding does not match what the importer expects. In the original ImportX case, the data looked correct in one context, broke into question marks in another, and eventually triggered field errors such as Invalid field: pagetitle.

That combination usually means more than one problem is happening at once: encoding mismatch, incorrect column mapping, and possibly hidden formatting damage from spreadsheet exports.

A practical import checklist

• confirm the source encoding before import,
• normalize the CSV to UTF-8 in a controlled way,
• check header names and field mapping exactly,
• test with a minimal sample file before running the full import.

Large imports are much easier to debug when you isolate one row and a few columns first. If that tiny sample fails, the issue is structural. If it works, the bigger file likely contains hidden formatting or inconsistent quoting.

Import pipelines become dependable only when encoding and schema mapping are validated before bulk runs.