Origo Help

Import and export

Use a small, mapped sample before making a bulk change, and treat every import or export as a reviewable job.

Last reviewed:

Key concepts and when to use them

Import brings structured data into Origo. Export produces a selected dataset for review or use elsewhere. A mapping connects source columns to Origo fields. Preflight checks whether the chosen mapping and current catalogue configuration can be used before the job writes data.

Permissions and preparation

Prepare a current backup or export, a clear source owner, and a small representative sample. Viewers can see the Import Jobs history summary. Creating an import and opening restricted import-job details require an admin or editor. The Export Jobs page, all export actions, and export results require an admin or editor.

Steps

  1. Open Import Jobs, choose the dataset, and start with a small sample file.
  2. Review each source column and map it to one intended Origo field. Keep identity columns mapped.
  3. Select Start import job. Origo runs preflight as part of this submission before it writes data.
  4. If preflight reports a mapping, language, attribute, or value issue, correct it and select Start import job again.
  5. When preflight succeeds, monitor the Import Job progress and row results.
  6. Open Export Jobs separately. Choose the dataset, format, and any available scope, then wait for the Export Job to finish before using its result.

Verification

Check the job status, processed and failed rows, and the resulting records. For an export, open the result and confirm its scope, identifiers, headers, and representative values.

Common mistakes and rules

  • Do not begin with the full source file.
  • Do not map two columns to the same target without an intentional, reviewed reason.
  • Do not treat an export as a complete backup unless its selected dataset and scope are known.

Work through a representative example

Start an Import Job with five chair records containing an identifier, name, material, and seat height. Map each source column once, run preflight, and correct an invalid list option before starting the job. After it completes, inspect all five records. Create a separate Export Job for the same small scope and compare its identifiers and fields before using the full source.