Successful email migration projects need a well-designed platform from which to deliver your mailboxes, calendars and collaboration apps.
Depending on your organisational needs and goals, data security requirements and regulations, your enterprise must consider you could end up with a odd mix of cloud based and on premise mailboxes, file and folder structures, mobile devices and other collaboration tools. This is why the right amount of time should be spent understanding what MS Office 365 can support and the process steps required to move to it.
It is advisable to estimate your target numbers for the migration and to size your infrastructure accordingly to be able to manage your migration as smoothly as possible. In addition, you should consider:
- Does any of your existing email management infrastructure need to be updated and upgraded before migration?
- What about your deployment technologies and supporting systems such as Sharepoint?
- Are you planning to improve asset management processes and get the environment into a healthier state prior to migration?
- How will switching to Office 365 impact your current collaborative technologies such as video conferencing and VoIP?
- How will switching to Office 365 impact your current infrastructure, storage, client environment, remote mail access, and archive methods?
These considerations can come up too late, like when the project is already well underway. If that happens, the initial project scope, budget, and resources have to be adjusted which causes the foundation of the project to start to deteriorate. Set yourself up for success by considering these critical questions at the outset and set realistic targets from the start.
There are many roadblocks you can run into with a large Office 365 migration. To avoid running into those, here are some of the questions you should ask in your planning phase:
- Which users belong to groups or are delegates for one or several mailboxes?
- Which mailboxes will be moved to the cloud and which stay on-premise?
- Where is my local Office data stored?
- How much storage and network capacity will be needed?
- Where are local archived mailbox data files (PST files) located?
- Will I determine application usage to decide which to take forward?
- What will be my testing and sign-off process?
- How will I perform business user-acceptance testing?
- How will I refresh my dependent application readiness data into the project?
- How will I manage the deployment of applications and 365 dependent updates to my users?