12 Weeks of Winter – Week 12
In our last blog, Week 11 of the 12 Weeks of Winter, we covered many of the nice-to-have features in the latest releases of MS Dynamics GP. I am sure you were happy to know that Microsoft’s focus of continuous improvement with each release is not slowing down! With this being our last blog in our series, I would really want to know if we got “excited” on your list of reasons to upgrade. I believe we have given you many good reasons to look at this as a process that will add value to the organization rather than a process that is done out of necessity.
With that said, the next question on your mind should be – How do I get started? As you may already be aware, there are a number of resources available to you through CustomerSource. In addition, the Dynamics Community contains information on many of the topics that we have covered here in our blog.
Here are a few things to consider as part of your upgrade planning:
Will your current hardware support the new version?
If you are using or planning to use any of the Web Applications such as Workflow, Web Services and SSRS here are the system requirement for:
What is the best timing for your upgrade?
The first thing to consider is what version of Dynamics GP you are currently running and when support for that version ends. If you want to take advantage of all of the new features you should look at staying current which means planning for an upgrade every 2 to 3 years. Click here to learn more and keep up to date on the Microsoft Support Lifecycle.
For example, if you are currently running GP2010 you will need to look at completing your upgrade before the end of the year as mainstream support for this version will expire October 13, 2015. This is especially critical for those of you with payroll, as there will be no tax table updates for the 2015 year end. (Tax table support is provided within the guidelines of mainstream support.)
Although there are a lot of activities surrounding an upgrade, the average client will be down with no access to their solution for 1 business day. This means that you need to look at the ebb and flow of your business and determine when one business day downtime would have the least impact on your business. It would be critical to not plan your upgrade when you need to get your payroll out!
The best thing you can do is pick up the phone and give Joesoftware a call. We can walk you through the process and cover some of the topics below that will take the unknowns out of the upgrade process.
Will you need to complete a test upgrade?
The purpose of a test upgrade is to provide you with an environment that will allow you to spend the time to test your critical processes and thus reduce risk of down time when completing your live upgrade. This means that you will need to look at your internal resourcing to ensure that your team will be able to spend the required time to complete this critical testing If you don’t have time to do the testing, then you need to evaluate the “value” of this process. Keep in mind, not everyone will need to do a test and the best way to determine this is to have a discussion with your Joesoftware consultant.
I must say that this has been a great way to countdown the 12 Weeks of Winter and with spring just around the corner, the end of our blog series is a great time to remind you about the purpose of our blogs. In Week 1 we encouraged you to schedule your upgrade in advance, suggested that you take control and pick the date and timeframe that works best for your organization and strongly encouraged you to be an early adopter and strategically preplan this engagement to ensure that you take full advantage of the new features. “Proactive” is the key to successfully putting you in control. I hope that you are picking up your pen today and writing “Excited” on the top of that list of reasons to upgrade – I know we are!