Import, review & export
09 Import, review & export
Make the move a sequence of reviewable results.
A migration is more than uploading a file. It has a source, matching decisions, accepted changes and destination formats. Homeroom provides concrete import and export paths that can be examined against the data your school actually needs.
Begin with a defined source.
The roster import run records the source system and adapter alongside the incoming people. Student information system IDs, names, grade and homeroom provide the basis for matching and review. Preserve the original source and decide which staff member owns questions about identities, enrollment and spelling before committing the proposed changes.
A practical pilot includes several kinds of row: an existing student whose homeroom changes, a new student, an unchanged student and an ambiguous match. These are illustrative test cases, not a promise that every school’s data follows a neat pattern. They make the behavior observable before a full roster depends on it.
Preview before committing.
The preview groups creates, updates, conflicts and unchanged records. It supplies match information and field differences where relevant. Its result says the import has not been persisted, while an audit record of the preview can still be written. That is a precise boundary: the proposed roster changes remain uncommitted, and the review action can have a history.
Read the changed fields, not only the total count. A surname correction and a new student may look similar in a spreadsheet but require different identity decisions. A homeroom update may be straightforward while a missing source ID deserves investigation. Leave conflicts as review items until the responsible staff have resolved the ambiguity.
Commit the accepted changes and retain the trail.
Committing the import applies creates and updates through the import-run process and records a change ledger. Import history and field-change views make it possible to inspect the accepted result afterward. Conflicts remain review work. The staff member responsible for the migration should reconcile the resulting roster with the source and inspect representative changes in the workflows that depend on them.
The right end point for a pilot is more specific than “the file uploaded.” It might be that the new student appears in the expected roster, the corrected name is present, the unchanged student retained their identity and the unresolved match remains visible for review. That provides a meaningful basis for deciding what to migrate next.
Choose an export for its actual destination.
Digital publication export offers an HTML flipbook with classic, modern or contrast styling and full or reflow layout choices. It also offers a PDF manifest as structured JSON. A manifest describes the material for a PDF workflow; it is not itself a generated PDF. School access and the safe output projection apply before the export is produced.
The portrait exchange path provides a PSPA index in text or CSV form with a manifest header. That gives a specific destination format to inspect. It does not establish that the export contains every photograph, every record or every setting in the platform. Academic outputs have their own JSON, print-data and PDF paths, and their own checks.
Begin with the work
Bring us the part
of school life you want to improve.
A roster that needs careful reconciliation. A publication program with several titles. A picture day with too many loose ends. Tell us who does the work, what they use today and what a reviewed result should look like. We can discuss the relevant workflow, its requirements and its limits.
Talk through your school’s needsAn inquiry, with room for your actual questions. No activation or purchase is implied.