Data imports
Import jobs bring tool inventories, contract calendars, and assessment data into Pytheus, with status and row counts tracked.
Last updated September 22, 2026
Data imports are how bulk data gets into Pytheus without hand entry. The Integrations surface tracks each import job so you can see what was brought in, how much of it landed, and whether anything failed.
Kinds of import
Onboarding imports seed your environment. They cover a tool inventory, a contract calendar, or a combined tools-and-contracts file, and they move through stages from uploaded and parsing to validating and completed.
Assessment imports bring existing capability assessment data into CAMP, so your team reviews and refines rather than starting from a blank page.
What each job records
Every job carries a label, a status, the number of rows in the source, and how many were processed, along with timestamps. That lets you confirm an import finished cleanly and catch one that stalled or partially failed, rather than assuming the data is all there.
An import that reports fewer processed rows than source rows is not done. Check the difference before you trust the data downstream.
Imported data is a starting point, not a finished record. Verify it before it shapes decisions, exactly as described in Importing assessment data.