Common NAV Implementation Misconceptions Remedied

By
49

Despite the marketing and education push from Microsoft, there’s still a good deal of hand-wringing in offices across America when it comes to implementing Microsoft Dynamics NAV. Misconceptions about the role, size, and labor requirements of an implementation abound, potentially diverting companies that could massively benefit from a working installation of NAV. For the benefit of any potentially satisfied NAV users, here’s some common misconceptions debunked about the implementation of Dynamics NAV.

Potentially the largest misconception about NAV is its role in a company. Many consider the software to be “IT Software,” though in reality it’s ERP (enterprise resource planning) software. Many companies end up tasking their IT departments with the maintenance and running of the software, but they don’t have the necessary perspective to get the most out of the product. NAV is business software, necessary to the operation of supply chains, commerce, financing, manufacturing, and so on As such, those core to the operations of a business should manage NAV; they’re the ones who can best capitalize on the software.

Another unfortunate misconception is that NAV is unusable out of the box, or that it requires tons of customization to be useful. Most partners report that aside from business forms (which are intrinsic to a business any way you look at it), NAV can be used right out of the box. The root of this misconception seems to come from customizations that are done but not entirely necessary.

The important point here is that customization helps – and the more you do the more it’ll help – but the base customization necessary is actually very low. Rolling out a base installation of NAV is still very usable and helpful, so it’s an option that should be considered if budgets don’t allow for an extended implementation period.

Speaking of budgets, the final misconception is that NAV is expensive to implement. Yes, it will cost money to implement, and there’s no getting around that, but expense is relative. From a business perspective, if you can spend $1 million to save $2 million, you’d do it without much deliberation. While the savings that Dynamics NAV can afford your business aren’t so easy to predict, the savings and enhanced rate of business need to be considered when appraising the cost of a deployment.

Sticker shock is a real thing, but calmer heads always prevail when it comes to business operations. Implementing NAV will yield constant and long-lasting benefits, and those benefits are sadly ignored when the calculators hit the table.

 

Contact Us

54321
(0 votes. Average 0 of 5)