Resolving Column Mapping Issues

Step 2 of the import wizard is where you map the columns in your CSV file to the corresponding fields in AccuArk. The wizard attempts to auto-map columns based on their header names, but auto-mapping does not always produce the correct result. This article explains the most common column mapping issues and how to resolve them.

1. No Columns Were Auto-Mapped

What happened: The column headers in your CSV file do not match any of the keywords that AccuArk recognizes. All fields show (Not Mapped) after loading your file.

How to fix it:

• Manually map each column — Click the Maps To dropdown next to each column from your file and select the AccuArk field it corresponds to. Use the Preview column on the right to verify that the data looks correct for each mapping.
• Rename your CSV headers — If you prefer auto-mapping for future imports, rename the column headers in your CSV to match what AccuArk expects. The easiest way to find the expected names is to export a template: open the Data Exchange Center, click Export on the same data type, and save the file. The exported CSV will have the exact header names that AccuArk recognizes.

2. A Column Was Mapped to the Wrong Field

What happened: Auto-mapping matched a column in your file to an incorrect AccuArk field. For example, your “Description” column was mapped to “Name” instead of “Item Description.”

How to fix it:

• Click the Maps To dropdown for the incorrectly mapped column and select the correct field from the list.
• Check the Preview column to confirm the sample data matches what you expect for that field.
• If the same AccuArk field appears mapped to two different columns, correct the wrong one first — AccuArk will flag the duplicate (see scenario 4 below).

3. “Required Fields Not Mapped” Error

What happened: You attempted to proceed to Step 3, but one or more required fields (marked with an asterisk *) are not mapped to any column in your file.

How to fix it:

• Review the mapping list and look for required fields that show (Not Mapped).
• For each unmapped required field, click the Maps To dropdown and select the column from your file that contains that data.
• If your CSV file does not have a column for a required field, you will need to add that column to your file. Open the CSV in a spreadsheet, add the missing column with the appropriate data, save the file, and restart the import.

4. Multiple Columns Mapped to the Same Field

What happened: Two or more columns from your CSV file are mapped to the same AccuArk field. Only one column can be assigned to each field.

How to fix it:

• Decide which column in your file contains the best data for that field.
• Keep that column mapped to the AccuArk field.
• For the other column(s), click the Maps To dropdown and select (Skip) to exclude them from the import.

5. My CSV Has More Columns Than AccuArk Expects

What happened: Your CSV file contains extra columns that do not correspond to any AccuArk field.

This is not a problem. Extra columns are ignored during import. They will automatically be set to (Skip) in the mapping list. You do not need to remove them from your file. Simply ensure that the columns you do need are mapped correctly and proceed.

6. My CSV Has Fewer Columns Than AccuArk Expects

What happened: Your CSV file does not have columns for every AccuArk field listed in the mapping step.

This may or may not be a problem. Only required fields (marked with *) must be present. Optional fields can remain unmapped — AccuArk will use default values or leave them blank. If a required field is missing from your file, you will need to add that column before you can proceed (see scenario 3 above).

Best Practice: Always Export a Template First

The most reliable way to avoid column mapping issues is to start with an AccuArk export as your template:

1. Open the Data Exchange Center
2. Click Export on the data type you plan to import
3. Save the exported CSV file
4. Open it in Excel or Google Sheets
5. Replace the sample data (if any) with your own data, keeping the header row intact
6. Save as CSV and use this file for your import

Because the headers match exactly, the auto-mapping step will assign every column correctly, and you can proceed directly to validation without any manual adjustments.