Skip to main content

Correct incorrectly mapped data fields during a contact CSV import

If a CSV import mapped your contact data to the wrong fields, you can fix it by updating your CSV and re‑importing it with the correct mapping.

Bartlomiej Rekosiewicz avatar
Written by Bartlomiej Rekosiewicz
Updated yesterday

Updating your CSV lets you overwrite incorrect values, remove unwanted data, or correct fields that were placed in the wrong columns. Once re‑imported, the mapped fields are updated immediately in your account, blank values remove existing data, and your corrected details are available straight away for personalisation, segmentation, and automation.

What you can do

  • Update the affected columns in your CSV file.

  • Re‑import the file and map each field correctly.

  • Overwrite your existing data with the corrected values.

If only a few fields need fixing, create a CSV with just the Email column and the fields you want to update. This overwrites only the mapped fields.


1. Edit your CSV file

  1. Open your CSV in Excel or another editor.

  2. Find the columns that were mapped incorrectly.

  3. Adjust the data as needed:

    • Correct any values that were placed in the wrong column.

    • Move or rename the column headers so they match the Dotdigital data fields you intend to map.

  4. Save your file in CSV format.

To remove values from a data field, leave the cells blank and map the column during import.


2. Import your corrected CSV file

  1. Go to Audience > Contacts.

  2. Select Import contacts.

  3. Choose your updated CSV file.

  4. If asked, select Unicode (UTF‑8) as the encoding.

  5. Continue to the Data mapping step.


3. Map your data fields correctly

During the mapping step:

  1. Map each CSV column to the correct Dotdigital data field.

  2. Map Email to Email Address so Dotdigital can match and update existing contacts.

  3. If you see columns you don’t want to update, set them to Skip column.

Correct mapping ensures that only the fields you specify are updated and prevents accidental data changes in other fields.

Did this answer your question?