Skip to main content
Bulk import is appropriate for initial catalogue loading and controlled data migration. The supported import formats and routes must be verified in the v6 source; this guide provides a safe process rather than assuming a particular importer exists.

Prepare the source

  • Define a source-to-target field mapping.
  • Normalize encoding, dates, decimal values, currency codes, and identifiers.
  • Deduplicate natural keys such as SKU or external reference.
  • Validate category, language, tax, and inventory references.
  • Separate create, update, and deactivate operations.

Run safely

  1. Back up the target database.
  2. Test a small sample in staging.
  3. Validate row counts and rejected records.
  4. Run production imports in batches sized for available database capacity.
  5. Make reruns idempotent using stable external keys.
  6. Reconcile imported records and totals.

Failure handling

Keep an import report with row number, safe error reason, and source key. Avoid storing secrets or unnecessary personal data in error files. Do not retry a partially completed import until you know whether the operation is idempotent.

Verify

Locate import commands, controllers, background jobs, and supported formats in the target release before publishing exact CLI flags or API schemas.