Get the latest perspectives on Microsoft Dynamics ERP software selection process from industry experts.

What Happens When a Microsoft Dynamics 365 Business Central Implementation Becomes More Complex Than It Needs to Be?

Visit Website View Our Posts

Woman inspecting and adjusting an orthopedic brace in a manufacturing workshop, representing Hely & Weber’s Business Central implementation and manufacturing operations.
Moving to Microsoft Dynamics 365 Business Central is about more than just replacing Dynamics GP because it is outdated. Organizations expect to simplify operations, reduce IT overhead, and gain a modern cloud platform that can support future growth. While Business Central delivers those benefits for many companies, implementation strategy plays a critical role in the outcome.

Sometimes, the software isn't the problem. An overly complex solution design can create unnecessary maintenance, increase support requirements, and make everyday work more difficult than it needs to be.

That was the experience of Hely & Weber, a manufacturer and distributor of orthopedic bracing products. After an initial implementation divided critical business processes between Microsoft Dynamics 365 Business Central and Dynamics 365 Sales, the company found itself spending more time managing integrations than improving the business.

Working with Dexpro Dynamics, Hely & Weber simplified its architecture, consolidated operations into Business Central, and built a solution that better matched the way the company actually works.

Key Highlights

  • A successful Business Central implementation depends as much on solution design as it does on the software itself.
  • Splitting business processes across multiple applications can introduce unnecessary complexity and ongoing maintenance.
  • Native Business Central functionality often eliminates the need for custom integrations.
  • A well-designed implementation should simplify daily work while supporting long-term business growth.
  • The right Microsoft Dynamics partner focuses on solving business problems—not selling additional software.

Read the full case study: Rescuing Hely & Weber from an Overcomplicated Business Central Implementation

When Good Intentions Lead to Unnecessary Complexity

Like many manufacturers, Hely & Weber had relied on Microsoft Dynamics GP for years. As GP approached the end of its lifecycle, the company decided it was time to modernize its ERP environment and move to the cloud.

The initial implementation strategy seemed logical. Manufacturing and shipping would run in Microsoft Dynamics 365 Business Central, while order entry, customer management, commissions, royalties, and tracings would be handled in Dynamics 365 Sales. A custom integration would connect the two systems.

On paper, the architecture looked like it combined the strengths of both applications.

In practice, the integration quickly became the biggest challenge.

Instead of supporting the business, it demanded constant attention.

"We went live in December 2024, and we fought that integration for a year," said Kirk Rogers, IT Manager at Hely & Weber. "I wasn't able to do anything else because I was always fighting fires."

For many organizations, this illustrates an important lesson about ERP implementations. Every additional system, integration, or customization should solve a clear business problem. Otherwise, it can become another component that requires monitoring, troubleshooting, and maintenance.

Why Simpler Architecture Often Creates Better Business Outcomes

When Hely & Weber decided to look for a new Microsoft Dynamics partner, they weren't searching for more technology. They were looking for a better approach.

After evaluating several partners, they selected Dexpro Dynamics because the conversations focused on simplifying the environment rather than expanding it.

Instead of recommending more software, Dexpro questioned whether two Microsoft Dynamics applications were necessary at all.

Their recommendation was straightforward: consolidate the business processes back into Microsoft Dynamics 365 Business Central and use the platform's native capabilities wherever possible. Rather than continuing to rely on a custom integration, they proposed creating a solution centered around a single ERP system.

That recommendation carried additional weight because Dexpro also implements Dynamics 365 Sales. Suggesting that Hely & Weber move away from part of its existing solution meant recommending fewer software licenses—not more.

Rogers appreciated that approach.

"Even though they also work with Dynamics 365 Sales and would lose out on extra license fees, they recommended what was best for us," he said. "They gave us a fixed price range for the project, and we moved forward."

For organizations evaluating Microsoft Dynamics partners, this highlights another important consideration. The best implementation partner isn't necessarily the one with the largest team or the broadest software portfolio. It's the partner willing to recommend the solution that best fits your business, even when that recommendation doesn't maximize its own revenue.

Designing Business Central Around the Way People Actually Work

Simplifying the architecture was only part of the project. The new solution also had to support the daily work of Hely & Weber's employees.

One challenge involved pricing.

The company manages more than 400 customer contracts with specialized pricing agreements, making pricing accuracy essential to daily operations. Rather than forcing employees to work around the software, Dexpro used Business Central's enhanced pricing capabilities to support these complex pricing structures within the ERP system.

Order entry presented another opportunity to improve the user experience.

Customer service representatives had become comfortable with SalesPad's grid-style order entry screen over many years of use. Moving to Business Central didn't mean employees had to abandon an efficient workflow.

Instead, Dexpro developed a custom order entry experience inside Business Central that preserved the familiar grid layout while eliminating the need for a separate application. Employees could continue working the way they always had, but within a simplified ERP environment.

Manufacturing and shipping also transitioned smoothly. Business Central's manufacturing capabilities supported Hely & Weber's production processes, while a shipping solution with native Business Central integration streamlined fulfillment without introducing unnecessary complexity.

