Find a software partner qualified to support your system.

 

You may sometimes wonder about the real value in having a software partner to support the regular upgrades of the Microsoft Dynamics NAV or Dynamics 365 Business Central system you use to help run your business. This sentiment might come about after you struggle with an upgrade project or when your partner takes three days to get back to you on a support issue. For some organizations, the strength of their internal IT staff might lead them to believe they don’t need any help.

 

Software partner relationship types vary depending on your needs

These are all valid reasons for questioning the value in having a software partner, but there are many levels of partner relationships possible. Because of this, in my mind the answer is a qualified “yes” to the question of whether a software partner adds value or not. You may just be out of sync with your partner in terms of the type of relationship you actually need. Or it’s possible you just haven’t found the right partner yet.

Unless you are planning on sitting on your system for 10 or 15 years and never making a change, you will need a software partner at some point. It is important to realize that all Dynamics NAV customers will eventually have to move to Dynamics 365 Business Central in the future if they are planning on an upgrade. For now, customers still have a choice between on-premise installations and a cloud option, but this may not be true in the future.

 

Microsoft chooses to work exclusively through partners for NAV & Business Central

Microsoft is heavily invested in the cloud option. The last major Business Central release in Spring 2020 (read more about it here) has removed the Windows client interface for Business Central and all new implementations or upgrades have to commit to the browser-based interface. There is a temporary option for customers to retain an older version of Business Central which allows for the Windows interface, but this is a short-term solution and probably shouldn’t be in your planning horizon.

Microsoft chooses to work exclusively through partners for these two products and not engage directly with customers. There are some very specialized exceptions to this statement, but they are very rare and unlikely to apply for the vast majority of Dynamics NAV or Dynamics 365 Business Central customers, unless you have signed up for one of Microsoft’s limited support or training plans.

 

Watch out for software partners who have no historical experience with Microsoft Dynamics NAV and are now selling Business Central.

Software partner relationship type 1: “We just need a change to our license”

This means that at a minimum you need a partner to process license changes such as adding users and additional functionality, etc. Although you can generally continue to run your software indefinitely without a partner, you need a partner relationship if you need any changes to your license.

In the older versions of Dynamics NAV, this could just mean additional functionality, whereas in later versions and in Business Central the only licenses available for on-premise databases are the Essentials or Premium license. The latter adds capability for manufacturing and service management. You may not need the additional capability but this restriction to license changes also applies to adding more users. If your business grows, you could find yourself limited with too few users.

For cloud licenses in Business Central, there are more ways for you to maintain basic changes to your own license but generally these are processed through a partner, whether directly or through a customer e-commerce portal. As an example, our company, Open Door Technology, provides our cloud customers with the ability to manage their own Office 365 or Dynamics 365 licenses. If you need to add a new accounting or Outlook user or even a new product, simply log into the system at any time and make your change. With access to a portal such as this and a cloud system that looks after upgrades, you can minimize your interactions with partners.

 

Type 2: “We need an upgrade”

If you plan on upgrading your Dynamics NAV system to a newer version or to Business Central, you will need at least a minimum interaction with your software partner to trigger the license change. The actual upgrade effort can be carried out by either your internal staff or the license or other third-party partner.

If you are considering a move from Dynamics NAV to a cloud version of Business Central, be aware that the internal development language has changed from the proprietary C/side development toolkit to Visual Studio AL (Application Language). Visual Studio AL is similar to the .Net code your developers may have learned in the past but it is substantially slower to develop in than C/side. Keep this in mind for internal or external time and cost budgets. Microsoft continues to improve the Visual Studio AL toolkit but for now this is our reality.

To move up to the latest version of Business Central, you will NOT be able to keep your existing modifications “as-is.” They will have to be re-done in the new toolkit. If this is the first time your developers have worked with Visual Studio AL, you could be looking at five to 10 times the time penalty versus your current C/side coding until your developers get up to speed. This is one reason to consider having your partner execute the upgrade effort as they should have some good experience by now.

The good news about an upgrade to Business Central is that in certain situations upgrades are processed automatically by Microsoft for minimal cost. Heavy customization may require some updates to meet new technical requirements from Microsoft, but in the long run the overall effort and cost will be substantially cheaper and less disruptive than the historical pattern of going through Dynamics NAV upgrades. Read our previous blog here to learn exactly how these upgrades work with your customizations.

 

Type 3: “We need technical support on occasion”

Some organizations don’t have the level of experience or expertise necessary to handle all issues that might arise, whether technical or arising from the software itself. Both Dynamics NAV and Business Central are extremely reliable and generally require little assistance once your initial implementation or upgrade has been live for three months.

Microsoft has offered customers a direct option for technical support plans for Dynamics NAV, but this can be somewhat inefficient as the support techs don’t have the first-hand knowledge a partner should have – especially the partner personnel who were involved in the original project. This same qualification also applies to high volume partners who rely on local or offshore support centers.

Most software partners will have a good handle on Dynamics NAV, but there are still partners out there who either haven’t really made a serious commitment to Business Central or don’t have in-depth experience with it yet. Make sure you are comfortable with the level of your partner’s expertise with and commitment to Business Central before starting an upgrade or implementation project – otherwise it may come back to bite you, especially if there are complex customizations required.

 

Type 4: “We often need support”

In this case, you definitely should engage with a partner who is committed to your business. They can handle the license changes, upgrades, and help you resolve your system issues. Again, find a partner qualified to support you on your system and especially if you are considering a move to Business Central with its substantially more complex development environment.

 

Type 5: “We believe in a true partnership relationship with our partner”

A true partnership relationship means both parties are committed to working together to get the maximum value out of the system. The partnership is based on mutual respect. The actual level of interaction will vary, depending on the customer’s internal support capability, but the two parties are working in tandem with proactive planning, regular contact, and strong technical capabilities. The customer will be assigned an account manager who understands the capabilities of both the core product and key add-on products that may bring further value to the customer.

 

Questions to ask when considering what your software partner relationship should look like:

  1. Do we ever plan on upgrading?
  2. Are we interested in moving to a cloud solution?
  3. Can we support ourselves technically?
  4. Is our partner capable or interested in supporting us?
  5. Do we view our partner relationship as being a true partnership?

Once you answer those questions, you will have the answer to whether you actually need a software partner for your Microsoft Dynamics NAV or Dynamics 365 Business Central system and if your current partner is the right partner. In some cases, your original partner may have gone out of business or has lost their capability of supporting Dynamics NAV. Business Central is quite different technically, although your users will find the functionality nearly identical to Dynamics NAV.

Watch out for partners who have no historical experience with Microsoft Dynamics NAV and are now selling Business Central. This can be true for IT partners who can now sell Business Central off a Microsoft price list or are currently supporting other ERP products and are looking for an alternative.

Open Door Technology has been in the mid-market ERP space since 1992 and has dealt exclusively with Microsoft Dynamics NAV and Dynamics 365 Business Central since 2000. We are both a services and ISV (Independent Software Vendor) development partner with average staff experience of over 10 years with the software platform.

Contact us here to discuss with no obligation exactly what your business requires in a software partner relationship.

 

*Have you thought about how much simpler your life would be if you didn’t have to manage servers? Rely on ODT Managed IT Services to enjoy all the resources Microsoft has to offer in maintaining your hardware, systems, and data. Learn more about our Managed IT Services in our recent blog here.