Cohiva Campus reads a standard AVETMISS NAT file set and stages students, qualifications, units, enrolments, outcomes, disabilities, prior education and completions. The importer runs a dry-run preview before an idempotent commit, and it uses the same NAT export you already produce for reporting, so no special vendor export is required.
Migrate from the export you already have
Switching student management systems usually stalls on data migration. Cohiva Campus removes the dependency on a vendor-specific export: it reads the standard AVETMISS NAT file set, which is the same export you already produce for reporting.
What the importer stages
The NAT-file importer reads your NAT set and stages students, qualifications, units, enrolments, outcomes, disabilities, prior education and completions. It builds the offerings it needs from the data, so the whole student lifecycle comes across rather than a bare list of names.
Preview before you commit
The importer runs a dry-run preview first, so you can see exactly what will be created before anything is written. The commit is idempotent, so re-running it does not duplicate records. That makes it safe to import, review, correct and re-import.
Why this matters
Because the importer works from the NAT export you already generate, you do not need your current vendor to produce anything special, and you can stage your real data to evaluate Campus before you decide. This lowers the cost and the risk of switching.
How to start
Export your current AVETMISS NAT set, run it through the Campus importer, and review the dry-run preview. From there you can commit the staged data when you are ready.
Frequently asked questions
- What do I need to migrate to Cohiva Campus?
- The standard AVETMISS NAT export you already produce for reporting. No special vendor export is required.
- What does the importer bring across?
- Students, qualifications, units, enrolments, outcomes, disabilities, prior education and completions.
- Can I preview the import before committing?
- Yes. The importer runs a dry-run preview before an idempotent commit, so you can review what will be created.
- Is it safe to run the import more than once?
- Yes. The commit is idempotent, so re-running it does not duplicate records.
- Can I use the importer to evaluate Campus?
- Yes. You can stage your real data and review the dry-run preview before deciding.