Final Report [Template and Examples] 10/10/2017 Upgrading Microsoft Dynamics 365 Final Report [Template and Examples] Findings and Recommendations Summary © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Please read this first: How to use this presentation This template of the final deliverable for Upgrading to Microsoft Dynamics 365 Planning Services includes slides which describe the required content for each of the engagements lengths deliverables Content which is included on some of the slides is there as an example, in order to give you an idea what content you should include in order to submit a compliant deliverable. You need to replace the content with content which is relevant to the specific customer engagement. If your company has a deliverable template which includes similar components you can submit your deliverable as it was delivered to the customer. But make sure that your delivery to the customer includes the required components. Include in your deliverable the relevant sections, depending on the length of the actual engagement delivered to the customer (see names of the section) 3 days engagement requires the first section (slides 5-9) and final recommendations section. 5 days engagement requires the above and the second section (slides 10-28). 10 days – same as 5 days and the third section covering FUNCTIONAL ASSESSMENT findings (29-38) + final recommendations section 15 days – everything mentioned above + forth section of the PoC summary

Table of Contents Executive summary Findings Summary 10/10/2017 Table of Contents Executive summary Findings Summary Business and IT goals Technical Assessment Findings Functional Assessment Findings and Recommendations Proof of Concept Summary Final Recommendations and Action Plan © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Executive Summary

Executive Summary Add text here Add text

Findings Summary

Business requirements Summary of top identify business requirements for upgraded solution Add text

Upgrade considerations Add text here Add text

Upgrade vision and recommendations Add text here Add text

Assessment findings

Technical Upgrade Requirements Business Challenges Recommended Assessment Components Upgrade should enable business growth and expansion Safeguarding IT investments in Dynamics as an CRM Platform Business continuity and supportability of the Microsoft Dynamics 365 Improving ROI for Dynamics 365 solution Adhering to compliance requirements(Localization) Need for latest Best Practices Integrated CRM Solution instead of multiple systems Improve ineffective interfaces and redundant customization Improve performance of application to enable user productivity Deploy a global instance supporting growth in multiple countries Continue with CRM and harvest investments made in previous years in user adoption, custom development and IT Reduce solution technical debt and IT maintainability cost, improve flexibility Increase functional footprint with new feature capabilities to improve ROI Improve CRM implementation performance Workflow, Policy Frameworks and better reporting capabilities in the current version of Dynamics 365 Gain more business insights and productivity using new functionalities of Microsoft Dynamics 365 2015 Ability to drop redundant customizations and replace with out of box functionality Improved performance of application and support on SQL Server 2012 For report template capture: Identified upgrade challenges risks involved, Outline of upgrade approach for the solution Optional key upgrade scenarios and analysis of them Propose options for data upgrade

Current Solution Implementation Landscape Add text here Add text

Proposed Upgraded Dynamics 365 Landscape Add text here Add text

Summary findings Some unsupported customizations found Mitigation: Replace unsupported customizations by supported customizations or new Microsoft Dynamics 365 features. Use of heavily customized system ABC interface as the main interface to Microsoft Dynamics 365 Mitigation: As part of the midpoint workshops compatibility with the ABC was confirmed Heavy integrated CRM landscape using many different technologies Mitigation: Documentation and aim to streamline the integration landscape (i.e. by making CRM the master system of customer records). Third Party ISV solutions in use (AgilePoint BPM, Avanade Marketing List component) Mitigation: Re-evaluate need and contact providers to confirm compatibility and upgrade steps as soon as possible (to be integrated in upgrade plan) Size (and growth) of Database Mitigation: Consider to clean up/migrate certain data sets prior to the upgrade. Consider to store attachments in a document management system. Significant Microsoft Dynamics 365 User Interface changes Mitigation: Change management, user training with Microsoft support

Prioritized Business Requirements Add text here Add texe

