Microsoft continues to gain momentum with IT departments as organizations look for modern cloud ERP solutions that integrate seamlessly with Microsoft 365, Azure, Power BI, and Copilot. More companies are viewing ERP as a strategic platform that supports reporting, automation, artificial intelligence, and long-term digital transformation.
With any ERP implementation, the process should begin with discovery, followed by budgeting, pricing, and project planning. Once approved, the implementation begins. At Accountnet, we typically create a prototype environment within a Business Central sandbox hosted in Azure. This allows end users to see their chart of accounts, companies, dimensions, and reporting structure before moving into production. Whether a company operates a single entity or multiple entities, the sandbox provides a practical way to validate requirements and reduce risk.
One area that consistently generates discussion is data migration. Clients migrating from legacy systems often discover that moving financial data, historical transactions, dimensions, reporting structures, customers, vendors, and operational information is more complex than originally anticipated. A well-planned migration strategy is critical to the success of any ERP project.
Recently, we worked with a client that selected Sage rather than Business Central. After the implementation, the IT Director expressed concerns about the overall approach and wanted to switch to Business Central. The organization specifically wanted Microsoft Copilot, Power BI, and deeper integration with the Microsoft ecosystem. As business requirements evolved, they found that advanced reporting, AI capabilities, and Microsoft platform integration were becoming increasingly important.
What Was Not Working Well
One concern involved the implementation methodology. The initial setup team was responsible for configuration and preparing the system for go-live. However, after deployment, support responsibilities shifted to different teams. This transition created challenges in maintaining continuity and ensuring the original business requirements remained fully understood throughout the project lifecycle.
Another Sage concern related to limited to or lack of parallel processing during go-live. Critical testing, validation, and configuration activities were often completed within the production environment rather than in a dedicated sandbox environment. Organizations generally prefer the ability to perform extensive testing in parallel before production deployment, reducing business disruption and implementation risk.
The client also identified Sage concerns regarding customizations and workflow changes being completed directly within the live environment. This increased the need for testing, documentation, and change-management controls. In addition, organizations migrating from software like Microsoft Dynamics GP may encounter differences in chart of accounts structures, dimensions, and reporting methodologies that require careful planning and validation.
Finally, with Sage and Netsuite, the chart of accounts and dimension migrations can present challenges, particularly when the GP account segments are leading with three zeros or when dimensional reporting structures have evolved over time. These issues should require additional data-cleansing and conversion efforts before implementation.
Summary
Based on our discussions with organizations evaluating Sage, NetSuite, and other ERP platforms, common concerns may include dimensional reporting limitations, implementation methodology, transitions between implementation and support teams, customization practices within live environments, and data migration complexities. In contrast, Business Central’s Azure sandbox approach, combined with Power BI and Copilot capabilities, gives organizations an opportunity to validate configurations, reporting, and business processes before go-live, helping to reduce risk and improve user adoption.
