Import Field Mapping Recheck

Recheck an import file’s column mapping against the fields the import requires. Preparation only, not an account action.

What to provide

The import file columns and the field mapping chosen for the import.

How it works

1. List the columns in the import file.
2. Record the field each column maps to.
3. Mark required fields left unmapped.
4. Return the recheck without importing.

The output

file | columns | mapped | unmapped | required_missing | verdict

Worked fictional example

Fictional import CSV has 6 columns; the mapping covers 5 fields and leaves the date column unmapped: 1 of 6 columns unmapped, so the import would create undated posts.

Checks and limits

Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

More marketing workflows · How-to guides

Method: reviewed source. Demand lead: Oct17 live AIS Search Console: marketing Copilot 37 impressions, Planable/Claude 45, Planable/ChatGPT 24, campaign brief 12, Muse India 125. Analytics and reporting topics follow parent-query leads plus documented marketing operations needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured. Checked October 24, 2026.