Published on April 7th, 2022
2 min read
Most of the functionality in Microsoft 365 exists to improve the way people work. Specifically, much of it directly solves problems people currently struggle with.
If you're not super clear on what the current pain points are, you're going to do a bunch of technical work without perceived value.
Examples of pain points directly soothed by migrating to M365 include:
When you solve a pain point, celebrate and promote it. This is one of the best ways to get people on your side.
Microsoft 365 opens up a whole new world of content interactivity, but this level of interactivity and shareability depends on whether you're using the containers best suited to each specific purpose.
Dedicating time to a thorough content audit and mapping to find the best destination for each purpose is critical to avoiding frustration later on.
You can plan the technical migration of content as thoroughly as you may think is necessary, but if you haven't tested each migration scenario with a pilot run, you'll be dead in the water when you can least afford to be.
Just a few snags which could lurk beneath the surface of content sources which may seem straightforward at first:
To avoid this pitfall, build and run a pilot for each individual migration scenario, even those you think are small and easy.
Optimism is great, but production migration slots are not the time to be a hero.
Your attempt to migrate 500GB from various sources to SharePoint and OneDrive over a weekend may seem realistic in the weeks leading up to it, but you don't know how many connectivity, throttling or unknown mapping issues you'll encounter late at night.
Give yourself all the buffer you possibly can and break migrations into batches at different times if you can. Rome wasn't built in a day.
Tip: Running pilot migrations beforehand will help you improve your duration accuracy and enable you to create a playbook to handle issues you discover.
People become very used to working in certain ways, even if they claim they're ready for change.
You don't want a high-ranking exec undoing a switch from a file share to SharePoint Online because they're not willing to start using the browser to interact with their files.
A few ways to manage change:
Want to talk about how we can help?Drop us a message in our chat widget and we'll get back to you soon!