Import history

Last updated 2026-06-08

View raw markdown

At a glance

  • Who uses it: Admins reviewing what CSV imports landed and when.
  • When to use it: After an import to verify counts; during troubleshooting; for compliance evidence.
  • Permissions required: Administrator.
  • Navigation path: Administration → Imports → History.

Purpose

Every CSV import (teachers, students, student assignments, staff) creates a batch record. Import history is the per-batch ledger — who ran the import, when, what file, how many rows created vs. updated, and the per-row outcome.

What a batch row shows

  • Type — teacher / student / student assignment / staff.
  • Run by — the admin who confirmed the import.
  • Timestamp.
  • File name — the original CSV filename.
  • Counts — new rows created, existing rows updated, rows skipped (errors).
  • Status — Success, Partial, Failed.
  • Detail — expandable per-row outcomes.

[SCREENSHOT: admin-imports-history-list] Administration → Imports → History with three batches listed (two Success, one Partial) and the Partial row expanded showing per-row outcomes.

Step-by-step

Review a batch

  1. Administration → Imports → History.
  2. Click a batch row.
  3. Read the per-row outcomes. Filter by Errors to see only the failures.

Re-run with corrections

  1. Download the original CSV from the batch (the link sits next to the file name).
  2. Correct the errored rows in your spreadsheet.
  3. Re-upload from the relevant import page. Re-runs are idempotent: existing rows update, not duplicate.

Pagination

History shows newest-first with pagination controls at the bottom. Use Previous and Next to navigate; the "Showing X of Y" indicator tracks your position.

Tips & best practices

  • After a large import, scan the Partial batches first — that's where the data quality issues live.
  • Save a copy of the corrected CSV in your district drive alongside the batch ID for audit purposes.

Common mistakes

  • Treating an "Updated" count as a problem — re-imports normally update existing rows, that's the point.
  • Re-running a failed import without correcting the file — the same rows fail the same way.

Related articles

FAQ

Can I revert an import? There is no one-click revert. For accidental imports, contact support@amplifyed.app with the batch ID — they can scope a targeted rollback.

How long is import history kept? Indefinitely — it's part of the audit log.

Related