A proper transition to those systems includes talking to each team that will be using it, breaking down all their workflows, and making sure that said system works with practices in place (a new system that causes everything to take 20% more time is not okay). It also includes maintenance plans; every bit of information planning I do also includes 'this is how you maintain this system/this is the parts that will require effort to maintain/this is what will happen if you decide not to do any maintenance whatsoever, which I do not recommend'.

Documentation management and information architecture planning is work, and properly planned your maintenance will be minimal (NOT non-existent, but minimal) because the system will be designed to be as frictionless as possible.

But nobody wants to either pay for that or accept the time it takes.