Skip to content
ITEMRA
Documentation menu

Migration

The import wizard

CSV imports for items, locations, stock, and BOMs: upload, mapping with suggestions, preview, error resolution, and commit.

Import kinds

Imports (Admin group) is the hub for structured data entry: items, locations, stock by location, and BOMs, plus the guided migration presets. Each kind documents its target fields, unique keys, and duplicate strategies (create only, update existing, or both).

Import in dependency order: locations before stock, items before anything that references them.

The wizard

Every import walks the same four steps:

UTF-8 CSV or TSV in; a mapped, validated import out.
  1. Upload — a UTF-8 CSV or TSV. Keep quantity and unit in separate columns and dates in ISO format.
  2. Map — pair file columns with Itemra fields. The auto-suggester proposes mappings from your headers; ambiguous columns stay unmapped for a human decision, never guessed. Save the mapping as a profile and the next file with this layout maps itself.
  3. Preview — validation runs on every row before anything commits: missing required values, duplicate identifiers, unknown units or locations, malformed dates.
  4. Commit — valid rows import; failing rows produce a per-row error report with stable codes. Fix the source and re-import just the failures.

Replay caution

Committed rows have no general undo, and interrupted jobs may have partially processed — inspect the job's status and results before retrying rather than re-running blind, or a replay can double opening stock. Rehearse production-sized imports against a fresh or demo-reset organization first, and keep the source file, mapping, and error report as the migration record. The public API offers the same import machinery for automated pipelines.