Getting your records out of what you're on now

What gets moved

Everything we can read. In practice that usually means:

• Children, guardians and their contact details
• Enrolments, bookings and session patterns
• Historic attendance, which is what your funding claims rest on
• Staff records, certifications and expiry dates
• Outstanding balances, so nobody's account resets to zero
• Sites, licence conditions and capacity

If your current system exports it, we can almost certainly import it. If it doesn't, we will tell you that early rather than after you've signed.

How it runs

1. We look at what you've got

Before anything is agreed, we take an export from your current system and check what is in it. That tells both of us what will come across cleanly, what needs tidying, and what will have to be re-entered.

2. A trial load you can check

Your data is loaded into your own Oversite environment first, so you can look at real records, meaning your children, your rolls and your balances, before committing. Finding a problem here is cheap.

3. Training while it's still parallel

Your team is trained on your own data rather than a demo, before you rely on it. Kiosks get set up on the tablets you already have.

4. A final load, then go live

A fresh export is loaded on the agreed date so nothing recorded during the crossover is lost, and the old system stops being the one that matters.

How long it takes

For a single site, usually a couple of weeks end to end. For a group of ten or more, plan on four to six weeks, most of which is checking rather than waiting.

The pace is set by how quickly your data can be checked by people who know it. That is not a step worth rushing, and it is the one part we cannot do alone.

What it costs

Nothing beyond the per-site price. Onboarding, training and moving your existing data across are included, at every size.

The twelve-month agreement is billed monthly with nothing collected upfront, so there is no large payment to find at the point where you have done the work and not yet seen the benefit.

What your team has to do

Less than you'd fear, but not nothing. Someone who knows your data needs to check the trial load, and your team needs to attend training. We do the rest.

The one thing worth doing before you start is deciding who owns the decision at your end. Migrations stall on approval, not on data.