Skip to main content

Migrating from Parature to Microsoft Dynamics 365: Part 2


On October 9, 2017, Microsoft released a migration tool to help its Parature customer service customers migrate to Microsoft Dynamics 365.   This blog post is a continuation of the first post in the Parature migration series.

The Parature migration tool provides capabilities to export data from Parature, map the data to Dynamics 365 fields, and configure a Dynamics 365 portal to replace the Parature customer service portal functionality. The tool is accompanied by training videos. 

In order to use the migration tool, you must be a Parature customer and request access from Microsoft technical support.  The tool is tied to your specific instance of Parature, so it requires configuration by Microsoft before you can use it.  It includes solutions that are installed in your instance of Dynamics 365.

Microsoft provides mapping of fields for entities such as contacts, accounts, cases (trouble tickets) and knowledge base articles.  In addition, the tool supports mapping of your custom fields. You can save your configurations and perform as many test migrations as necessary.

Migrating your data from Parature to Dynamics 365 provides an opportunity for data cleansing.  For instance, you may want to delete fake email account records if you receive online support inquiries from bogus email addresses or identities.  Many organizations are hit by spammers who use support email aliases because they are published on your website and discovered through searches for email addresses.

You could also clean up your data further if desired by removing erroneous cases that do not contribute to improving your customer service or are not used to derive your case performance metrics.  These may be cases submitted by SPAM accounts but they could also be other forms on illegitimate cases.

Part 3 of this series will focus on the migration of the customer service portal.

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

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

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend 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