Spreadsheet replacement plan for school management, ERP, and SIS

Inventory before replacing

A spreadsheet is often a symptom of a missing workflow, not merely an old file. Inventory the sheets, owners, users, fields, formulas, imports, exports, copies, links, reports, and decisions they support. Include files used only during term start, year end, admissions, fee collection, or reporting.

Classify each sheet as source of truth, working list, calculation, report, temporary transfer, archive, or shadow system. The school cannot plan a safe replacement until it knows what the file actually does.

Assess risk and minimum scope

Look for sensitive data, broad sharing, stale copies, hidden formulas, manual re-entry, unclear definitions, and a single expert who understands the file. The U.S. Department of Education data governance checklist connects quality, access, security, lifecycle, sharing, disposal, and monitoring.

Choose one high-value workflow for the first replacement. Do not migrate every historical column because it exists. Define the minimum fields, relationships, history, approvals, reports, exports, and retention needed for the approved outcome.

• Inventory and accountable owner
• Approved data and definition map
• Migration sample and reconciliation rule
• Role and permission matrix
• Temporary fallback and retirement date

Design the replacement workflow

Map the trigger, record, validation, decision, exception, output, and support route. Ask where the new system becomes authoritative and how a correction moves through dependent reports, messages, payments, or family views.

GOV.UK procurement guidance recommends data protection by design and default, minimum necessary data, access control, security, supplier responsibilities, subprocessors, incident notification, and data return or deletion. Include these questions before moving data into a replacement.

Migrate and validate in stages

Start with a controlled sample. Compare counts, identifiers, relationships, dates, statuses, totals, permissions, and outputs. Have the people who use the workflow accept the result. Keep the old sheet read-only or otherwise controlled while reconciliation completes.

Test duplicates, missing values, changed guardians, archived records, corrections, exports, and reports. A technically successful import is not proof that the school can make the same decision safely.

Train, retire, and review

Train by role and scenario. Explain the new source of truth, correction route, support path, and what must no longer be copied into a private sheet. Provide a temporary fallback for critical work and a dated plan to retire it.

Review at 30, 60, and 90 days for duplicate entry, correction loops, support questions, access exceptions, and the original outcome. If the old sheet returns, investigate the unmet need instead of simply banning it.

The retirement decision should be visible to everyone who depended on the file. State the final read-only date, the approved replacement, the owner of historical access, the retention rule, and the route for a missing value or report. A hidden copy is not a reliable fallback; it is an unmanaged data store.

Apply the guidance to one school decision

Before approving this guidance for spreadsheet replacement plan for school management software, translate it into one school-specific decision record. State the workflow, roles, data fields, permissions, evidence, support route, academic-calendar constraint, and condition that would hold the next phase. Keep product capability, school responsibility, legal advice, and measured outcome as separate questions.

Run the decision with controlled data and the people who will operate the workflow. Record what was observed, what remains unknown, who owns the unresolved item, and when it will be reviewed. Revisit the record after launch at 30, 60, and 90 days. This keeps a useful guide from becoming an untested promise or another document that sits outside daily work.