TLDR
Switching off Brightwheel is less risky than most directors think if the migration is sequenced around billing cycles and subsidy reporting windows. This guide walks through a 2-to-3 week cutover that keeps attendance records intact, parents informed, and compliance documentation current through the change.
Why centers switch
The switch usually starts with a single moment. A state licensor asks for 12 months of ratio documentation, and the director spends Saturday assembling spreadsheets from Brightwheel’s basic attendance exports. Or a subsidy agency kicks back a claim because the attendance records do not match the billed hours, and reconciling the mismatch takes half a week.
Brightwheel is genuinely good at what it was built for: parent engagement. The app is polished, parents adopt it quickly, and the daily reports keep families feeling connected. None of that is at risk when you switch. What switches is which platform does the compliance heavy lifting.
The common triggers: per-enrollment pricing that grew past $300 a month as the center filled up. Subsidy billing that requires manual CSV reconciliation every month. Ratio tracking that shows the morning headcount but misses the transitions that actually cause licensing violations. Audit prep that requires a full weekend of spreadsheet assembly before every inspection.
If any of those sound familiar, the switch is a cost-savings and risk-reduction move — not a downgrade on parent experience.
What you’ll need to export
Get these five things out of Brightwheel before you commit to a cutover date.
Child roster CSV: Full names, dates of birth, enrollment dates, classroom assignments, and current status (active, waitlist, withdrawn). This is Brightwheel’s cleanest export.
Family contact CSV: Parent/guardian names, phone numbers, emails, pickup authorizations, and emergency contacts. Verify emergency contacts are current before import — stale contact data is common and dangerous.
Billing records CSV: Invoice history, payment records, and any outstanding balances. Do not attempt to migrate in-progress invoices — close them out in Brightwheel first.
Subsidy billing data: If you bill CCDF, CCAP, or state vouchers, export the authorization documentation and any active reconciliation records. Subsidy data is the most fragile part of the migration; budget extra time here.
Historical attendance: Request this through Brightwheel support, not the self-serve export. Attendance logs older than 90 days may take 3 to 5 business days. Request it the day you decide to switch so it’s ready when you need it.
Step-by-step migration
The migration runs over 2 to 3 weeks. Front-load the data work; back-load the cutover.
See the ordered step checklist below for the week-by-week breakdown.
Two principles matter more than the specific tasks. First, never run a single subsidy billing cycle across two systems — reconciliation becomes impossible and auditors notice. Second, never cut Brightwheel off before the parallel run is complete. You will need it as a reference, and cancelling early invites data loss panic.
Staff training checklist
Staff training is where migrations quietly fail. The operational motions look familiar, but enough details change that staff slip back into paper workarounds during the first week if they don’t feel confident in the new system.
Hold two 45-minute sessions: one for the check-in, check-out, and incident workflow, another for activity logging, photo sharing, and parent messaging. Give each staff member a printed one-page cheat sheet for the first week. Identify one “power user” per classroom — a lead teacher who picks it up fastest — as the go-to for day-to-day questions.
Do not schedule training the week of cutover. Staff need a week between training and go-live to practice without operational pressure.
Go-live timeline (2-3 weeks)
Days 1-3: Export all data from Brightwheel. Start the historical attendance request.
Days 4-7: Import into the new platform. Configure classrooms, ratios, subsidy sources, and billing.
Days 8-10: Staff training. Power users configure their classrooms.
Days 11-17: Parallel run. Staff operate in the new system; Brightwheel stays as reference.
Days 18-19: Send parents their new credentials. Share the why.
Day 20: Cutover. Brightwheel becomes read-only.
Days 21-27: Support parents transitioning. Keep Brightwheel accessible as a parent-only reference.
What to expect in month 1
Week 1 post-cutover is the hardest. Expect 30 to 50 parent support messages — most are login help, missing photos from a specific day, or confusion about the new billing portal. Stock a FAQ document for your front-desk staff.
Week 2 normalizes. Parents who are going to use the new app daily have adopted it. Holdouts ping you for help.
Week 3 is when operational benefits show up. Your Monday morning ratio check takes 2 minutes instead of 20. The first subsidy reconciliation of the new month runs automatically against attendance records. A staff certification renewal alert fires before it expires.
By week 4, the director’s weekly paperwork load drops noticeably — usually 3 to 5 hours per week returned to the work you actually want to do.
The compliance posture is the bigger shift. Instead of assembling audit documentation after an inspector asks, the records are audit-ready continuously. That is the durable benefit of the switch.
Q&A
Can I migrate from Brightwheel without paying for both systems at once?
Brightwheel bills monthly, so one overlap month is usually the maximum cost. Time the cutover for the last week of your Brightwheel billing cycle so the parallel week falls in a period you've already paid for. PebbleDesk Center at $50/month flat keeps the new-system cost predictable.
Q&A
Will switching off Brightwheel affect my state licensing compliance?
Not if attendance records are exported and imported intact. State licensors care about the continuity of the record, not which platform holds it. Keep the Brightwheel export archived as a backup for at least 12 months after the cutover in case an auditor asks for historical data.
Q&A
How do I tell parents we're switching off Brightwheel?
Send one clear email 2 weeks before cutover, a reminder 5 days before, and a same-day login guide. Lead with the why (better compliance tooling, better value), not the how. Parents do not care about your software; they care about photos, messages, and billing. Reassure them those work on day one.
Like what you're reading?
Start your 1-month free trial. Credit card required. We email you 3 days before the trial ends.
Start 1-Month Free TrialWant to learn more?
1-month free trial. Credit card required. We email you 3 days before the trial ends.
Frequently asked