Lessons learned from a Salesforce to Dynamics CRM Online migration gone (nearly) wrong

When something unexpected and perhaps troubling arises on an enterprise software project, project managers and other stakeholders may be tempted to understimate or ignore the issue. Such problems often lead to teams grinding through the issue, even if it means adding resources and working late nights and long weekends. And once it is done, some people would prefer to never speak of it again.

But Travis Hargett, president of Microsoft Dynamics partner Eastridge Technology, took another approach on a recent project that turned painful - in this case, a migration from Salesforce.com to Dynamics CRM Online. Rather than brush it under the rug, he decided to share his experience and the lessons learned.


Requires FREE Membership to View

Become a Member Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also receive periodic email newsletters with the latest relevant articles and content updates.
About Linda Rosencrance

Linda Rosencrance is a freelance writer/editor in the Boston area. Rosencrance has over 25 years experience as an reporter/investigative reporter, writing for many newspapers in the metropolitan Boston area. Rosencrance has been writing about information technology for the past 16 years.

She has covered a variety of IT subjects, including Microsoft Dynamics, mobile security issues such as data loss prevention, network management, secure mobile app development, privacy, cloud computing, BI, big data, analytics, HR, CRM, ERP, and enterprise IT.

Rosencrance is the author of six true crime books for Kensington Publishing Corp.

Read full bio...

What else can go wrong

Thanks for the honest Postmortem.

I did a similar blog post on things that can go wrong with data migration. Hope you find it useful.