As much Microsoft standard as possible, as much customization as necessary. NAVAX customizes where standard and apps fall short, and reviews existing customizations before they move.
Do you recognize yourself in one of these statements? Tap it, and next to it you see how we handle it.
Choose what it's about: a new requirement or a customization you already have. Then you see how we decide.
First, we check the standard process. Whatever the standard functionality covers needs no customization.
Solved entirely with Business Central's built-in tools, deliberately without customization.
Schematic view. The examples are anonymized; nothing is stored.
Gap/fit analysis, assessment of the standard functionality, an MVP built with the business department, and only then are remaining gaps closed in a targeted way.
What customers most often want to know before an extension or a system change.
Customization is adapting standard software, such as an ERP system, to the requirements of a company. At NAVAX, the rule is: as much Microsoft standard as possible, as much customization as necessary. NAVAX uses customization specifically where standard functionality or available apps don't deliver enough business value.
No. Customization isn't rejected but used in a targeted way. NAVAX implements via standard processes, extends as needed and combines with apps and custom extensions when that brings concrete value. At NAVAX, custom development complements the ERP EasyStarter, migration, apps, training and the Customer Service.
When, after the gap/fit analysis, the assessment of the standard functionality and an MVP with the business department, a gap remains that has real business value. Two examples: sales returns we solved entirely with Business Central's built-in tools, deliberately without customization. For production output postings, a targeted extension was built that can report several production order lines together based on a grouping code.
They go into the customization audit. There, we assess which customizations should be carried over, which can be replaced by standard functionality and which can be dropped completely. Only once it is clear which customizations are truly business-critical do we migrate.
With the Easy Starter, you reassess customizations; this brings the strongest modernization and the greatest reduction of historical custom developments. With the data migration, your history is preserved; we reassess the customizations and carry them over selectively. With the 1:1 migration, existing customizations largely remain; the modernization effect is smallest here.
Too many legacy customizations endanger maintainability and upgradeability. In many NAV systems, customizations sit directly in the program code and have to be reworked with every version change. In Business Central, customizations are built as extensions, not in the standard code. Existing customizations therefore have to prove their value again.
NAVAX recommends before the project starts: check the quality of your master data, clarify how much history you need, critically question customizations and assess the options for process optimization.
In the toolkit around the NAVAX ERP EasyStarter, customization covers: custom extensions, interfaces, AppSource apps, AI & agents, Power BI, Power Platform and modern workplace. In addition, there are preconfigured industry solutions, reusable best practices and standardized implementation approaches as packages.
For Microsoft Dynamics 365 Business Central and for the CRM applications Dynamics 365 Sales, Customer Insights, Field Service and Customer Service. The principle is the same everywhere: as much Microsoft standard as possible, as much customization as necessary.
Checking your processes against the standard, implementing on the standard and the paths for existing systems.
