We published our first blog here with the facts about the right way for schools to conduct data migration when they change provider to correct misinformation on this issue, and better inform the discussion. Unfortunately, we continue to see other industry players circulate misinformation.
This is not helpful for schools. We want to ensure the facts are set out clearly. We are happy to talk to any schools if they are unclear what this means for them.
It is important everyone understands that our focus is on the inappropriate conduct of other MIS vendors and not schools. Schools are run by hard working and responsible people who would not contemplate doing the wrong thing or knowingly breaking an agreement with anyone. It has been surprising and concerning to see other MIS vendors doing just that, and then see them ask schools to do the same thing. These companies have then offered to cover a school’s legal costs on some unexplained basis as if that makes this OK.
We would urge all schools still unclear on their options to talk to us first. After that they should seek genuinely independent advice from consultants who they have confirmed are not affiliated formally or informally with a particular vendor. There’s a lot of so-called independent advice or ill-informed commentary circulating at the moment which is not helping.
We remain optimistic that when faced with the facts these other MIS vendors will stop defending the indefensible and concentrate their efforts on just following the long-standing rules. Putting their energies productively into complying with our migration process so schools that do still want to change MIS can do this safely and appropriately.
We’ve been following the online discussion on this issue and thought it helpful to comment on the most common repeating themes we’ve spotted so far. Thank you for reading.
SIMS supports schools who want to move their data or change MIS.
If a school decides to change MIS, they need a safe, reliable, easy, and appropriate way to move their data. It is their data after all. That’s why we provide MIS vendors with access to the tools and process they need to do this properly. Some MIS vendors have chosen to do things improperly, and now this has been identified, we’re simply asking them to stop and follow our process.
It suits others to suggest we are making things difficult, but this is not true. We only ask that these companies act safely, properly, and don’t infringe our Intellectual Property (IP) – entirely reasonable things to ask.
Our concern is with the MIS vendors whose conduct is poor and not the schools that have made a considered choice to change technology. Schools are diligent buyers and now they know the facts they will ensure that any provider they contemplate moving to has a compliant data migration process. We are here to help these schools with their migration and with advice.
Our data migration methods are easy but also a safe, reliable, and appropriate way to move sensitive school data.
For more than a decade migrating data from SIMS has been possible using SIMS Application Programming Interfaces (APIs). Alternatively, a school can use our reporting facility or work with aggregators such as Wonde or Xporter (previously GroupCall Xporter) to extract the data for them.
Legitimate access to school data is freely available and easily workable. It is not right, and there is no need, for other MIS vendors to request a copy of the database to migrate data for schools.
Let’s start with the easy point. Some MIS vendors have claimed that using ESS databases for migrations is more convenient than using SIMS reports or APIs. Putting aside the fact they know it is not permitted and that convenience is no defence for doing the wrong thing, we don’t agree that it is easier. ESS’ tools and our processes have been available for many years. ESS’ partners use them to extract billions of data items from SIMS every month. They are perfectly viable means of obtaining school data.
Now for safe and reliable. Copying databases is not safe because scripts or programs written by others to extract data directly from a SIMS database can’t guarantee the integrity and accuracy of the data they extract, and there is no guarantee that they will continue to extract data correctly over time.
Finally appropriate. A SIMS database contains over 1.5 million lines of ESS program code and other valuable ESS IP. Alternative MIS vendors have no need or right to obtain or use it and to do so infringes ESS’ IP.
For these reasons direct extraction of data from a SIMS database or a backup copy of a SIMS database is unsafe, unsupported by us, and infringes ESS’ IP rights.
ParentPay Group is delivering cloud innovation for SIMS now and is committing very significant investment in its development.
Since acquiring SIMS, we have been investing heavily in both cash and people in cloud development. We have already invested £25M in the development of SIMS Next Generation (SNG). SNG is our new look and features for SIMS in the cloud. Over the next three years alone, we expect to invest a further £55M in SNG, FMS (finance), and further innovation across the wider ParentPay Group portfolio of payments, messaging, and parental engagement technologies that will also benefit SIMS customers.
The first SIMS Next Generation modules and features are with schools now, with further new features being released every term. Nearly all existing SIMS customers are entitled to use core SNG modules now, at no additional cost as part of their existing contract.
SNG received a very positive reaction from schools at the Bett edtech show last month. What people particularly liked was that with SNG you can add these innovative cloud capabilities to your existing SIMS systems today. SNG works alongside, and shares data seamlessly with, your current SIMS software (on-premises SIMS 7 or in the cloud with SIMS Connected). With SNG you get to move to the cloud at a pace that works for you with no disruption, no data loss, and no large-scale retraining.
Plus, we are delivering completely new functionality such as performance dashboards with SIMS Group Analytics for MAT leaders, and Seating Plans and Fire Registers for teachers and administrators – all available this term.
Migrating school data and copying or direct extraction from SIMS databases are not the same thing.
Some commentators are intentionally or accidentally confusing these two things. Schools can get their data when changing MIS. I’ve explained how this is possible. You don’t need to copy the SIMS database to do this.
It is not necessary, safe, or right for any third party to ask schools to provide a copy of their SIMS database during a migration.
It is not safe because scripts or programs written by others to extract data directly from a SIMS database can’t guarantee the integrity and accuracy of the data they extract.
It’s not right because a SIMS database contains over 1.5 million lines of ESS program code and other valuable ESS IP. These companies have no need or right to obtain or use it, and to do so infringes ESS’ IP.
For these reasons, direct extraction of data from a SIMS or FMS database or a backup copy is unsafe, unsupported by us, and infringes ESS’ IP rights.
But this is different from claiming we want to stop schools getting their data. We don’t want to stop schools getting their data and we aren’t.
We did not know MIS vendors have been asking schools to take copies of databases during migrations. We believed they were following the rules.
When ParentPay acquired ESS, we were not aware that some MIS vendors were asking schools to provide them with copies of the SIMS database as part of MIS migrations.
As long-standing users of the SIMS APIs, ParentPay reasonably assumed that anyone wanting to extract customer data from SIMS would be following the rules and either use SIMS reports, write programs that used the APIs, or engage with aggregators.
Our understanding of the migration process was that schools made a backup copy of the SIMS database and then either produced XML reports from this copy or provided an ESS technical integrator with API access to the copy for the purposes of programmatic extraction.
This remained our understanding until October 2023, when we obtained actionable evidence that certain competitors were not operating appropriately. We wrote to them in December 2023 requiring them to stop, but despite this, they apparently continue to encourage schools to provide them with SIMS databases.
One of these companies has been an ESS technical integrator with access to the SIMS APIs for many years. Another has recently approached ESS to become a technical integrator to access the APIs.
We regret needing to pursue these organisations and would much rather they simply opted to put their house in order, but they have unfortunately focused their energies on justifying their conduct rather than resolving it.
SIMS welcomes fair and appropriate competition.
Competition is good and drives innovation. We welcome fair competition. But fair competition requires all companies to operate appropriately – this isn’t a radical or complex concept. Using or copying ESS’ IP without permission is not something we can accept. As explained, appropriate means of data extraction are available, and the misuse jeopardises the integrity of schools’ data.
It suits some MIS vendors to try and conceal their misuse of ESS’ IP with a smokescreen of allegations of anti-competitive behaviour. To paint themselves as the victims. They are not.
ESS provides lawful, safe, and authorised means for its competitors to migrate data from SIMS, which our competitors have ignored, instead choosing to access our program code and not just school data.
Other MIS vendors do not make it easier than SIMS to move from their MIS.
In our experience, when we move customers to SIMS from other MIS vendors, the migration options are more limited and onerous, and we’ve not used nor had the option to use a database copy.
We give MIS vendors, schools, and partners multiple ways they can migrate their data safely. We would ask other MIS vendors to make it as easy for schools to leave them as we have made it for them to swap from SIMS.