How to manage a phased Microsoft Dynamics CRM and GP upgrade and migration to the cloud
We recently came upon a challenge from a client who needed to upgrade a complex Microsoft Dynamics CRM environment and migrate it, along with a large number of Dynamics GP databases, to the cloud. They had a large user base and were concerned that all of the training and end user support happening at once would be disruptive.
The customer had complex integrations running between Dynamics CRM and Dynamics GP and needed to upgrade both applications. However, their requirements were to do the CRM upgrade first and to take a phased approach - upgrading 6-12 business units at a time. As part of the cloud migration, they needed to migrate a single GP company with each corresponding CRM business unit, along with the associated integrations for each.
Not your average approach
A typical server move or upgrade approach would include the GP system database, typically called DYNAMICS, and all company databases. For this scenario, though, we needed to be able to move chunks of GP company databases while somehow keeping the DYNAMICS database in sync between their on-premise environment and the new cloud hosted environment. We reached out to the Dynamics partner community as well as Microsoft, and no one had encountered this scenario before.
To address the needs of this unique ...
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here