Released: August 18, 2026
Alert and case data is now fully supported in the Import + Export module. You can bulk import alerts and cases from a CSV file (or SFTP, Dropbox, and Google Drive), and export them to any destination, using the same import and export tasks you already use for other student data.
Alert and case fields are mapped alongside contact fields within a standard task; there is no separate task type to learn. This makes it possible to migrate historical alert and case data from a legacy early-alert system into Element451, or keep an external system in sync on a schedule.
Alert and case imports: Import tasks now support mapping alert and case fields, including type, name, status, system status category, priority, assignee, due date, description or notes, created date, and an external ID. Alerts can also be linked to course enrollments and to an existing case. Cases also support a private flag; private cases require at least one assignee.
Import records in a closed state: The system status category lets you bring records in as they were, for example a resolved or dismissed alert or a cancelled case, instead of everything landing in triage or To Do. This is what makes a historical migration usable on day one.
Person matching: Rows match to contacts using your existing Matching Settings.
Duplicate prevention: When an external ID is mapped, re-importing the same file updates the existing alert or case (or leaves it unchanged) instead of creating a copy.
Test before you run: Preview, Test Import, and Run History with row-level error reasons all work for alert and case rows, and results report created, updated, and failed counts specific to alerts and cases.
Alert and case exports: Alerts and Cases are now options in the "Repeat Fields Based On" selector, with the full field set available for mapping, including record IDs and created and updated timestamps. Alert exports can also include the linked case and course enrollments.
System Mapping transformations: Type, priority, and status values can be translated between your file's values and Element451's using System Mapping column settings, on both import and export.
Auditability: Imported records are tagged with an origin (defaulting to "External import"), the import timestamp, and the importing user, so externally sourced alerts and cases stay distinguishable from ones created in Element451.
Student success teams moving from a legacy early-alert platform can bring years of alert and case history into Element451 without manual re-entry, and institutions with external systems of record can keep them in sync using scheduled imports and exports.
