Skip to main content

Migrating from Parature to Microsoft Dynamics 365: Part 3

The discontinuation of Microsoft Parature is just over two weeks from now, so presumably nearly all customers have chosen a new software platform for customer service and migrated to that platform.

Many customers likely chose Microsoft Dynamics 365.  They may have picked Dynamics 365 because it comes from Microsoft, and they can receive credit from Microsoft for any Parature subscriptions which were purchased but cannot be used due to the discontinuation of service.  They also may have chosen Dynamics because of the integration with Office 365 and other Microsoft products.

It may have come as a surprise to some customers that Dynamics 365 is not at all similar to Parature, even though Microsoft progressively implemented new features in Dynamics 365 to replace the functions that Parature provided.  Here are some of the ways that they are different:

  1. Dynamics 365 is a broader platform than Parature.  In addition to customer service it offers sales, marketing, field service, project management and other apps (not to mention accounting in the ERP side of Dynamics 365).
  2. Dynamics 365 is built on the Microsoft developer stack which is much more well known than Parature, so it is more broadly supported.
  3. Some Parature features that seem simple require planning, design and implementation in Dynamics 365.  Parature embodies some assumptions about how customer service representatives behave, such as grabbing tickets and generating emails to customers triggered by many actions on the tickets.
  4. The nomenclature of Parature and Dynamics 365 are different. It takes a while to get accustomed to talking of cases instead of tickets, for instance.
  5. Microsoft no longer offers live chat which was included in Parature.  Instead, CafeX Live Assist add-in is available from a third party vendor. 
  6. The portal technology is quite different in Dynamics, with many options that did not exist in Parature. 
Nothing lasts forever, and this is particularly true for products acquired by software companies. For software deployed on premises, customers can keep going with an old product even as tech support dwindles or is dropped altogether.  It doesn't work that way for cloud services. 

I hope all Parature customers have made it to their new platform or are in the final stages of migration as of May 1. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises