May 13, 2026

Dynamics NAV to Business Central Migration: ONICON’s Cloud Journey

A Dynamics NAV to Business Central migration often reveals hidden issues, from customizations and integrations to vendor compatibility and data complexity.

In this client testimonial, ONICON shares how they approached their NAV 2017 to Business Central migration and why working with an experienced partner helped them navigate the process with confidence.

Planning a Dynamics NAV to Business Central SaaS migration

ONICON, a fast-growing manufacturer of precision flow meters used globally in the HVAC industry, had been running Dynamics NAV 2017 for years.

As part of their modernization strategy, they planned a move to Business Central in the cloud to:

• Align ERP with their existing cloud-based CRM
• Improve data sharing across systems
• Leverage Power Platform tools and integrations
• Support long-term scalability

After evaluating multiple partners, ONICON selected ArcherPoint for its migration experience and structured approach.

A structured ERP migration process

From the outset, ArcherPoint guided ONICON through a detailed assessment process, including:

• Reviewing existing add-in vendors and solutions
• Evaluating compatibility with Business Central
• Identifying where replacements were needed

During the migration, the team:

• Converted NAV customizations into AL code
• Executed data migration and multiple mock go-lives
• Refined processes based on real-world testing

The process was highly collaborative, with ongoing communication between ONICON’s team, the project manager, and ArcherPoint’s lead developer.

Reducing risk during ERP migration

ERP migrations rarely go exactly as planned—and ONICON’s experience reinforced the importance of preparation and expertise.

During the final migration weekend, a configuration issue arose while connecting Business Central to CRM—something that hadn’t appeared during testing.

Rather than delay the project, ArcherPoint’s team worked alongside ONICON for several hours to troubleshoot in real time. The lead developer ultimately identified a solution outside the standard interface, enabling the migration to proceed successfully.

This level of responsiveness underscores the value of working with a partner who understands both the process and the potential risks.

A long-term ERP partnership

Beyond the migration itself, ONICON emphasized the importance of working with a partner they could rely on throughout the process

ArcherPoint was consistently:

• Responsive and easy to work with
• Collaborative throughout the project
• Invested in the success of the implementation

Over time, the relationship evolved beyond a typical vendor engagement—becoming a trusted partnership built on communication and shared goals.

Watch the client testimonial

If your organization is planning a Dynamics NAV to Business Central migration, learning from companies that have successfully navigated the process can help you avoid common pitfalls and move forward with confidence. Reach out to ArcherPoint by Cherry Bekaert to explore how an experienced migration partner can support your transition.

Video Transcript

My name is David Stevenson from ONICON Incorporated. I’m a Senior Software Developer there. We’re located in Largo, Florida.

ONICON is a manufacturing company. We make precision flow meters and other measurement tools that are used extensively in the HVAC industry. Our products are installed all over the world. We’re a fast-growing company.

I started as a consultant with ONICON for about three years, and then I went full-time almost 16 years ago.

We were looking at moving from NAV 2017 to Business Central in the cloud. We assessed that whole process, and I had heard ArcherPoint make a presentation at one of the conferences about their migration process. That was very impressive to us.

We looked around and evaluated other options, and then decided to make ArcherPoint our partner for our migration effort because of their experience in doing so many migrations.

From the very beginning of our migration project, ArcherPoint was very methodical in taking us through the steps. They had a very good assessment process at the start. They helped us review all of our add-in software vendors and the products we were using in NAV to determine how they would translate into Business Central.

We ended up having to replace a couple of vendors that didn’t have a Business Central solution, and ArcherPoint helped us through that process.

When we got into the actual migration, their migration team took all of the many customizations we had done in NAV and worked through them over a period of several months. They converted them into AL code for Business Central.

They then completed the initial data migration and our first mock go-live. Through that process, we assessed the weaknesses and things that weren’t working exactly as expected, or areas where Business Central worked a little differently from NAV.

It was a great collaborative effort back and forth between our team, the project manager, and the lead developer who was handling the migration coding work.

We had a lot of communication with the ArcherPoint lead developer, who was very responsive and provided quick turnaround on the items we needed adjusted.

We completed a second mock go-live, made a few more refinements, and then the actual go-live weekend went very smoothly.

We had already migrated our CRM to the cloud, and it seemed like the logical next step. We were still running on the original release version of NAV 2017 and had not made significant changes to it aside from a few communication updates.

We wanted to move BC onto the same online platform as CRM so we could take advantage of Power Apps, Power Platform tools, and collaborative features to transfer data between the two systems more easily than we could on-premises.

What stood out to us was the friendliness of the employees, their helpfulness, and their responsiveness to our needs—especially during the migration.

One example stands out. On migration weekend, when we were finishing configuration of our connection to CRM, the setup screen in BC got stuck in an incorrect configuration. That issue had not occurred during our mock go-lives.

They stayed up with us for several hours that night while we were close to pulling the plug. The lead developer found a way to make the necessary configuration change outside of the user interface and ultimately salvaged the project.

We were delighted to have resources who were so knowledgeable and able to solve problems on the spot to help us get through that weekend successfully.

Yes, I would definitely recommend ArcherPoint. Their knowledge of migrations in particular is unsurpassed.

They’ve completed so many migrations and have the depth of experience and understanding of what can go wrong—and what likely will go wrong if certain steps aren’t taken first.

I would highly recommend ArcherPoint for anyone looking to change partners or begin a migration project.

We’ve developed a strong working relationship with several people on the ArcherPoint staff. It’s become more than just a business relationship—it feels more like a friendship—and we value that very highly.

Trending Posts