The Real Cost of Implementing Microsoft Dynamics GP: Understanding Legacy Data Options

In a new series of articles, I'll discuss the complexities of dealing with situations where Microsoft Dynamics GP implementation services far exceed budget.  This is not a black and white issue -  it's appropriate to go beyond budget in some situations and not in others. And if you think you simply can't afford important services, I'll discuss how you find ways to adapt by controlling costs intelligently.

My articles are based on my years of observing that a major cause of failed or threatened implementations - those over budget and schedule - is a lack of preliminary planning and analysis.  The implementers are locked in a tug-of-war with the companies they serve, unable to accurately estimate a project yet unable to win or start the project unless they provide a competitive quote.  Then the big surprises come with major hurdles like integration of data, training, and "Go Live" consulting - three issues I plan to explore in depth.

What I'm faced with many times in smaller companies is a lack of understanding in how ERP costs really add up, such as with respect to their legacy data integration and migration needs.  Before they proceed, many prospective clients want to know what services will cost in their very first discussion.  The reality is:  no two companies are alike, and neither are their data.  Even small companies transitioning from Peachtree or QuickBooks to Microsoft Dynamics GP can vary greatly in implementation time and cost.

Here are some of the key concerns when dealing with legacy data in a Dynamics GP project.

Integration of Data - What do You Really Need to Transition

The Rapid Migration Tool that works with Microsoft Dynamics ...