Skip to main content

Migrating from Parature to Microsoft Dynamics 365: Part 1

Breaking News: Microsoft has updated the release date of the Parature migration tool to the end of September 2017.

In spring 2017, Microsoft announced that it was phasing out its Parature cloud customer service offering in favor of Dynamics 365 for Customer Service, one of the Dynamics 365 apps based on what was previously called Dynamics CRM.  Parature customers and Microsoft partners were informed of this plan in August 2016 prior to the release of Dynamics 365.

Microsoft also announced a toolkit with tools for migrating accounts, files and other assets; templates for creating support portals and customer service workflows; and tutorials and documentation. As of this writing the toolkit is not available, but scheduled to be released at the end of September 2017.

In the absence of a migration tool, what are the steps to migrating from Parature to Dynamics 365?  What are your migration options?

First, you should catalog your Parature implementation to determine which features you were using and where your customer service data resides.  The planning documents from your Parature implementation such as design templates are valuable here.  Your analysis should answer questions such as these:

  • Are you using Live Chat?
  • Does Parature integrate with any other systems?
  • Do you want to migrate all your past data or only a subset of the data? 
  • Do you want to run in parallel during the migration or cut over completely?
  • Will you migrate groups of users separately or all at once?
  • How is authentication managed for your customer service representatives?  You will be moving to the Dynamics 365 authentication which is managed by Office 365 and may be integrated with your domain login. 
Parature includes an export feature which generates delimited text files for data including Accounts, Customers, Ticket data, Phone Calls and Notes, Tasks, Products, Emails, and Knowledgebase References.  You can use the import feature in Dynamics 365 to import these records or a third party integration tool such as Scribe or Kingswaysoft.  Be sure to consider the relationships among the entities that you are importing so that you import them in the correct order.  

Migrating to Dynamics 365 provides the opportunity to take advantage of new features in the Dynamics 365 platform which were not available in Parature.  This is a good time to review these and determine whether to implement them in the initial migration or add them as needed later.  For instance:
  • Should Live Chat be added now if not using before?  Dynamics 365 uses CafeX for Live Chat.
  • What new dashboards and reports would your users like to see?
  • Do you want to make your customer service portal look different than it did when implemented in Parature? 

While Parature provided a complete, integrated customer service cloud, it was not based on the Microsoft Dynamics architecture, and did not lend itself to being as easily or thoroughly customized. Developers with experience on the Microsoft platform in general and Dynamics 365 in particular can apply their skills to reshape Dynamics 365 for Customer Service and also combine its functions with apps those such as Dynamics 365 for Sales, Project Service, or Field Service.

Unlike Parature, the customer service portal is based on Microsoft Dynamics Portal. Configuration settings for the portal are stored in Dynamics 365, and many changes may be made without extensive HTML coding.

The user experience for customer service representatives is quite different in Dynamics 365 for Customer Service from Parature.  The good news is that there is more extensive training material, videos and official Microsoft courseware for Dynamics 365.



Popular posts from this blog

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

Updated 8/15/2022 To understand Microsoft Dynamics 365 (formerly Dynamics CRM) and Power Apps, 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.  These concepts also apply to Power Apps.  The main difference is that with Power Apps you are not starting with a Microsoft app but more of a blank canvas for your custom apps.  This post introduces some key terms and how these concepts are important for planning your implementation. While Dynamics 365 is still 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 in several countries. 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 uni

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

Switching from Microsoft Dynamics GP to Dynamics 365 Business Central

Updated 4/6/2022 Register for our webinar  "Great Plains to Microsoft Dynamics 365 Business Central for Nonprofits." Source: https://docs.microsoft.com/en-us/dynamics-gp/terms/lifecycle This year Microsoft announced a date for the end of mainstream support for Dynamics 365 GP 2018 accounting software.  This spurred some blogs and customers to think that they must switch from Dynamics GP to another product by January 10, 2023 when mainstream support ends. It turns out that this announcement does not cover the latest version which is named simply Dynamics 365 GP (without a year in the product name).  Dynamics 365 GP will continue to be developed and supported indefinitely. Without support, customers cannot continue to use accounting software because it must be maintained in order to comply with changing tax and regulatory requirements.  Microsoft ships these updates in the June and December releases, and adds hotfixes and other new features in an October update.  This stay of