Key Drivers Behind Moving to Microsoft Great Plains
Great Plains Accounting has long been a staple for many mid‑size companies, but the landscape of enterprise software is changing. As an IT specialist, understanding why a migration might be in order is the first step toward making an informed decision. The main reasons revolve around product lifecycle, underlying technology, and vendor support.
First, the original Great Plains line has been gradually phased out since the mid‑1990s. The company that created it began the shift toward new products, like Great Plains Dynamics, and later Dynamics/CS+. When Microsoft bought Great Plains, the focus moved toward the latest version, 8.0, and beyond. Because newer releases incorporate modern features, security updates, and better integration with cloud services, staying on the older platform puts an organization at risk of falling behind in compliance and efficiency.
Second, the core database engine used by the old system was Btrieve, a Pervasive product that has seen little development in recent years. Microsoft’s current ERP stack relies on SQL Server, a platform that offers advanced analytics, robust backup options, and tighter integration with other Microsoft products such as Dynamics 365 and Power BI. The decision to retire Btrieve in favor of SQL Server reflects Microsoft’s desire to unify its ecosystem, and the company stops offering new support or patches for the older Btrieve‑based products.
Third, Microsoft’s support policy favors the latest version of its solutions. When you install the newest platform, you receive priority patches, direct access to technical teams, and compatibility with the latest hardware and operating systems. If you stay on a legacy version, you risk losing official support, and you may have to rely on third‑party vendors for maintenance, which can increase costs over time.
Beyond these high‑level factors, the migration process itself is a technical operation that involves reading the Btrieve tables, translating data structures, and loading everything into the new SQL‑based tables. Although the core data - customers, invoices, inventory records, and financial ledgers - remains the same, the underlying schema has changed. The migration tool or service must preserve relationships, data types, and business logic while adapting them to the new environment.
Because Great Plains Accounting is still in use in many places, a full migration isn’t mandatory. Companies can operate in a hybrid mode, keeping legacy data in the old system and connecting it to newer applications via APIs or data connectors. However, a hybrid approach adds complexity to maintenance, security, and reporting. Over time, the cost of managing two separate systems tends to outweigh the benefits of a single, modern platform.
From an IT perspective, the decision boils down to evaluating the business’s readiness for change versus the risks of sticking with a platform that no longer receives official updates. If the organization needs advanced analytics, improved data security, or easier integration with cloud services, migrating to Microsoft Great Plains 8.0 or newer is the logical path. On the other hand, if the company’s processes are tightly bound to legacy workflows that would be disrupted by migration, a phased approach or selective migration may be required.
In short, the migration conversation is about aligning technology with strategic goals: staying current with security patches, leveraging modern database capabilities, and accessing a broader ecosystem of Microsoft services. These benefits make the migration a worthwhile consideration for most organizations that still rely on Great Plains Accounting as their core ERP solution.
Choosing a Migration Partner and Execution Tips
Once the need for migration is established, the next critical step is selecting the right partner to execute the move. The migration itself can be handled in two main ways: through Microsoft Business Solutions or through a certified Value‑Added Reseller (VAR) partner. Each option carries its own advantages and considerations.
Microsoft Business Solutions offers a turnkey migration service. The process typically involves the IT team packaging the existing Btrieve files and sending them to Microsoft. In return, Microsoft provides a fully configured SQL Server database backup that contains the migrated data, along with detailed installation instructions for the new Great Plains environment. This path guarantees that the migration follows Microsoft’s recommended practices, and it eliminates the risk of data loss or incompatibility caused by misconfigurations. The trade‑off is that the cost is generally higher than hiring a third‑party partner, and the customer’s team must trust Microsoft’s handling of sensitive financial data during the transfer.
For organizations that prefer to keep a closer eye on the migration process or that have budget constraints, a VAR partner can be an attractive alternative. VARs specialize in custom implementations and often have experience with multiple Great Plains migrations. When choosing a VAR, due diligence is essential. Verify that the partner has completed at least two successful migrations, and request references from clients with similar business sizes and industry focus. Check their technical certifications, such as Microsoft Dynamics 365 or Great Plains Expert, and evaluate their post‑migration support model.
Andrew Karasev, Chief Technology Officer at Alba Spectrum Technologies, exemplifies a partner who brings depth of expertise to the table. The company operates nationwide in the United States - spanning states like Illinois, California, Texas, New York, Georgia, and Florida - and offers services in Microsoft CRM, Great Plains customization, and related technologies. Karasev’s background in Dexterity, SQL, C#.NET, Crystal Reports, and the Microsoft CRM SDK positions the team to handle both the data migration and the integration with existing customizations. Visiting the company’s website at
Tags
No comments yet. Be the first to comment!