Map, Preview, and Review Import Results

Confirm column mappings, row corrections, product matches, and final outcomes before relying on imported data.

Before you begin

Complete workbook readiness and know the selected organization, target module, sheets, and expected row count. Identify which source columns hold stable IDs, SKUs, variations, dates, amounts, statuses, or related records. Decide who is authorized to approve the write.

How it works

Mapping connects source columns to CapitalOS target fields. Preview displays interpreted rows and supports allowed corrections before import. Matching resolves SKUs, aliases, orders, tickets, or other supported relationships. Results then separate completed, skipped, or unresolved rows so follow-up is based on evidence.

Step-by-step

Review automatic mappings and confirm each source column points to the intended field.
Remove mappings for unrelated source columns rather than forcing them into approximate fields.
Save a mapping template only when the layout is stable and clearly named.
Open preview and compare representative rows with the original workbook.
Check dates, decimal interpretation, currencies, statuses, blank values, and variation identity.
Review SKU and related-record matches; resolve ambiguous aliases deliberately.
Correct supported preview values or return to the source workbook for systematic issues.
Confirm target module, sheet selection, row count, and organization one final time.
Start the import and wait for the supported result summary.
Review successful, skipped, and unresolved rows, then verify a sample in the destination module.
Correct and retry only unresolved data rather than reimporting successful rows blindly.

Check your result

The destination contains the expected sample records with correct identifiers and fields. The result summary accounts for the source rows, unresolved items have specific reasons, and no duplicate batch was created during retry.

Common problems

Automatic mapping is wrong: select the correct target field and verify several preview rows.

Dates or amounts shift: inspect source formatting, locale assumptions, timezone, decimal separator, and target type.

A SKU match is ambiguous: resolve the organization identity or alias before writing the row.

Retry creates duplicates: use the result summary and retry only records that did not succeed.

Permissions and data notes

Preview is the final safe review boundary before organization data changes. Imports can affect workflow status, analytics, and linked records at scale. Preserve source and result evidence, restrict approval to authorized users, and verify representative destination records before relying on the full batch.