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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Parallel testing a new version of GP

(0) ShareShare
ReportReport
Posted on by 571

Our CEO has made it clear that he'd like us to do a 30-day parallel test of GP 2016 alongside our current 2013 R2. That means all transactions, deposits, checks, etc.

What, if anything, would you suggest as an alternative to entering everything twice? Or is that something you expect to do and it doesn't sound too out-there at all?

Hoping to mitigate the stress on our accounting team...

Sincerely,

Steve Erbach
WOW Logistics Company
Appleton, WI
2015 GPUG All Star
2016 GPUG Emerald Volunteer Engagement Award
VP for Communication, GPUG Wisconsin (Milwaukee)
Co-Chair, GPUG Wisconsin (Green Bay)

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,061 Moderator on at

    Hi Steve,

    I've been going thru quite a few GP major upgrades in my 'GP' existence.. most of the time you setup a whole new server to move the your old data to the new environment, which usually involves a new OS & SQL version to keep up with Microsoft's system requirements.

    For my past 13 years working with GP, I've never gone thru a 'parallel' testing .. and honestly I don't think that it is very productive.. My experience with major version upgrades is anyway that end-users most of the time don't have a lot of time to spend on testing, while trying to perform their daily duty and keep up with all the data entry.. so doubling that amount of data would just be killing.

    Microsoft used to provide an application called SureStep to the partners in order to prepare a system migration. There were Excel workbooks attached to this that would allow to prepare a migration test plan and have that assigned to the various users. This way you can hand over a check-list with all the functions to TEST in the new system and have the users  sign off from this TEST plan.

    The last major upgrade I performed from 2010 to 2015R2 involved only about a dozen key users (from a larger pool of users and 47 companies) that were responsible to test the various modules and all the 3rd party products (including MR 2012).

    6 weeks of testing were enough to ensure that the system fulfilled the company's expectations on the new release. 6 weeks may sound a short time, but the company was only using GP for it's core modules (Financial & Sales). If you're using a wider range of apps and 3rd party, then you'll likely extend this. My last test time-frame from 2010 to 2013R2 span over almost 6 months, but it involved also the migration from Business Portal to the new GP web client (BP is no longer supported after 2013R2).

    It is important to have the users perform not just daily activities, but also the ones that are one only once in while (month-end and year-end) as those are the ones usually forgotten or underestimated.. and when that time comes in the real-world, they hit an issue that no one encountered during testing, because it's rarely performed.

    Hope this helps and good luck with your project.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Shravan Attelli Profile Picture

Shravan Attelli 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans