# csv import columns misaligned error questionnaire: how to fix it

Misaligned CSV columns in a questionnaire import mean the delimiter or quoting is off, so values land in the wrong fields. Open the file, confirm whether it is comma or semicolon delimited, and make sure quoted fields are consistent. Re-import once the structure is clean and columns line up.

```text
csv import columns misaligned error questionnaire
```

## When to use this skill
- Imported questionnaire columns dont line up
- Values appear under the wrong headers

## When not to use this skill
- Encoding errors (a different skill)
- Import fails entirely (a structural issue)

## Tool compatibility
RFP questionnaire CSV imports with delimiter settings.
Related area: CSV and Excel data import pipelines.
Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with imported questionnaire columns dont line up, start at step 1 below.
- If instead encoding errors (a different skill), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Inspect the raw file

```
Open in a text editor and check the delimiter and quoting on a few rows.
```
Expected: you see whether commas, semicolons, or tabs separate fields.

### 2. Fix quoting on text fields

```
Wrap any field containing the delimiter character in double quotes.
```
Expected: every row has the same field count.

### 3. Match the importer delimiter setting

```
Set the import delimiter to match the file, or convert the file to match the importer.
```
Expected: preview shows columns aligned.

### 4. Re-import and verify

```
Import and check that answers sit under the right questions.
```
Expected: columns line up correctly.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (inspect the raw file): Expected: you see whether commas, semicolons, or tabs separate fields.
- Step 2 (fix quoting on text fields): Expected: every row has the same field count.
- Step 3 (match the importer delimiter setting): Expected: preview shows columns aligned.
- Step 4 (re-import and verify): Expected: columns line up correctly.

## Quick recap
1. Inspect the raw file
2. Fix quoting on text fields
3. Match the importer delimiter setting
4. Re-import and verify

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### csv columns misaligned import
Delimiter mismatch is the cause nine times out of ten. If this matches what you saw, the steps above apply as written.

### questionnaire import wrong columns
Check the preview before committing the import. If this matches what you saw, the steps above apply as written.

## Why it happens
CSV has no real standard, so commas inside unquoted text fields shift every column after them. European exports using semicolons read as one giant column under a comma-expecting importer.

## Edge cases
- Line breaks inside quoted fields are legal but fragile, avoid them
- Always check the import preview, never blind-commit
- A stray delimiter in one row misaligns everything after it

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst__4R6vmWYwM_FFm3PMOzcOw