CSV: first import
Validate and submit CSV, then read the import batch result.
integrationcsv
Audience: Organization admin / academic ops · Applies to: SaaS / private deployment
Goal: Land one successful small-sample import, then scale to full load.
Prerequisites
- CSV filled per Templates and fields.
- Signed in to the org console with access to Data integration.
Recommended order
- Classes
- Teachers, students
- Class members
Steps
- Open the Data integration import entry (Import users (entry)).
- Pick the import type and upload the CSV.
- Run Validate first (do not jump to submit):
- Read errors by row number
- Fix the file and re-upload to validate
- After validation passes, Submit to create an import batch.
- In the batch list, check success count, failure count, and failure summaries.
- Fix only failed rows and re-import (or follow the product’s update strategy).
How to confirm success
- Batch success count matches expectation.
- New rows appear under Teachers / Students / Classes.
- Spot-check one teacher and one student login for class and to-dos.
Practice tips
- Start with 5–10 rows.
- Keep single files modest; split full load by grade/department.
- Keep each batch ID for support triage.
Common failures
See Common import errors. If validation passed but some rows failed after submit, fix row-by-row from batch detail.