failed migration to Bromcom - registers not saving

[taz]

Our migration to Bromcom has failed - we are unable to save any attendance registers. We mark the screen but it is not saving to the database - absolute nightmare and failed launch. Bromcom say "few issues with registers for newly migrated schools known" but no fixes forthcoming. Has anyone else had this problem and if so, how did you fix it please? I advocated so strongly for Bromcom - am so disappointed they aren't more concerned.Our third party support have been excellent in chasing it up but nothing they can do unless Bromcom can resolve at their end.

Edited January 29, 2025 by taz

[kevin_lane]

I would keep pushing the support, like us you paid for a product that is supposedly better than what you had before.

 

We use to be sims locally hosted, and at least when there was something wrong I could try and sort it, now it’s out of my hands and have to rely upon them trying to fix it.

 

But I would just keep pushing it with their support remember it’s a legal requirement for schools to register pupils and a safeguarding issue so they need to be sorting it

 

Hope they get to the bottom of it for you quickly other wise staff will have to do paper registers, if your not doing that already

[PotNoodleTech]

Don't pay them until it's resolved.

[Oaktech]

Call support and basically don't hang up until someone is actively looking at it for you.

[Bromcom_Darren]

Good morning,

 

Please drop me an email on [email protected] and I will ensure this gets investigated as a matter of urgency.

 

Thanks

Darren Moody

Community Manager

[taz]

We are now underway for a second launch tomorrow - wish us luck!

[PotNoodleTech]

Good luck hopefully it was just a blip!

[supportman]

Good luck, it will be worth it in the end once it all settles down.

[Bromcom_Darren]

We are now underway for a second launch tomorrow - wish us luck!

 

Good luck, if you need me for anything, please do not hesitate to shout.

 

Thanks

Darren Moody

Community Manager

[taz]

*update*

Firstly, thanks to everyone who gave advice, much appreciated. We did manage to go live 2 days later than planned. Since then, all has gone well. If I had read this post when choosing an MIS this would have put me off. So I just wanted to be fair - the day I wrote this was the most stressful day of the project and the point at which we were unfortunately the most let down. However, there were factors in the background:

 

 

- as some have mentioned, Bromcom support is just a no go zone. Get yourself third party and you will be fine. Be aware there is a weird DMZ between them however - third party cannot help until you go live; after you go live Bromcom will not help you. So if you have an issue that sits in that middle zone of the actual go live, you are stuck no matter what reassurances Bromcom give you beforehand. Your third party can only ask Bromcom for help but that is up to Bromcom to give it - they have no leverage in that.

 

 

- our Bromcom Project Manager largely did not follow up on issues raised and disappeared completely 1 week before go live. Our case was not picked up by anyone else and we only made it because others managed to call in a favour. Not sure how it was missed that a site was going live.

 

 

- we never got an answer on what went wrong with our registers. In our case I methodically undid every change we made to go live, until on the second morning, we could take registers. I don't know if that is a coincidence or if something was fixed at Bromcom end. I suspect the key change was around automated rebuilding of the timetable after a change is made (if you are in the same boat, just DM and I will provide more info) but that is just a guess.

 

 

- Darren from Bromcom did reach out and offer to support if we DM (which we didn't as we were live at that point) but it did show they are listening in the forums, which is appreciated

 

 

So all in all, these were exceptional circumstances - at the root was a poor onboarding experience with one individual who was unfortunately a key one, and a process failure in picking up cases if a PM is absent. Being fair again, I know others had great experiences and felt very supported by their PM so I believe we were the exception rather than the rule. We met some very helpful people too, e.g. our Bromcom sales manager (Lizzie) went above and beyond to help us raise the alarm; onboarding engineer (John) helped with technical questions, Lydia and Steph managed to get our live site back to us with seconds to spare.

 

 

If you are thinking about moving to Bromcom, I would still say go go go. I don't regret the decision - one bad experience does not make for an overall bad product. I'm also very happy for anyone to reach out if you would like to ask about our setup or what prompted our choices.

[Bromcom_Darren]

*update*

Firstly, thanks to everyone who gave advice, much appreciated. We did manage to go live 2 days later than planned. Since then, all has gone well. If I had read this post when choosing an MIS this would have put me off. So I just wanted to be fair - the day I wrote this was the most stressful day of the project and the point at which we were unfortunately the most let down. However, there were factors in the background:

 

 

- as some have mentioned, Bromcom support is just a no go zone. Get yourself third party and you will be fine. Be aware there is a weird DMZ between them however - third party cannot help until you go live; after you go live Bromcom will not help you. So if you have an issue that sits in that middle zone of the actual go live, you are stuck no matter what reassurances Bromcom give you beforehand. Your third party can only ask Bromcom for help but that is up to Bromcom to give it - they have no leverage in that.

 

 

- our Bromcom Project Manager largely did not follow up on issues raised and disappeared completely 1 week before go live. Our case was not picked up by anyone else and we only made it because others managed to call in a favour. Not sure how it was missed that a site was going live.

 

 

- we never got an answer on what went wrong with our registers. In our case I methodically undid every change we made to go live, until on the second morning, we could take registers. I don't know if that is a coincidence or if something was fixed at Bromcom end. I suspect the key change was around automated rebuilding of the timetable after a change is made (if you are in the same boat, just DM and I will provide more info) but that is just a guess.

 

 

- Darren from Bromcom did reach out and offer to support if we DM (which we didn't as we were live at that point) but it did show they are listening in the forums, which is appreciated

 

 

So all in all, these were exceptional circumstances - at the root was a poor onboarding experience with one individual who was unfortunately a key one, and a process failure in picking up cases if a PM is absent. Being fair again, I know others had great experiences and felt very supported by their PM so I believe we were the exception rather than the rule. We met some very helpful people too, e.g. our Bromcom sales manager (Lizzie) went above and beyond to help us raise the alarm; onboarding engineer (John) helped with technical questions, Lydia and Steph managed to get our live site back to us with seconds to spare.

 

 

If you are thinking about moving to Bromcom, I would still say go go go. I don't regret the decision - one bad experience does not make for an overall bad product. I'm also very happy for anyone to reach out if you would like to ask about our setup or what prompted our choices.

Good morning,

 

Thank you for your feedback, I am always willing to assist if you need anything please do not hesitate to reach out.

 

Thanks

Darren Moody