I have seen the same story in more than one institution. A learning platform is purchased or installed, a launch event is held, logins are created, and six months later almost nobody is using it beyond uploading a few PDFs.
The platform was not the problem. The problem was that the project began with a tool and went looking for a use. Real adoption starts somewhere else: with a specific friction that teachers or students already feel. Marks that take three weeks to compile. Notes that never reach students who missed a class. Parents who cannot see how their child is doing.
When you start there, the questions change. Instead of asking which features the system has, you ask who will use it every day, what they do today instead, and what has to be easier on day one for them to switch. Those answers shape everything, from the interface to the training to the support you provide.
A few habits that have served me well. Pilot with a small group that wants to try it, and fix their complaints before expanding. Make sure someone owns support, because a broken login on a Monday morning can end an entire rollout. And measure what matters, not how many accounts exist, but whether the thing it was meant to improve has actually improved.
Technology is the easy part. People, habits and incentives are the project.