• Home
  • About Us
  • Contact Us
  • Privacy Policy
  • Special Offers
Business Intelligence Info
  • Business Intelligence
    • BI News and Info
    • Big Data
    • Mobile and Cloud
    • Self-Service BI
  • CRM
    • CRM News and Info
    • InfusionSoft
    • Microsoft Dynamics CRM
    • NetSuite
    • OnContact
    • Salesforce
    • Workbooks
  • Data Mining
    • Pentaho
    • Sisense
    • Tableau
    • TIBCO Spotfire
  • Data Warehousing
    • DWH News and Info
    • IBM DB2
    • Microsoft SQL Server
    • Oracle
    • Teradata
  • Predictive Analytics
    • FICO
    • KNIME
    • Mathematica
    • Matlab
    • Minitab
    • RapidMiner
    • Revolution
    • SAP
    • SAS/SPSS
  • Humor

Microsoft Dynamics CRM Implementation – Data Migration and Integration Deserve Respect (part 1)

May 14, 2016   CRM News and Info
CRM Blog Microsoft Dynamics CRM Implementation – Data Migration and Integration Deserve Respect (part 1)

This is the first of a two-part post intended to get you thinking about Microsoft Dynamics CRM data migration and integration prior to the start of your project.

Most Microsoft Dynamics CRM implementations require some sort of data migration and/or system integration. The client wants to bring over current and legacy data. Conceptually, it’s a no-brainer as the upside is quite easy to justify. But the path to success in moving and working with data is not always a straight one and there are usually a good number of square pegs that need to be fit into round holes. Have no doubt, when we’re talking Microsoft Dynamics CRM implementation – data migration and integration deserve respect.

I’ll say it even though it’s obvious: Data is one of the most important assets any company has so it is a KEY deliverable. Moving data from one system to another is a regular part of many CRM projects and there are a number of tools available to help with the ‘mechanical’ part of it. However, a project that includes data migration and integration possesses a higher level of risk than a similar project without it. So we need to have a healthy ‘respect’ for the circumstances and situations we’ll be facing.

On the Client Side

Clients may not have a complete understanding of:

  • The level of detail and complexities involved with many data integration and migration projects.
  • How the various pieces of their data relate to one and other.
  • The condition of their data.
  • The differences between migration and integration and which they really need.
  • Their responsibility for validating and participating in the data work and the effort it will take.

It’s easy to assume that “it’s just data” and to underestimate that part of the project – this can be a costly assumption.

On the Consulting Side

Consultants need to:

  • Work closely with the Client or Prospect in order to educate and help them gain a proper understanding and perspective of the above topics.
  • Make every effort to gain as much understanding about the Client and their data as possible, given the limitation of scope of discovery and terms of the project.
  • Evaluate expertise and experience with the systems, industries, etc. we’ll be dealing with in the project.
  • Given the (usually) limited exposure to the data prior to project initiation, be up-front with the client regarding comfort level and the ability to accurately assess and estimate the level of effort needed, as well as identify possible risks.

Consultants need to nurture the relationship with the Client and to help the Client to help them.

The nature of the ‘beast’

  • Data is a ‘beast’ . . . working to ‘tame’ it often takes more time than initially thought as we uncover new aspects of the data models during implementation.
  • Without a complete ‘under the hood’ assessment of data prior to commencing work, know that there will be surprises and things that just have to be dealt with.
  • The more the Client and the Consultant know about it up front, the smoother the project will go and risk level will decrease.
  • It’s difficult to scale back the scope of data work once you are committed – good reason to avoid getting into trouble in the first place.
  • Both sides will know the data much better once the work is done – and both will wish they had that same understanding when they started the data work.

Stay Tuned

Integration and data migration are areas certainly deserving of an appropriate level of risk management throughout a project. In the next post we’ll dig a little deeper into some specific things Consultants should consider as they plan and execute systems integration. The same goes for Clients as they look to implement CRM or perform integration for themselves.

By John Clifton, Application Consultant xRM³, a Microsoft Dynamics CRM Partner focusing on sales and productivity solutions powered by Microsoft Cloud. Based in San Diego County Southern California. For help, contact us by clicking here.

by xRM3

Let’s block ads! (Why?)

CRM Software Blog

data, deserve, Dynamics, implementation, Integration, Microsoft, migration, Part, Respect
  • Recent Posts

    • WATCH: ‘Coming 2 America’ Movie Review Available On Amazon Prime & Amazon
    • IBM launches AI platform to discover new materials
    • 3 Ways a Microsoft Dynamics 365 Supply Chain Management and EDI Integration Enhance E-Commerce CRM Strategy
    • The Neanderthals
    • What the swarm of new Azure announcements mean
  • Categories

  • Archives

    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • March 2020
    • February 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    • December 2016
    • November 2016
    • October 2016
    • September 2016
    • August 2016
    • July 2016
    • June 2016
    • May 2016
    • April 2016
    • March 2016
    • February 2016
    • January 2016
    • December 2015
    • November 2015
    • October 2015
    • September 2015
    • August 2015
    • July 2015
    • June 2015
    • May 2015
    • April 2015
    • March 2015
    • February 2015
    • January 2015
    • December 2014
    • November 2014
© 2021 Business Intelligence Info
Power BI Training | G Com Solutions Limited