A guide to standing up a class, caseload, or pilot roster from a CSV without typing every student by hand or creating duplicates you have to untangle later. The work is mostly in the source file: a clean spreadsheet means the import preview is a quick confirmation instead of a cleanup project.

Prepare a clean CSV

Use one row per student with display name, grade level, and any local student identifier your school uses internally in separate columns. Keep sensitive notes out of the import file entirely; this is a roster, not a record. Student email addresses are not required, so do not chase them down for behavior charting.

Review the import preview before confirming

Before you confirm, scan the preview for duplicate names, missing grades, and capitalization that does not match. Fixing the source spreadsheet and re-importing is almost always faster than correcting students one by one afterward. Treat the preview as the checkpoint where the roster is still cheap to fix.

Archive duplicates instead of deleting

When a duplicate slips through and there is any chance a record already has chart history, archive it rather than deleting it. Deleting can remove useful context you will want at a later meeting. Archived students stay out of the daily logging view without losing what was already logged.

Create charts only for students you will log now

After import, create charts for the students you plan to start logging immediately and leave the rest as is. Inactive students without charts do not clutter the daily workflow, so there is no rush to chart everyone at once. For a school or district import, agree on ownership and permissions before loading a large roster so the right people hold access from the start.