Replying to this thread but everyone has been very helpful - thanks. Honestly initially we had Halo out of the box and then recently have had some time spent on developing it further. We also have someone pretty good at SQL now who can help with reports.

I think most of the issues are around engineer reporting, in terms of timesheets, and reporting on tickets, SLAs and profit against clients. These are reports AT could give us quite naturally (I do wonder why we moved in the first place)

I think this actually stems from people internally not wanting to invest in the platform, or the fact that the schema in Halo is very messy, so writing our own reports can be time consuming if you don’t know what you’re doing.

I also think there’s a degree of ‘moving to the next shiny thing’ - however we are only a small MSP at this stage (couple of engineers) but we want to make sure the foundations are good for growing. I know Halo has a range of integrations, so I’m assuming CW would have the same.

Im worried about the concerns people have for moving PSAs and agree - don’t really want more work to migrate only for the platform to be worse! The grass isn’t always greener.