Disconnected systems and manual processes were creating unnecessary complexity for a residential construction company that needed greater control over its growth. Centre Technologies helped the organization transition from Dynamics GP to Microsoft Dynamics 365 Business Central through a phased approach designed to modernize its ERP without disrupting the business. In approximately 3.5 months, the teams moved from kickoff to go-live while maintaining a strong focus on financial controls, testing, training, and adoption. Today, the company has a more scalable ERP foundation that can support continued integration and automation.
Replacing an ERP system is bigger than a simple IT upgrade. Financial controls, operational continuity, reporting requirements, and audit readiness all have to remain intact throughout the transition.
This residential construction company had outgrown an environment built around Microsoft Dynamics GP and several connected systems. Manual processes and spreadsheets added complexity, while disconnected workflows made it harder to maintain the level of visibility and control expected of a public company.
At the same time, the business itself presented unique ERP demands. Its operations included manufactured home production, dealer and retail sales, inventory, consumer lending, and multiple locations. They needed a better platform that could support the complexity of their infrastructure without forcing every system and process to change at once.
Rather than treating the project as a direct replacement for Dynamics GP, Centre approached it as an opportunity to establish a stronger financial and operational foundation.
The work began with deep discovery. Centre worked closely with finance and operations teams to understand:
Third-party integrations
Those findings became detailed solution designs that helped answer an important question early: What should Business Central handle today, and what should wait for a later phase?
Where standard Business Central functionality could meet the requirement, Centre prioritized configuration over unnecessary customization. Role-based permissions, approval workflows, posting controls, change logging, fixed assets, inventory tracking, purchasing, financial reporting, and other capabilities could become part of a more controlled ERP environment without recreating every legacy process.
Most importantly, specialized applications remained in place where they still served the business effectively.
The broader philosophy behind the project was this: solve the business problem without adding complexity simply because the technology allows it.
A major challenge was the timeline. From kickoff on May 11 to the targeted September 1 go-live, the teams had roughly 3.5 months to move the project forward without skipping critical implementation work.
Instead of treating discovery, configuration, integrations, training, testing, data preparation, and cutover as completely separate stages, Centre coordinated the work across a tightly managed schedule. Weekly status meetings, detailed action tracking, frequent follow-ups, and early escalation of blockers kept both teams aligned.
Scope discipline was equally important. When requirements needed additional discovery, Centre didn't force uncertain work into the initial implementation simply to preserve the original plan. The team made practical decisions about what belonged in the initial phase and what could responsibly move to a later stage.
The speed came from close collaboration and disciplined project management, with practical scope decisions. Not from skipping implementation steps.
PM at Centre Technologies
Centre worked with the organization to incorporate controls directly into the Business Central design. That included role-based access, approval workflows, segregation of duties, posting controls, supporting documentation, and change tracking.
Rather than carrying the previous Dynamics GP configuration forward, the project created an opportunity to establish a cleaner security and control model around how financial activity would be prepared, reviewed, approved, and recorded.
This control-first approach helped ensure Business Central wasn't simply newer technology. It could provide a more sustainable foundation for the organization's financial processes and future audit requirements.
Training wasn't treated as the last step before deployment.
Centre also began transferring knowledge into its Premier Business Central Support team as implementation work concluded. That gave the support team context around the organization's configurations, business processes, and custom requirements instead of forcing the customer to start over with a new team after go-live.
The relationship could then shift naturally from implementation toward ongoing improvement.
The biggest outcome wasn't simply moving away from Dynamics GP.
The manufactured housing company established a modern ERP foundation that could become the center of a broader financial and operational environment.
Business Central could serve as the system of record for critical business information while specialized applications remained connected where they continued to provide value. Centre could then help the organization improve the environment incrementally instead of requiring another large-scale transformation every time the business needed something new.
That work continues through Business Central support and optimization, including evaluating opportunities for additional automation. For example, AP processes can be explored through tools such as Continia Document Capture to reduce manual invoice processing while strengthening approval and audit workflows.
The result is a relationship that extends well beyond a single ERP project.
Centre helped transform a business-critical platform and stayed alongside the organization as it evolved.