> Do note that during the pilot phase, the new system runs in parallel with Microsoft 365 rather than replacing it outright. That's okay, I think.
Well I think it's not ok without at least a fixed deadline for removal of MS365. People usually have work to do and learning new ways to get it done means extra work, and (almost) nobody takes upon extra work if they don't have to. So the new software will be largely ignored by default.
> Well I think it's not ok without at least a fixed deadline for removal of MS365
I guess that when you "test" something, it means that you have not yet decided that you will completely migrate there?
That's the problem, nobody is going to test the new software unless they have to, it will sit unused until the end of the pilot period as long as the old software is available too. Those people are no cs nerds who like testing new software, they are office people and learning new tools is stressful for (most of) them. I have been there.
I worked in Switzerland for 5 years in the 1980’s before Windows when the IBM PC/AT’s I ordered ran DOS with my own menu software. (And my father who fought in WW2 asked “Didn’t the Swiss allow sealed troop trains through their country?”, but that’s not my topic.) Anyway, I once installed a new version of WordPerfect alongside the old version, guess which version was never used? And the poor secretary who accidentally ran the new version couldn’t work with her old files & went home crying for 3 days. I was blamed for not explaining things, but I was sure anyone could tell the difference between the old & new versions - no, they evidently could not.