Importing students

At a glance

Who uses it: Admins rostering students at the start of each school year (or mid-year for new arrivals).
When to use it: Once at year start, plus periodic deltas — or skip if you use Canvas / SIS sync.
Permissions required: Administrator.
Navigation path: Administration → Imports → Students.

Bulk-create or update student records and (optionally) attach them to teachers and facilitators in one CSV.

Two import shapes are supported:

Column	Required	Notes
`student_id`	✓	Your district's stable ID. Used as the alias for future imports.
`first_name`	✓
`last_name`	✓
`grade`	✓	e.g. `5`, `K`, `9`.
`preferred_name`		If different from first name.
`homeroom`
`email`		Only set if the student will use a portal feature.

Column	Required	Notes
`student_id`	✓	Must match an existing student.
`teacher_email`		Existing teacher in AmplifyED.
`facilitator_email`		Existing facilitator.

Confirm your plan's student capacity. Imports that would exceed it are blocked before any rows are created.
For assignments, the teacher and facilitator emails must already exist in AmplifyED — import them first (see Managing teachers).
Keep a backup copy of your source CSV.

[SCREENSHOT: admin-imports-students-preview] Administration → Imports → Students preview screen showing 200 new, 35 updated, 2 errors.

Run a small test file (10 students) on a fresh school year before doing the full roster.
For assignments, build a single combined CSV instead of separate per-teacher files.
Re-importing the same CSV is safe — existing rows update rather than duplicate.

Missing student_id — every row is rejected.
Importing assignments before the matching teachers exist — assignment rows fail.
Changing student_id between imports — creates duplicates. Use aliases instead.

Can I import via Google Sheets? Export the sheet to CSV first.

What encoding should the CSV use? UTF-8. Apostrophes and accented characters in student names will display incorrectly with other encodings.