web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

GP 2013 12.00.1412 SP1 to GP 2016 R2 upgrade

(0) ShareShare
ReportReport
Posted on by

I am preparing to upgrade a client from GP 2013 12.00.1412 SP1 to GP 2016 R2.

I have already done it on a non production server although when I originally did it I upgraded to GP 2015.  The client had some misgivings about Management Reporter and stayed course with GP 2013 and FRx.

My concerns are as follows;

1.  As I recall I had to perform an upgrade to GP 2013 R2 and then to GP 2015.  Since then I have upgraded to GP 2016 with no problem.  According to a Leslie Vail post (thanks LV), I need to be at 12.00.1826 or later.

2.   On the live server I have installed another instance of SQL server and created the company/restored the GP 2016 R2 database from the non-production server onto it.  I restored the dynamics database and it works okay.  They have 8 years of historical companies, i.e.  at the end of each FY, I created a new company, X2014 etc. and the restored the Year End database to that company to provide P&L account detail.  Operational continuity is critical and I am leery of upgrading the original SQL instance.

2a.  Is it feasible to run GP 2013 for access to the historical companies and GP 2016 R2 for current year?  Ideally I would upgrade the current SQL instance and not tax the server with another SQL instance, I have the GP2016 SQL test instance disabled when not testing due to performance issues.  Besides the live company database and the Dynamics database, is there any other databases I would need to backup/restore in the event of failing to upgrade, i.e. must be operation Monday?  Historical companies are not critical to initial upgrade. 

3.  I have installed Management Reporter and imported FRx reports.  They have been running and enjoying it for a month now.  I have read that due to ports, etc. it is not possible to run with different SQL instances.

thanks in advance for your insight.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    twelvestrikes Profile Picture
    3,657 on at

    Hi Phil

    Lets take each section one at a time.

    Section 1,

    Funny thing I am working on the same upgrade for a client right now, GP 2013 SP2 to GP 2016 R2.

    You mentioned a post by Leslie Vail and she is 100% correct.  You have a choice with GP 2013 you can update it to GP 2013 R2 so that the version is at least 12.00.2130 and then go to GP 2016 R2 or you can go from GP 2013 to GP 2015 R2 (version 14.00.725) and then to GP 2016 R2

    As a note I am going GP 2013 SP2 > GP 2013 R2 > GP 2016 R2

    Section 2

    Why do you want to create additional companies for historical data?  You can simply upgrade the existing companies and then have the historical data at hand in one database.

    If your client is one that is very transaction heavy and the database size is very large, then I would look into using Company Data Archive by Professional Advantage.  

  • Community Member Profile Picture
    on at

    Hey Jeffrey,

    Maybe it's a setting but when we close the Year, we lose the P&L accounts detail or transactions.

    thanks,

  • twelvestrikes Profile Picture
    3,657 on at

    Hi Phil

    I bet when you do your year end you are also opting to run Period Consolidation.  Don't run that just run the year end closing

    That will keep all the transaction detail.  I never even show Period consolidation.  It stems from way back when hard drive space was expensive and this was a way of keeping the database sizes small.  No point to do this as hard drive space is cheap.

  • Community Member Profile Picture
    on at

    Thanks Jeff!  I'll run through it on my non-production server and look forward to that next year end closing.

  • Community Member Profile Picture
    on at

    Hi Jeffery,

    Out of curiosity, how long did it take to upgrade from GP2013 R2 to GP2016 R2 ?

  • Suggested answer
    twelvestrikes Profile Picture
    3,657 on at

    Hi Yves

    I have just done this upgrade for 2 clients.  It is going to depend on your server. Client 1 was 2.3 or 2.3 single processor and 8GB of RAM.  Mostly GL transactions.  The largest company db was just under 700MB.  It took an average of 40 minutes per company to go from GP 2013 to GP 2013 R2 with the June SP installed.  Then GP 2013 R2 to GP 2016 R2 took 55 minutes per company.

    The Second upgrade went much faster. The server was a 3.2GHz Xenon with 16GB of RAM.  GP 2013 to GP 2013 R2 took just under 25 minutes and GP 2013 R2 to GP 2016 R2 took about 30 minutes for a database size of 1.7GB with mostly payables and GL transactions

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans