Is September Really the Wrong Time to Switch Daycare Software? Here's What That Advice Actually Assumes

Every before-and-after-school program registration in Ontario becomes effective the same week: the week of September 1st. Whatever system a program is using, every family in it starts at once, on the same date, whether that system is ready or not. Centre-based programs feel a version of the same thing — a new cohort arriving within days of each other, all needing profiles built, baselines established, and a program running from day one.

If you've been thinking about switching software and you keep running into the same advice — don't do it during enrollment season, wait for Q4 or February — it's worth being precise about what that advice is actually protecting against. Because for the kind of switch most supervisors are actually considering right now, it may not apply the way it sounds like it does.

What the Standard Advice Actually Says

The consensus among people who run childcare software implementations is consistent: the best time to switch is typically the last quarter of the year or February, rollouts should be planned around enrollment cycles to avoid overload, and a full transition — data migration, staff training, a parallel-run period — commonly takes weeks to months. Running the old and new systems side by side for 30 to 60 days is a common recommendation to reduce risk.

This is sound advice. It's just advice about a specific kind of switch: replacing a billing, attendance, and enrollment management system — the system holding years of family payment histories, tuition schedules, attendance records tied to subsidy reporting, and enrollment data that a CMSM or DSSAB may reference. Ripping that out and replacing it mid-cycle genuinely is risky, and genuinely does take real vendor coordination and parallel-run time to do safely.

What That Advice Assumes — and What It Doesn't Cover

Here's the assumption baked into "wait until February": that switching software means migrating a large body of existing historical data out of one system and into another, correctly, without losing anything a funder or a family might need later.

That assumption makes complete sense for billing and attendance software. It doesn't automatically apply to a program planning and documentation tool — the layer that handles ELECT-aligned weekly plans, developmental observations, and AQI readiness tracking, sitting alongside whatever billing system a centre already uses.

Here's the distinction that actually matters: a new cohort of children starting this September doesn't have five years of billing history to migrate. They have zero history in any system, in any tool, anywhere. Their child profile, their first observations, their baseline ELECT-aligned plan — all of that has to be built from scratch this month, regardless of which tool ends up holding it. That's not a switching cost. That's a cost every centre pays either way, in a new tool or in the same Word documents and paper binders it's always used.

The real question isn't "should we avoid building this in a new system." It's "who's actually doing the building — us, manually, from a blank page, or the tool, from the registration paperwork we already have."

What Root Skills Actually Changes About That Math

This is where the specific mechanics matter. Import from Forms takes the registration PDFs a centre already collects for every new family and drafts each child's full profile from them the same day — name, schedule, allergies, dietary needs, strengths, challenges, and parent notes included, not just contact details. For a September cohort of ten, fifteen, twenty new children, that's the difference between a week of manual data entry and an afternoon of review.

From there, Weekly Plan's "from observations" and "from theme" generation modes give a starting program for the new group immediately, instead of a supervisor building nine ELECT learning areas across five days from a blank page while also handling the rest of a new-intake week.

None of this requires migrating anything out of a legacy system, because there's nothing to migrate for a brand-new cohort. It requires building it once — and the question is just whether a person builds it by hand or a tool builds the first draft in minutes.

Where the Standard Caution Still Applies — Honestly

To be fair to the advice this is pushing back on: if your centre needs to replace its actual billing, tuition, and attendance system — the system with years of family payment history and subsidy reporting tied to it — the standard caution is correct. That's a real migration, it carries real risk, and September, during your highest-volume enrollment week, is a legitimately bad time to attempt it.

It's also worth being direct about what switching to a new planning and documentation tool doesn't instantly solve: historical observation notes sitting in your old system or paper files don't automatically appear in a new one — that's still a manual carry-over for existing children, room by room, at whatever pace works for your team. And staff still need a short runway to learn a new interface, even one built to be simple. Neither of those is the multi-week, high-risk migration the standard advice is warning about — but they're real, and worth planning for honestly rather than promising a zero-effort switch.

Frequently Asked Questions

Is it actually risky to switch childcare software during September? It's genuinely risky to replace a billing, attendance, or enrollment management system during your highest-volume month — that involves migrating real historical and financial data. It's a different situation to add a planning and documentation tool for a new cohort that has no historical data to migrate in the first place.

Do we need to migrate our existing children's records into Root Skills? Historical observation notes and past planning records from a previous system or paper files don't transfer automatically — that's a manual carry-over you do at your own pace for existing children. For new children starting this fall, there's no legacy data to migrate at all; their profile is built fresh, the same day, from the registration form.

How long does it actually take to get set up? Import from Forms drafts a new child's full profile from their registration PDF the same day it's uploaded. Getting a September cohort's profiles built is a matter of reviewing AI-drafted profiles, not typing them in from scratch — measured in an afternoon, not weeks.

Should we run Root Skills alongside our existing childcare software? Yes, for most centres. Root Skills handles ELECT-aligned planning, observations, Quick Guide, and AQI readiness — it isn't a billing or attendance system, so there's no need to replace what you're already using for tuition and enrollment management.

What if we're not ready to fully commit before September? The 14-day free trial, no credit card required, is built for exactly this — set up a room or two with your incoming cohort's registration forms and see the profiles and first week's plan before deciding anything.

The Bottom Line

The advice to avoid switching software during enrollment season is right — for the system holding your years of billing and attendance history. It was never really about a program planning tool being introduced for a brand-new cohort that has no history to migrate in the first place. Every centre is building September's child profiles and program plans from scratch this month, in whatever tool they're using. The only real choice is whether that building happens by hand or starts from an AI-drafted first pass.

Root Skills is built for exactly this moment. Free 14-day trial, no credit card required. Starting at $129/month.

Start your free trial at rootskills.ca

Sources: TDSB and Ontario school board before/after-school program registration guidance (registrations effective the week of September 1st, via OneList-based waitlist systems); Kindertales, "Adopting New Childcare Software"; LineLeader, "Preschool Administration Software: What Directors Should Look for Before Switching Systems"; MyKidReports, "How to Switch Childcare Software Without Losing Your Data." This post reflects standard childcare-software implementation guidance as of mid-2026.