Industry solution
Move student data between systems on a schedule, not by hand.
Admissions, enrolment and reporting data flowing between your CRM, your student information system and the spreadsheets the office actually opens.
The problem
What teams are dealing with.
- Admissions season means another fortnight of CSV exports and re-keying.
- Vendors each want a rostering file in their own format, on their own timetable.
- Student records are sensitive, and most integration tools want them sent to someone else's cloud.
Why it stays unsolved
Existing approaches fragment the workflow.
- The CRM, the student information system and the spreadsheet were bought separately and never connected.
- A custom integration project costs more than a school can justify for a seasonal job.
The DooHorizon solution
FlowDoo already speaks the systems schools use.
FlowDoo
Status: AvailableConnects PowerSchool through a district plugin, Salesforce through a connected app, plus Google Sheets, Google Drive, SQL Server, MySQL and REST APIs — and runs the sync each night.
About FlowDooVizzDoo
Status: Public BetaTurns enrolment, attendance and admissions data into dashboards for leadership.
About VizzDooMLDoo
Status: PreviewMakes modelling approachable for analytics and data science teaching, with every step visible.
About MLDoo
Reference architecture
How the pieces are arranged.
- SalesforceApplicationsSpreadsheets
- FlowDoo
- Validate
- PowerSchoolGoogle SheetsVendor files
Example business workflow
Built once on a canvas, previewed against real records, then run nightly through the enrolment season.
- Admissions records
- Match fields
- Clean and convert
- Look up school and term
- Write to the SIS
- Log the run
Business outcomes
What this lets you do.
- Admissions records from the CRM into the student information system, nightly.
- New-student imports validated before they reach the SIS.
- Rostering files for a vendor, built on the schedule they ask for.
- The end-of-year archive as one flow instead of a fortnight of exports.
Governance and security
How it stays under control.
- Self-host on a machine you control and student records never leave your network.
- A desktop agent lets a scheduled flow use folders on an office computer with no inbound firewall rule.
- One essential sign-in cookie; saved credentials are encrypted and never returned to the browser.
- A data processing agreement is available for hosted use.
Start with this use case.
Start with one use case. Expand across the ecosystem.