Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Angela Morehouse]

With all of the rebranding and release information from Microsoft the more research I do, the more confused I become. My initial understanding was you could go to the ‘perpetual’ release from GP 2018 R2. This made me believe I only had a double-hop of an upgrade, but I think I’m looking at a triple hop. What is my path for an upgrade from GP15 v14.00.0619 to the latest version of GP? My understanding with my most recent research is we have to upgrade to the GP15 SP and then to v18.0xxx (I believe, GP 2018 R2). Is going to v18.2xxx another upgrade? Anyone BTDT? Any insight would be much appreciated.

——————————
Angela Morehouse
CC Industries
Chicago IL
——————————

[Joseph C. Markovich]

Hi Angela-

We are on GP 2015 R2 (14.00.1230) — the 2019 Year End Update version. Then we have to upgrade to the 2019 year-end update version for 2016 R2 (16.00.0814) and then straight to the latest 18.2 update (18.2.1060).

That is the path I have been testing and works.

I hope this helps.
Joe

——————————
Joseph C. Markovich
Valparaiso IN
——————————
——————————————-

[Derek Albaugh]

When in doubt, the ‘Upgrading to Microsoft Dynamics GP ####’ hot topics on PartnerSource and CustomerSource are your best choice in planning an upgrade path. In most cases, if there isn’t an upgrade path per the hot topic, it can’t be done directly.

For example, looking at the ‘Upgrading to Microsoft Dynamics GP’ (18.2) hot topic, there is no direct upgrade path from GP 2015 at all, only GP 2016 (16.00.0716 or later) minimum or GP 2018 (18.00.0496) minimum.

Based on this, as you mentioned, you’d need to upgrade from GP 2015 to GP 2016/GP2018, then upgrade to GP 18.2.

The hot topics are important in that, depending on what version/build of a GP product you’re currently on, can dictate the minimum version/build of GP that you need to be upgrading to?.

I also wanted to mention that 14.00.0619 for GP 2015 isn’t a high enough build to upgrade to either GP 2016 nor GP 2018. You have to be on a minimum of 14.00.0725 or later to upgrade to GP 2016 or 14.00.0898 or later to upgrade to GP 2018.

So, to answer your question, to go from 14.00.0619 to GP 18.2, you’re looking at one upgrade to get to a higher build of GP 2015, then upgrade to a version/build of either GP 2016 or GP 2018 in order to then turn around and then upgrade to GP 18.2, so a total of 3 upgrades from where you are at now.

Thanks

——————————
Derek Albaugh
Sr. Support Engineer
Microsoft
Moorhead MN
——————————
——————————————-

[Blair Christensen]

If you check the upgrade matrix, this can be done by going to 2015 R2 and then straight to 2018 R2.

My suggestion is to set up a test server with a copy of your live environment.  Run through your proposed upgrade there and test things out.  This has the added benefit of getting you comfortable with the upgrade process itself and establishing a time allotment for the real upgrade.  It will also help you work through any issues you may find along the way – some of which may require data cleanup on your production system prior to attempting the upgrade!

If you’d like, I taught a class on this at Summit last year and gave out a variety of upgrade scripts (SQL) to help with environment analysis and planning.  Email me directly if you are interested.

——————————
Blair Christensen
Database Administrator
Oppenheimer Companies, Inc.
Boise Idaho GPUG Chapter Leader
——————————
——————————————-

[Cecile Dinh]

Just wanted to chime in… GP 2015 R2 (14.00.0983) straight upgrade to GP2018.2 (18.2.1013) works just fine.

——————————
Cecile Dinh
GP Admin at ARC (Airlines Reporting Corp.)
GPUG Chapter Leader – Washington, D. C.
——————————
——————————————-