Is Google Workspace a problem for school operations?

Not by itself. The risk appears when files, forms, and sheets carry official work without ownership, permissions, naming, retention, or migration rules.

Should this happen before buying a school management system?

Yes. Workspace cleanup helps define what should migrate, what can remain lightweight, and which workflows need a formal system.

Google Workspace School Operations Checklist

Audit Drive structure and permissions

List every shared drive or folder that contains student, admissions, compliance, curriculum, or staff records.
Name the owner for each folder and confirm who should have view, comment, edit, or admin access.
Remove abandoned personal-folder dependencies from workflows that should belong to the institution.
Create naming, archival, and retention rules for sensitive documents before cleanup begins.

Standardize forms, sheets, and templates

Inventory forms that create admissions, student record, support, or compliance data.
Check response sheets for unclear statuses, duplicate columns, hidden formulas, and missing owner fields.
Convert recurring documents into controlled templates instead of copying old files by hand.
Flag spreadsheets that are acting as unofficial databases and need migration planning.

Prepare system migration or automation

Decide which workflows can safely stay in Workspace and which need an LMS, SIS, CRM, or custom workspace.
Define source-of-truth rules before connecting automations or moving data into another platform.
Create a cleanup backlog for active records first, then archived records.
Review access and ownership monthly so Workspace does not drift back into hidden infrastructure.