It was June, and we had just made a very bold decision.
After many years with the same learning management system, we switched to Toddle. Completely. No pilot. No phased rollout. When we came back in August, our old platform would be gone. We had 70 days, and we knew from the moment we made the decision that we were not easing into this but committing to it entirely.
I remember saying to my team, “I have done implementations before. Are you aware of what we are about to do? It will not be easy.” The school year was ending, people were tired, and we were preparing to return in August and hit the ground running on a completely new system.
Why off-the-shelf stopped working
Our school operates across the IB continuum, and our parents, our teams, and our data needs do not fit a standard mould.
Over time, the gap between how we work and what an off-the-shelf system assumes became too wide to ignore. Each programme has its own reporting needs, its own rhythms, and its own expectations of what a system should do. Our parents expect clarity and context. Our teams need to work with data in ways that support genuine analysis, not just compliance.
We were not looking for more features. We were looking for a system we could shape around how we work.
That is where Toddle began to feel different.
#1 A partnership built on context
From the beginning, our conversations involved giving them context for our school system and ways of working. Toddle, in turn, brought in a willingness to understand and build around our needs.
Our ECA programmes are a good example of how that partnership worked in practice. Students needed to enrol across the IB continuum, something the system default did not accommodate. Rather than treating this as a boundary, Toddle asked alongside us whether an existing feature could be repurposed to make it work. It could, and it was.
From early on, the system adapted to us, not the other way around.
#2 Flexibility beyond the standard setup
That same mindset carried through every corner of our academic workflows.
Our Grade 12 gradebooks are fundamentally different from Grade 11, and reporting requirements change year to year. We sat down with programme coordinators and academic leadership and asked how we could get the system to serve our internal processes rather than force us to adjust to them. Each programme was configured separately, and that distinction mattered to us, and it built trust among our teaching teams.
The same was true for parent communication. We wanted granular control over what parents could see and when, and we needed a partner willing to work through that with us rather than offer us a binary choice.
We worked through it together, and Toddle did not set us up and step away.
#3 Going beyond configuration
Data migration was the most complex part of this journey.
We carried years of legacy data. On top of that, UAE regulations require that any student who has ever attended our school can request an official transcript. That meant historical records could not sit in cold storage. They had to remain fully functional and accessible within the system.
Together with Toddle, we split the problem in two.
We separated data we needed to retain for records from data that needed to function actively within gradebooks and reports. Once we separated data, the solution became possible. We built a custom academic transcript system within Toddle that meets UAE compliance standards for both current and former students.
This was the moment that defined the partnership for us. It was the shared responsibility to stay with the problem until it worked.
What changed 70 teaching days later
Jumeirah Baccalaureate School is now fifteen years old, and over that time, various parts of the school have developed different ways of working with systems. What we were looking for was alignment, one shared platform that brought the school together.
A full school rollout across the IB continuum is no small thing. Training was what made it possible, and Toddle showed up for every part of it. Any platform that ignores the fact that teachers have limited time will fail at implementation, and Toddle understood this. We aligned training to our school calendar and to real need, with admin and senior leadership coming first, and teachers focusing only on what they needed for week one. We built from there.
Parents were brought in early, too. Ours is a highly engaged community, and they wanted to understand not just how the system worked but why they should trust it. Toddle showed up for those conversations, and when our principal shared that parents were comfortable and confident with what they had seen, we knew we had done something right.
Seventy teaching days in, we pushed hard and had moments of tension, but nothing has stalled because the system was not ready. The reason is simple: partnership. Our relationship with Toddle has become so embedded that sometimes it is difficult to tell where our team ends, and theirs begins.
If you have worked as a school leader, you know that each school is unique, constantly changing, and growing. Off-the-shelf solutions assume schools are static, but we know (and Toddle does too) that schools are forever evolving. What matters is having a system and a partner that is willing to keep evolving alongside you.
