From School Walls to Digital Archives: How Starlings ED Migrated 40+ Years of Student Records to a Cloud-First Platform

## Overview Starlings Education Centre (ED) is a mid-sized independent learning provider operating across three campuses in Western Australia. Established in 1978, the centre has grown from a single neighbourhood classroom to a multi-site institution serving more than 2,400 students annually, with programs spanning early childhood intervention, vocational training, and tertiary preparation. Like many education organisations of its generation, Starlings ED accumulated student records, compliance documents, progress reports, and administrative files in a patchwork of physical archives and standalone digital systems. In early 2025, the centre’s leadership team initiated a digital transformation project with a clear objective: consolidate four decades of student data into a single, secure, cloud-hosted platform. What followed was a nine-month engagement with Webskyne, covering discovery, architecture design, data migration, integration, user training, and change management. This case study documents the full lifecycle and the measurable improvements delivered at go-live and in the months since. --- ## The Challenge Before the project began, Starlings ED’s records ecosystem was highly fragmented. * **Physical archives:** Basement storage at each campus held physical folders covering approximately forty years of enrolments, assessment results, incident reports, and financial correspondence. These files were indexed inconsistently and were vulnerable to water damage, misfiling, and unauthorised access. * **Disconnected systems:** Student administration was split across three tools: a legacy SMS for current enrolments, a payroll-adjacent database used by finance staff, and an early 2000s Learning Management System that had not received vendor support since 2018. * **Manual reconciliation:** Staff spent significant time each month reconciling data between systems, resolving duplicate records, and cross-referencing physical files with digital notes. Estimates from the centre’s Operations Manager suggested between eight and twelve hours per week were lost to these tasks. * **Compliance and audit risk:** State education regulators and accreditation bodies increasingly required rapid production of student records during audits. The existing setup made this process time-consuming and unreliable, exposing the centre to compliance findings and reputational risk. * **No unified search:** Teachers and administrative staff could not efficiently locate student history across campuses. A behaviour support officer, for instance, might need to consult records from five prior years before designing a learning plan; doing so required physically visiting the main campus or requesting files via email. The leadership team recognised that fragmentation was no longer just an operational inconvenience. It had become a strategic barrier to safe growth. --- ## Goals and Success Criteria At the project’s scoping workshop in January 2025, stakeholders agreed on five primary goals and a set of measurable success criteria. 1. **Unified records management:** Build a single source of truth for all student data, replacing fragmented systems and paper archives. Success metric: 100% of active student records accessible from one interface within 90 days of go-live. 2. **Cloud-first architecture:** Migrate from on-premise and disconnected tools to a modern, cloud-hosted platform with automated backups. Success metric: Daily backup verification report shows 100% successful replication, with no manual interventions required. 3. **Compliance and access control:** Meet state education record-keeping requirements through role-based access, immutable audit trails, and secure data retention policies. Success metric: Pass external compliance audit without any records-management findings within the first post-go-live audit window. 4. **Operational efficiency:** Cut time spent locating and reconciling student records by at least 50%. Success metric: Monthly staff survey shows a statistically significant reduction in time-on-task for record retrieval by month three after launch. 5. **Scalability for future growth:** Design a flexible platform capable of expanding into new program areas, campuses, and reporting requirements without major rearchitecture. Success metric: Documented roadmap approved by the centre’s leadership team, with quarterly technology reviews built into governance. --- ## Our Approach Webskyne adopted a phased, education-sector-specific methodology grounded in co-design, iterative validation, and heavy emphasis on change management. ### Discovery and Data Audit Instead of immediately recommending a vendor or building bespoke software, the project began with a four-week discovery phase. Consultants interviewed department heads, classroom teachers, finance staff, and site administrators across all three campuses. The goal was to map existing workflows, identify pain points, and quantify the true cost of the current setup. Following discovery, a forensic data audit was conducted. Over 200,000 records were documented across physical and digital sources. Records were categorised by type, retention period, sensitivity, and current accessibility. The audit revealed that roughly 18% of physical files contained no matching digital record, and approximately 12% of existing digital records contained duplicate or conflicting entries. ### Architecture and Platform Selection With a clear data inventory in hand, Webskyne evaluated platform options against the centre’s requirements: strong document management, role-based access, long-term preservation, and out-of-the-box reporting capabilities. The selected solution was a headless Content Management System with a custom records-management layer built on top, deployed on a managed Kubernetes infrastructure in a secure multi-cloud configuration. This hybrid approach provided flexibility for future integrations while maintaining strong data governance. APIs were exposed for potential future connections to the centre’s planned student information system upgrade and to external government reporting platforms. ### Migration Strategy: Phased with Rollback Planning Rather than a single high-risk migration event, the team designed a phased rollout. Each campus migrated sequentially over a six-week period. Prior to migration, legacy systems were set to read-only for selected staff for two weeks ahead of time to catch reconciliation issues and identify duplicate records. The migration process itself was semiautomated: custom scripts parsed digitised physical files, CSV exports from legacy systems, and scanned PDF documents into a structured ingestion pipeline. Each ingested record was enriched with metadata—student ID, program cohort, campus, date of origin, retention class, and access permissions. A critical part of this phase was rollback planning. If a serious issue occurred during a campus migration, the team needed to return to read-only legacy status within four hours. This contingency was tested via two dry-run migrations and was successfully invoked once during the Field Campus transition when a permissions inconsistency was discovered; rollback occurred in 2.5 hours, the issue was resolved, and migration restarted the following week without data loss. --- ## Implementation Details ### Data Enrichment and Normalisation One of the most labour-intensive parts of the project was normalising decades of loosely structured data. A dedicated team of five educators and two data specialists spent three weeks mapping data fields across systems. This work produced a canonical student schema—a single structured definition of what a student record should contain. Subsequent data imports were validated against this schema, drastically reducing the incidence of corrupted or incomplete entries. ### Permission Model and Compliance The centre required granular access controls. Teachers should see records for their current classes; site administrative staff should manage files for their campus; the Executive Director should have access to aggregate reporting. Remote parents and guardians needed a limited portal to review specific documents. To achieve this, the platform used attribute-based access control rather than simple role inheritance. Permissions were tied to campus location, student cohort, relationship type, and document classification. Every access event was logged in an immutable audit trail with timestamp, user identity, and action performed. This met the requirements of the state’s Education Records Act and positioned the centre well for future regulatory changes. ### Training and Change Management Technology deployment is only successful when people can use it. From week one, Webskyne embedded a change-management specialist within the Starlings ED project team. They ran structured workshops, created quick-reference guides, and established a pilot group of fifteen staff members who tested early builds and surfaced usability issues. Training was delivered in two formats: live campus-based sessions during the final weeks before each migration, and asynchronous video guides hosted within the new platform itself. Attendance at mandatory sessions exceeded 90%, and post-training assessments showed an average comprehension score of 94%. A dedicated internal champion—the centre’s newly appointed Digital Learning Coordinator—was trained early and empowered to provide frontline support to colleagues. This buy-in was instrumental in sustaining adoption rates through the first term after go-live. --- ## Results The platform went live progressively across campuses between May and June 2025, with all sites fully operational by mid-June. By the time Term 3 commenced in late July, the centre had accumulated sufficient operational data to begin assessing outcomes against the original success criteria. By the end of the first full term post-launch, staff saved an estimated 11.5 hours per week collectively in record-retrieval and reconciliation activities. This translated to approximately AUD 18,400 per term in recovered productive capacity, based on average loaded hourly rates for administrative and teaching staff. Compliance posture improved materially. During the state regulator’s annual audit in August 2025, auditors requested records for a cohort dating back to 2019. These were produced in under four minutes via the platform’s advanced search and filters—previously a process that would have required a minimum of one business day and significant manual effort. The audit was completed with no findings related to records management. User confidence grew steadily. The internal digital champion reported that by Week 10 of Term 3, 83% of staff said they were either confident or very confident using the new platform, up from 52% in the first week. Parent and guardian portal usage also rose, with 68% of families accessing documents through the portal by the end of the second month. --- ## Key Metrics | Metric | Target | Result | Status | |---|---|---|---| | Active student records in one interface by 90 days post-go-live | 100% | 100% | Achieved | | Daily backup verification (no manual intervention) | 100% | 100% | Achieved | | Compliance audit findings (records management) | Zero | Zero | Achieved | | Reduction in record-retrieval and reconciliation time | 50% | 61% | Exceeded | | Staff confidence in using the platform at 10 weeks | Not specified | 83% | Strong adoption | | Project duration | 9 months | 9 months | Delivered on time | | Project budget adherence | Within 5% | Within 3% | Under budget | | Migration rollback contingency activation | Tested in dry run | Activated once in production | Tested and effective | --- ## Lessons Learned Several recurring themes emerged from the project that are worth documenting for other education institutions undertaking similar initiatives. **Start with a rigorous data audit.** The discovery phase paid for itself many times over by revealing exactly what data existed, where it lived, and how reliable it was. Had the team rushed to build or buy without this understanding, they would have inherited a messy dataset and faced significant remediation later at much higher cost. **Plan for rollback, not just success.** The decision to set legacy systems to read-only and maintain a proven four-hour rollback capability introduced discipline into the migration process. It also gave stakeholders confidence that the centre would not be left without usable systems if something went wrong. That patience spared the centre from a potential data integrity issue during the third campus migration. **Invest in internal capability, not just technology.** Training a digital champion within the organisation, rather than relying solely on external consultants, created sustainable adoption. When the WebSkyne engagement concluded, Starlings ED already had someone who understood both the technical system and the day-to-day staff context. **Design with future state in mind.** By exposing APIs and using a modular architecture, the platform is ready to integrate with the next student information system, government reporting portals, and potentially future AI-assisted insights tools. The centre avoided the typical trap of replacing yesterday’s technical debt with today’s permanent monolith. --- ## Final Reflection The Starlings ED digital transformation project demonstrates that education-sector records migration is as much an organisational change challenge as it is a technical one. Success depended on clear goals, rigorous discovery, phased delivery with tested contingencies, and consistent investment in people—not just in software. With the platform now in daily use across all campuses, the centre is better positioned to focus on its core mission: supporting students rather than searching for their files. The savings in time and risk have already begun to compound: administrative staff redirect effort to student engagement, compliance costs have stabilised, and the organisation has a clear technical foundation for the next decade of growth. --- *Technical details in this case study reflect a real-world education services transformation project delivered in partnership with an independent learning provider. Project specifics, timelines, and outcomes have been adapted for a professional case study presentation.*