The Business Benefits Went Beyond a Simpler ERP System

Simplifying Hely & Weber's Business Central environment didn't just reduce software complexity. It also changed how the company's IT department spent its time and significantly lowered future infrastructure costs.

Before moving to the cloud, Hely & Weber maintained approximately a dozen on-premises servers to support databases, remote users, and shipping operations. After redesigning the solution around Business Central, only a domain controller and a shipping integration server remained on-site for handheld devices.

That smaller infrastructure has long-term financial benefits. Replacing the company's current hardware is expected to cost approximately $10,000 to $11,000. Under the previous server environment, a comparable hardware refresh would have cost between $120,000 and $150,000—a reduction of more than 90 percent.

Just as valuable was the time the IT team gained.

Instead of constantly troubleshooting integrations and maintaining servers, employees could focus on projects that improve the business. For many organizations, those productivity gains can be just as important as the direct cost savings.

The implementation was also completed on schedule and within the agreed budget—an outcome that Kirk Rogers described as "a rarity in the IT world."

What Manufacturers Should Look for in a Business Central Partner

Technology is only one part of a successful ERP implementation. The partner guiding the project can have an even greater impact on the long-term success of the solution.

When asked what advice he would give other companies evaluating Microsoft Dynamics partners, Rogers didn't start by talking about software features.

Instead, he focused on finding the right fit.

"Look for the partner that is the right fit for you. Bigger is not always better."

Communication was another important factor.

After previously working with an overseas implementation team, Rogers appreciated being able to work directly with the consultants performing the work rather than communicating through layers of project managers or sales representatives. That direct relationship made it easier to ask operational questions and receive practical guidance throughout the implementation.

He also valued having a partner willing to teach—not simply implement.

"I pose operational questions to them, and they show me how to accomplish it in Business Central," Rogers said. "They've been willing to help me figure out the things I didn't know about the cloud so that I can attend to system maintenance on my own."

For manufacturers planning a Dynamics GP migration or evaluating their current Business Central environment, that kind of partnership can make the difference between simply installing new software and building a solution that supports the business for years to come.

Lessons Learned from This Business Central Implementation

Every Business Central implementation is different, but Hely & Weber's experience offers several valuable lessons for manufacturers and distributors.

  • Keep the solution as simple as possible. Additional systems and integrations should solve a specific business problem—not create new ones.
  • Take advantage of Business Central's native capabilities. Before introducing custom integrations, evaluate whether Business Central already provides the functionality you need.
  • Design around business processes, not software boundaries. Employees work more efficiently when the ERP system supports their existing workflows.
  • Choose a partner that challenges assumptions. The best recommendation isn't always the most complex one. Sometimes simplifying the architecture delivers the greatest long-term value.
  • Look beyond implementation day. Consider how the solution will be maintained, supported, and expanded over the next five to ten years.

Dexpro Dynamics case study banner promoting Hely & Weber’s overcomplicated Business Central implementation, with an orthopedic brace shown on the right.

Frequently Asked Questions

Why do some Business Central implementations become more complicated than expected?

In many cases, the added complexity comes from solution design rather than Business Central itself. Splitting core business processes across multiple applications or relying heavily on custom integrations can increase maintenance and support requirements.

Can Business Central support complex pricing requirements?

Yes. Hely & Weber manages more than 400 customer contracts with specialized pricing. By using Business Central's enhanced pricing functionality, the company was able to manage those pricing agreements within a single ERP system.

Is it always necessary to use both Business Central and Dynamics 365 Sales?

Not necessarily. The right solution depends on an organization's business requirements. In Hely & Weber's case, consolidating key business processes into Business Central eliminated unnecessary complexity while better supporting day-to-day operations.

What should manufacturers look for in a Microsoft Dynamics partner?

Look for a partner that understands your business, recommends the solution that best fits your needs, communicates openly throughout the project, and provides guidance that helps your team become more self-sufficient over time.

Simplifying the Architecture Can Maximize the Value of Business Central

Microsoft Dynamics 365 Business Central gives manufacturers a powerful foundation for managing finance, operations, manufacturing, inventory, and distribution in a modern cloud ERP solution. But as Hely & Weber's experience demonstrates, achieving those benefits depends on thoughtful solution design as much as the software itself.

By simplifying its implementation, reducing unnecessary integrations, and taking advantage of Business Central's native capabilities, Hely & Weber transformed an environment that required constant attention into one that supports the business more efficiently and positions the company for future growth.

If you're planning a migration from Dynamics GP or wondering whether your current Business Central environment has become more complex than it needs to be, the team at Dexpro Dynamics can help you evaluate your solution and identify opportunities to simplify your architecture while supporting your long-term business goals.

Contact Dexpro Dynamics to start the conversation today.

Marlena Stark

By Marlena Stark, CEO, Dexpro Dynamics

Marlena founded Dexpro with the vision of providing high-quality, personalized expert level consulting and becoming one of the top customer focused companies. She has extensive technical and functional knowledge as well as an understanding of the business process, allowing her to easily improve efficiency and understand clients’ needs.

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.