Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

GPUG 2014 Stories From the War Room: Upgrade Successes and Lessons Learned

718 views

Published on

Jim Lemkau, Andrew Kampwerth, Pat Schimpf talked about how to not have your Microsoft Dynamics GP 2013 upgrade turn into a horror story

Published in: Technology
  • Be the first to comment

  • Be the first to like this

GPUG 2014 Stories From the War Room: Upgrade Successes and Lessons Learned

  1. 1. #GPUGsummit Upgrade Horror Stories Dynamics GP 2013 Jim Lemkau, Andrew Kampwerth, Pat Schimpf
  2. 2. #GPUGsummit Upgrade Horror Stories • Though we are in a season of ghosts and goblins, your upgrade to Dynamics GP 2013 does not have to be a horror story. This morning we will discuss some potentially grave situations, that if not addressed in your upgrade planning could result in its untimely demise. • Consider your environment and GP 2013 System Requirements. https://mbs.microsoft.com/customersource/northamerica/GP/learning/documentationmdgp2013_system_requirements • Consider your current GP version and the upgrade paths available. https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGP2013Upgrade#UpgradePaths 2
  3. 3. #GPUGsummit Upgrade Horror Stories • Obtain registration keys for all 3rd parties. Some have reverted back to the original developers and their upgrade steps may differ. • Smartlist Builder • Collections Management • Extender • Concur Expense • Audit Trails • Electronic Signatures 3
  4. 4. #GPUGsummit Upgrade Horror Stories • FRx migration to Management Reporter. • ISO codes assigned to all currencies. • Functional currency set in all companies. • Cleanup FRx prior to migration. • Migrated reports will need to be tweaked in Management Reporter. • Currently on GP 2010, why not migrate now. 4
  5. 5. #GPUGsummit Upgrade Horror Stories • Test Upgrades • Pros • Uncover data corruption and have time to fix it prior to production upgrade. • Ensure data integrations are working properly. • Resolve issues with modified reports that do not upgrade properly. • Users will develop knowledge of additional features. • Cons • Cost. • Time. • Introduction – Pat Schimpf 5
  6. 6. #GPUGsummit Questions? 6

×