When organizations move from Dynamics GP, SL, or NAV to Microsoft Dynamics 365 Business Central, the conversation usually starts with data, timelines, and core ERP functionality. But one of the most important—and often overlooked—parts of the journey is the ISV stack that surrounds the ERP solution.
As Enavate’s alliance manager, I spend a lot of time working with ISVs and with clients who’ve accumulated years’ worth of add‑ons to support their business. In a recent #AskEnavate session, I sat down with my teammates Carolyn Newell Robbins and Blair Shelton to talk through how we help clients simplify and rethink their ISVs as part of a Business Central migration.
The biggest takeaway from our conversation was simple: a move to Business Central is the perfect moment to pause, reassess, and avoid bringing unnecessary complexity forward.
What an ISV Really Is—and Why That Matters Now
An ISV, or Independent Software Vendor, is a company that builds software to extend the capabilities of your ERP system. Historically, GP, SL, and NAV relied heavily on ISVs to fill functional gaps—whether that was electronic payments, reporting, compliance, or industry‑specific needs.
Standard ERP software cannot do everything, especially when you’re dealing with vertical requirements or advanced functionality like compliance or reporting. ISVs have long played a critical role in making ERP systems usable for real‑world businesses.
What’s changed is the platform.
Business Central brings significantly more functionality out of the box, which raises a new question for migrating organizations: Which ISVs still add value—and which ones don’t?
Starting with Business Needs, Not the ISV List
One of the things Carolyn emphasized is that simplification starts with understanding how clients are actually using their systems today.
“At Enavate,” she explained, “we start with assessment tools that show us what ISVs are installed—but that’s just the baseline.” From there, the real work happens in discovery sessions, where we talk through whether an ISV is still used, partially used, or no longer necessary at all.
In many cases, an ISV that was critical five or ten years ago is no longer essential—either because Business Central now handles that functionality natively or because the business itself has evolved and changed.
As Carolyn put it, “It could be that Business Central eliminates the need for that ISV entirely, or that only a portion of what you were using is still relevant.”
Where Business Central Naturally Reduces ISV Dependence
A clear example we discussed came from SL environments, where core banking functions often required add‑ons.
“Electronic banking, ACH payments, blank check processing, and cleaner bank reconciliation were all add‑ons in SL,” Carolyn noted. “In Business Central, those capabilities are built in.”
This pattern shows up again and again during migrations. What once required customization is now standard functionality, which is why we encourage clients not to automatically replicate their old environments.
When ISVs Still Make Sense in Business Central
That said, ISVs are far from disappearing.
Blair, our Business Central delivery lead, summed it up well when he said, “The first question should always be: what business challenges are we trying to solve?”
In our experience, ISVs are still very common (and very valuable) in areas like:
- AP automation
- Multi‑entity management
- Advanced reporting
- EDI and compliance
- Warehousing, manufacturing, and shop‑floor extensions
Blair emphasized that timing matters too. “Some ISVs need to be part of the initial rollout. Others are better added in a second phase once the foundation is stable.”
Avoiding the Trap of Over‑Customization
One of the strongest messages from our discussion was about restraint.
Blair put it bluntly: “Anytime you add an ISV, you’re adding complexity, cost, and long‑term risk.” His recommendation is to stay as close to standard Business Central as possible unless there’s a clear, documented business case for extending it.
I see this play out often in the field. A cleaner base system is easier to upgrade, easier to support, and easier to evolve. ISVs should enhance the system, not weigh it down.
Handling Gaps Like Payroll and Industry Requirements
Some transitions do come with real gaps that require careful planning. Payroll is a common one.
As Carolyn explained during the session, “GP and SL had payroll inside the ERP. Business Central doesn’t. That’s a big change—and it affects everyone.”
That’s why we guide clients toward strategic payroll ISVs that integrate cleanly and meet their specific needs, rather than treating payroll as just another checkbox in the migration.
We also see similar conversations in highly specialized industries, such as food and beverage, where ISV choices can change when moving platforms.
Take a 2-Minute Payroll Assessment
How Enavate Evaluates ISVs During Migration
At Enavate, ISV evaluation starts with data—but it doesn’t stop there.
We begin with assessment tools that identify which ISVs are installed in your current environment. From there, we hold discovery conversations to understand:
- Which ISVs are actively used
- Which features are actually relied upon
- Which tools were implemented years ago but are no longer critical
From that baseline, we determine:
- Whether Business Central replaces the functionality natively
- Whether a comparable Business Central ISV exists
- Whether a different solution better fits current needs
- Or whether the requirement can be eliminated entirely
Every recommendation is made in the context of where your business is today—and where it’s headed.
Choosing the Right ISVs Moving Forward
Not all ISVs are created equal, and experience matters.
Carolyn shared an important principle we follow: “We have identified strategic ISVs in key areas because we know how they implement, how they support their products, and how they work with partners.”
That track record makes a difference—not just during go‑live, but over the life of the system.
When evaluating new solutions, it’s important to consider:
- Whether the ISV is certified for Business Central
- How long the vendor has supported the Microsoft ecosystem
- Their implementation history and support model
- How well the solution aligns with your future roadmap
Blair added that Microsoft AppSource is a great starting point, especially when clients focus on certified solutions with proven Business Central compatibility.
The Mindset Shift That Makes Migration Successful
If there’s one idea I hope you take away from this, it’s this: a move to Business Central is not about recreating your old ERP environment.
As Blair said near the end of the session, “You really have to ask yourself whether the ISVs you use today are the ones you’ll need tomorrow.”
Business Central gives organizations a chance to streamline, consolidate, and modernize—not just swap platforms.
When our clients approach migration with that mindset, they don’t just end up with a new ERP. They end up with a simpler, more flexible foundation that’s ready for what’s next.
