Presentation on theme: "Migrate Your Dynamics 365 On Premises to the Cloud"— Presentation transcript:
1 Migrate Your Dynamics 365 On Premises to the Cloud CRM UG BeLux Webinar, December, 14th 2017Stephane Dorrekens, Business Elements
2 CreditsBased on the following content : “Planning your Dynamics 365 Onprem to Cloud Migration” by Nick Doelman “Migrating from the Dynamics 365 App for Outlook to the Dynamics App for Outlook” by Josh Wells “Migration of CRM Onpremise Organization to Dynamics 365 Online using LCS” by Aditya Varma ”Migrating to Microsoft Dynamics 365 for Customer Engagement”, MPN Network
3 Migrate Your Dynamics 365 On Premises to the Cloud OverviewWhy?12 Steps to move from Onpremise to OnlineMicrosoft Lifecycle ServicesLessons Learned & TipsQ & A
4 Why move to the cloud? Why Dynamics 365 Online? No infrastructureMore featuresSmaller, lower impact upgradesSecurityMicrosoft focusIt’s a “when” not an “if”
5 12 Steps to Migrate to Dynamics 365 Online Take InventoryReview and PlanProvision Dynamics 365 OnlineCreate Upgrade Step EnvironmentsBackup Custom CodeDeploy and Upgrade ConfigurationClean Up ConfigurationFix Custom CodeFix ReportsIntegrationsISVs & AddinsMigrate Data
7 Historical Data – Keep or remove? Unmanaged versions of managed Step 2 – Review & PlanningHistorical Data – Keep or remove? Unmanaged versions of managedsolutions?ISVs -> what is their upgrade path?Is now a good time?Start Fresh?Data size and users -> subscription requirements?What custom code can be replacedwith something newer?What reports can be replaced?Is source code available for plug-ins?
8 Step 3 – Provision Dynamics 365 Setup new “target” systemSetup Users -> including historical usersAllocate spaceSetup Sandbox environmentsPoint in Time Backups on Azure
9 Step 3 – Provision Dynamics 365 – Add Legacy Users Create List of LegacyUsersImport Users to Dynamics 365Activity/Transactional Data can be mapped to these users
10 Step 4 – Create Upgrade Step Environments Azure VM, VMWare, or dedicatedserversNext version to latest version that will allow solution importFor solution upgrading (Entities, Fields, Forms, Views)
13 Step 5 – Backup Custom Code Comment out old codefor upgrade processLeave function names
14 Step 6 – Deploy and Upgrade Configuration Import into step environments asrequiredCRM 4.0 can be imported/upgraded to CRM 2011CRM 2011 can be imported/upgraded to CRM 2013Export from CRM 2013 directly toDynamics 365
16 Step 6 – Managed Solutions? Not an ISV, have managed but no unmanaged or even managed zip fileThis will be a hack. This is unsupported. Not for ISVRun process on a “destroyable” database (e.g. not on a production db)Remove all other solutions if possibleRemove plug-ins and SDK stepsRun SQL script, will have “unmanaged” solution that is exportable.4/converting-managed-solutions-to-unmanaged-solutions-crm-2013
20 Step 9 – Fix Reports Dynamics 365 requires reports to be in FetchXML Consider Charts, DashboardsConvert T-SQL to FetchXMLTIP: CRM 2011 or higher, start now! (FetchXML is supported onpremise as well!)PowerBI is the new SSRSStill possible to sync a database copy
21 Step 10 – Fix Integrations Consider timingMost industry standard tools will link to Dynamics 365 with little issuesCannot write directly to database (you weren’t doing that anyway? Right?)
22 Some Hybrid Integration Patterns On Premises To Dynamics 365 Customer EngagementVia WebApi (Latency, #Connections Limits)Via Azure Service Bus or Event Hub (Allows outbound/inbound bandwidth mismatch)*Via an On Premises Queuing/Bus (Allows outbound/inbound bandwidth mismatch & SPOC)*Via Azure SQL (Allows Outbound Direct Database sync)*Via Virtual Entity (Needs Odata Endpoint)…Dynamics 365 Customer Engagement to On PremisesVia WebApi (Data Pull from On Prem/Cloud applications)Via Azure Service Bus (Data Push from Dx365 CE Workflow or Plugin)Via Data Export Service (Data Push to Azure SQL)* All those patterns ultimately uses the WebAPI for injection, the change is in the intermediary steps
23 Step 11 – Update ISVsMost involve installing latest solutions on Dynamics 365Do you still need that ISV? (Features in Dynamics 365)Consider data migrationAre there new feature gaps? (e.g. Portals)
24 Outlook Client Deprecation Dynamics CRM 2013Dynamics CRM 2015Dynamics CRM 2016Dynamics 365 (online),version 9.0Major release (10.0)Outlook add-in supported, nonew functionality is addedOutlook add-in supported, no new functionality is addedOutlook add-in removedDeprecation announcement on June 2017Deprecate the add-in starting version 9.0Removal of the add-in with version 10.0
25 Terminology Outlook client Outlook Add-in Dynamics 365 App for Outlook Dynamics 365 for OutlookOutlook plug-inCOM add-in
26 Feature Comparison Dynamics 365 Dynamics Dynamics 365 Dynamics Feature App for OutlookYes365 for OutlookYesFeatureWorks with Outlook for the Mac Works with phonesOpen and create Microsoft Dynamics 365 record directlyApply custom forms and business logicWork offlineApply templates Apply sales literature Apply knowledge articlesAbility to monitor s aftersendingSort, filter, format, group, and categorize viewsCreate Word mail-merge documentsApp for Outlook YesYes365 for Outlook NoNoTrack and set regarding forTrack and set regarding forappointmentsTrack and set regarding for contactsYesYesYesYesYesNo Yes Yes YesYesYes Yes Yes YesNoYesYesTrack and set regarding for tasks NoYes No NoOne click set regardingShows recipients' summaryShows the regarding record summary in the /appointmentWorks with Outlook on the web YesWorks with Outlook desktop YesYes YesYesNoNoYesNo YesNo YesMore Info see TechNet: Deploy Dynamics 365 App for Outlook
27 Challenges Feature Description Challenge Replies not automatically Replies to previously tracked On the roadmaptrackeds are not automaticallytracked.Tracking icon is not presentWith the Outlook client, the EWS does not allow theon tracked activitiesicon would change from the ability to define thestandard icon to the tracked IconIndex which is used toicon. This functionality is not define the icon.available with the AppDelegate trackingA user has access to another On the roadmapuser’s mailbox and wants totrack activities on behalf ofthe delegated user.
28 Challenges Feature Description Challenge Not able to track meetings Currently only organizers of a meeting can track the appointmentThere are design discussions about handling record ownership between Exchange/Dynamics 365 items.Tracking all typesOnly IPM.Note messageThis is being tracked andclasses where users are inbeing discussed by thethe To or CC fields areproduct teamsupported for trackingTracking signed sSimilar to the challenge above where users are unable to track signed sThis is a limitation from Office addins and feedback has been received for and against
29 Outlook add-in deprecation Version 9.0 contains the add-inNo immediate action necessary, at this pointDoesn't have to be all or none
30 Suggested transition plan Use SSS/Outlook clientAdd App for Outlook for users. Request early adoptersBusiness usage is verified, switch usage to the AppUninstall the add-in for all users.
31 During the transition time Some configurations are not recommended for an extended length:It is not recommended to use the add-in and the App at the same time for tracking purposesIt is not recommended to switch back and forth from Outlook sync to server-sidesyncIt is not recommended to have some users sync with Outlook sync and some users at the same org sync with server-side sync.It is not supported to have two different sync methods (Outlook vs SSS) for the same user at the same time ( /ACT)
32 Step 12 – Migrate Data Microsoft FastTrack/Lifecycle Services KingswaySoft, Scribe, OtherCobalt Migration DynamicsClean up old dataMaybe Fresh Start?Potential for biggest spend of timeConsider downtime or gaps, deltas, etc
34 Planning your Dynamics 365 Onprem to Cloud Migration Microsoft Lifecycle Services
35 Microsoft Lifecycle Services Tool will solveDirect CRM Ingestion up to CRM 2015Database migration up to SQL 2012Migrate Manage SolutionsAudit log MigrationHelp with user & personal settings migrationChecks for security issues/vulnerabilities in the Database & extentions
36 Microsoft Lifecycle Services Tool will NOT solveCRM Upgrade issuesUpgrade is a multi step processSelective data migration is not possible (unless done beforehand)Fix detected security or upgrade issuesISV Integration / reconfiguration
37 Microsoft Lifecycle Services Intake : using existing FastTrack intake process to take the nominationNominator : Account team or PartnerCurrent Target : 250 Users+Managed Process with FastTrack PMPrerequisites :Dynamics 365 tenant & OrganizationAzure Subscription (VMs)User Licenses & RecordsSolutions, Codes, etc.. Ready
38 Lessons Learned & Tips and Tricks A LOT of legacy code can be replaced with portable business logicData migration & integration takes a lot of timeManaged Solution IssuesData clean upHistorical Users
39 Planning your Dynamics 365 Onprem to Cloud Migration Questions?