Migration

Migrate data into Itemra

Plan a controlled CSV migration with mapping, preview, validation, and reconciliation.

Define the migration boundary

Choose a cutover date and decide which master data and opening balances must move. Keep the source system read-only during the final export. Preserve its full history separately when it cannot be represented as Itemra movements.

Prepare generic files

Export items, categories, suppliers, sites, locations, and stock into UTF-8 CSV files. Give each record a stable external key. Keep quantity and unit in separate columns and use explicit ISO dates.

Map and preview

Use Itemra's import mapping and preview before committing. Resolve missing required values, duplicate identifiers, invalid units, unknown locations, and malformed dates. Import structure and catalog before stock balances.

Reconcile

Compare record counts and stock totals by item, unit, and site. Investigate every rejected row and material variance. Let a small operator group test search, receive, move, count, and reporting before cutover.

Keep a rollback point

Retain the source export, mapping, rejection report, and reconciliation result. Do not delete or overwrite the source system until the agreed acceptance period has passed.

Source presets and their current validation boundaries are documented in the PartsBox, Sortly, and InvenTree guides.