Initial Impact Assessment – Code Upgrade About the Engagement Upgrade Impact Upgrading all the Dynamics CRM 2011 customizations to Dynamics 365 using a standard Code upgrade process may be expensive as some of those customizations may need to retired or remodeled in Dynamics 365. Recommendation: Customer to list the “Mandatory Must Have” customizations from Dynamics CRM 2011 environment which need to be migrated to Dynamics 365 Partner team will review and recommend the best way to migrate these customizations in Dynamics 365– the approach can be Retire, Remodel or Retain. Microsoft Confidential 16

Key Processes Reviewed Add text here Add texe

Identified Area of Customizations Example Invoice Workflow Contract Management Project Accounting

High Level Upgrade Approach Example - Replace with customer relevant content 0. Current Situation Technical Upgrade to Microsoft Dynamics 365 CCA remains in place – Dynamics 365 quick wins Functional Dynamics 365 release Microsoft Dynamics Marketing Pilot (optional) Microsoft Social Engagement Dynamics 365 Online Migration (schema + data) CUSTOMER integrations compatibility with CRM Online Email Router to Server Side Sync upgrade

Upgrade Path Microsoft Dynamics 365 Recommended upgrade path to meet business requirements and technical findings Microsoft Dynamics 365 Microsoft Dynamics CRM 2015 Microsoft Dynamics CRM 2013 SP1 …Microsoft Dynamics CRM 2011 Migration Microsoft Dynamics 365 Technical Assessment Functional Assessment Findings and Recommendations + Roadmap Upgrade Project Migration Project

Detailed Technical Assessment Findings

Customization by Type

Entity Customization

User Per Role

Customizations Per component

Code Assessment Findings Workflows – Green Plugins - Green Custom Code (3 must change) JavaScript (7 must change – 94 should change) See “Detailed Findings customerABC.xlsx” for details

Integration Requirements Findings and Actions Add text

Other Considerations and Challenges Data base sizes Record Count Table size Performance analysis

Functional Assessment and Fit-Gap Analysis

Recommended Upgrade Approach

General Functional Findings Many customizations in certain key areas (Case – Marketing) Aim to replace certain customizations with new Dynamics 365 out of the box features. Configure before customize going forward. CRM is heavily integrated in the ABC IT landscape Master data management strategy. Aim to replace systems Three CRM instances exist (A, B, C) 3 vs 1 instance discussion General sentiment that current marketing processes do not work inside CRM (= users don’t see an advantage of using CRM) Proposed to re-use ‘quick wins’ Implement Microsoft Dynamics 365 for Marketing pilot to rethink segmentation strategy and landscape Aim to have a customer 360° is there, but departments still work separate sometimes (marketing and sales areas) Aim for integrated scenario’s i.e. when a customer sends a question about a product he has shown interest in in marketing (newsletter or landing page), try to upsell

Example Process Assessment - existing Process Description: Add relevant description Key Functionalities and Customizations Add relevant content

Example Process Assessment – upgraded Process Description: Add relevant description Key Functionalities and Customizations Add relevant content

Process Business Requirements and Degree of Fit Add content

Key New Functionalities to Implement Add content

Key Functionalities to Replace Customized Code Add content

Other Functional Considerations and Degree of Fit General Business Rules Add General System-Wide Requirements Integration Requirements Data Migration Requirements Requirements Security Requirements

Additional Functionalities to Consider [ADD specific functionalities of Dynamics 365 that can be helpful for the business as a whole and describe each and its benefits for the specific customer]

Proof of Concept Description

Proof of Concept Description Add text

Summary Findings

Summary findings Add text

Summary and Next Steps

Action Plan and Priorities Initiatives Next Steps High Replacement of retail back office Requirement and process review, scoping assessment Date: Low Replacement of POS system None Medium Omni-channel platform Proof of concept Optimization of supply chain Demo ... <Initiative overview> <insert here action items>

Next steps Use this slide to assign names and dates for next steps Action Item Assigned to Due Date