RETIRED CONTENT
Please note that the content on this page is retired. This content is not maintained and may contain information or links that are out of date.If you resist moving to Office 365 you will see:
- High overhead for maintaining the supporting infrastructure for SharePoint, Exchange, and Office.
- SharePoint does not meet user needs.
- Users are going rogue for mobile content creation.
Moving to Office 365 can:
- Reduce long-term infrastructure spend.
- Optimize resourcing for SharePoint and Exchange.
Book Your Workshop
Onsite Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn’t enough, we offer low-cost onsite delivery of our Project Workshops. We take you through every phase of your project and ensure that you have a road map in place to complete your project successfully.
Module 1: Evaluate Office 365 needs
The Purpose
- Define the realistic cost of Office 365.
- Evaluate key metrics for Office 365 value.
- Define organizational future needs for Office 365.
Key Benefits Achieved
- An understanding of the benefits and drawbacks to Office 365.
- A clear view of your spend with Microsoft.
- Define the capacity and use of key Microsoft licenses.
Activities: | Outputs: | |
---|---|---|
1.1 | Define the current needs for content based on user needs. |
|
1.2 | Evaluate the growth of information in the organization |
|
1.3 | Map the gaps in your current strategy |
|
Module 2: Build a roadmap for Office 365
The Purpose
- Identify technical gaps for moving to Office 365.
- Identify key infrastructure time points.
- Combine the organization needs with best practices for Office 365.
Key Benefits Achieved
- A complete timeline view of the projects needed to implement Office 365.
Activities: | Outputs: | |
---|---|---|
2.1 | Define the current IT skill set |
|
2.2 | Define when storage will be a critical concern |
|
2.3 | Set start and finish dates for Office 365 |
|
2.4 | Build a timeline |
|