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

PowerApps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as PowerApps Portal and shifted to the PowerApps side of the Microsoft product family.


Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users.

The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription."

Pricing starts at $200/mo. for 100 dail…

The DATA Act Driving Grant Management Automation

The Digital Accountability and Transparency Act enacted in May 2014 calls for making spending data available in open, standardized formats to be published online.  It is a continuation of transparency initiatives and lessons learned with experiences such as grants.gov, the 2009 economic stimulus under the Recovery Act and the spending site USASpending.gov.

Government grantees will have significant new administrative responsibilities.  Many organizations that were tracking grants in spreadsheets or documents will have to adopt more sophisticated automated grant management systems such as Microsoft Grants Manager to keep up with reporting rules.

For profit companies will lose some privacy as a result of this law.  Grant recipients will be required to disclose information including officer salaries.

Continued improvements to publishing grant opportunities such as grants.gov may make it easier to find grants. These reforms together are designed to improve the effectiveness of grant prog…

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet:

ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience.

You can also use ScreenMeet with other CRM products or even on its own without a CRM.

Here is a short video demo of ScreenMeet with Dynamics integration:


ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appears on Case pa…