NAV application support
Investigate recurring errors and custom behavior, document the affected objects and define a maintainable support scope.
Microsoft Dynamics NAV support
Dynamics NAV support. For the business you run today.
Your Dynamics NAV system holds years of business decisions. AIONDATA helps maintain its customizations, repair order and inventory handoffs, and plan the next step around the business you run today.
Support what matters. Improve what comes next.
The business you already run
OrdersInventoryFinance
Your system of recordDynamics NAVBusiness rules · Data · Customizations
A defined engineering scopeApplication + integrations + operating knowledge
Maintain Connect Improve
Start with the workflow. Choose the change.
Start with the problem
Tell us what has
become difficult.
A recurring error. A failed integration. An application only one person understood. Tell us where the work gets stuck.
Your system and the workflowYour version, if you know itWhat you need to happen next
We’ll confirm fit, access requirements and scope before proposing work. Please do not include credentials or customer records.
info@aiondata.ioDiscuss Dynamics NAV
You do not need all the technical details to start.
01 / Keep the business moving
Years of customization. A business that cannot stand still.
Pricing rules, warehouse processes and invoicing may depend on NAV objects that only a few people understand. A broken commerce connection or a small change request can turn into a much larger problem.
We start by tracing one workflow and establishing who owns the customizations, interfaces and operating environment. Then we scope the repair or improvement, with a clear path for testing and handover.
Commerce and CRM handoffs
Trace missing orders, mismatched items or invoice updates through the actual interfaces available on your NAV release.
Customization continuity
Recover source, object ownership and deployment knowledge so a change does not depend on one person’s memory.
Upgrade readiness
Identify what must survive a move to Business Central, including custom business rules, historical data and integration dependencies.
02 / Make the improvement concrete
An order should not disappear between systems.
Consider a commerce order that cannot reach NAV because an item mapping is missing. The useful improvement is a visible exception, the information needed to correct it and a controlled retry—not another silent background job.
Explore the three steps. This is an illustrative workflow, not a production demo or a promise of compatibility with every release.
AI is optional. Ownership is essential.An assistant could help explain an exception. Validation, permissions and the decision to change a record still need explicit controls.
Workflow walkthroughIllustration
Commerce orderNAV sales order
Example order / ORD-1042Needs attention
An item is not mapped.
The order is held before creation in NAV. The operations owner sees the source reference and the missing item mapping.
- Source order: identified
- Item mapping: missing
- Retry: held for review
Synthetic example. No live Dynamics NAV connection or customer results. Actual behavior depends on your release, interfaces and agreed scope.
Built around your environment
The details make
the difference.
The release determines the interface
We inspect the exact NAV release and available web services. SOAP, OData and custom objects need environment-specific review; modern Business Central APIs are not assumed to exist on NAV.
Business rules stay in view
Customer, item, currency and posting rules need to be understood before changing a handoff. We review custom objects and test the proposed path in an agreed non-production environment.
Recovery is part of the integration
Agree duplicate detection, retry limits, reconciliation and who resolves exceptions. Your team receives the operating notes for the work delivered.
03 / A concrete first step
Know what to fix.
Before the larger commitment.
The System Continuity Assessment gives you a written view of the environment, one priority workflow and the options worth considering.
A paid, defined engagement. We agree the scope, fixed fee and access requirements before work begins. Implementation and care are scoped separately.
Discuss an assessmentYour assessment deliverables
01
Your environment, understood
Application release, hosting, customizations, interfaces and critical dependencies.
02
One workflow, traced
Where work becomes manual, which handoffs fail and who needs to resolve them.
03
Responsibilities, made clear
What your team, AIONDATA and existing vendors would each own.
04
A next step you can evaluate
Prioritized findings, options and a scoped recommendation for the next phase.
04 / Clear responsibilities
Support you can
define and hand over.
After the assessment, choose a focused improvement project or an ongoing care agreement. Covered systems, working hours, response targets and escalation belong in writing.
The agreed engineering work
Application and integration issues, scoped customizations, tests, monitoring and operating documentation.
Business decisions and approvals
Application ownership, access decisions, accounting rules, change acceptance and named process owners.
Vendor and platform dependencies
Licenses, manufacturer patches, hosted services and specialist obligations retained under their agreements.
Independent engineering support does not extend the manufacturer’s lifecycle. A discontinued hosted service may require export and transition rather than continued operation.
Keep exploring
The next useful page.
Before we begin
Questions worth
asking.
Can you work alongside our existing NAV partner?
Yes. We can take a defined application or integration scope while your existing partner retains licensing or other responsibilities. We agree access, release coordination, escalation and ownership before making changes.
Can you maintain our Navision customizations?
We assess the deployed release, custom objects, source access, development tools and ability to reproduce changes. The support scope follows that assessment; we do not assume an undocumented customization can be safely changed immediately.
Do we need Business Central before fixing an integration?
Not necessarily. The existing NAV interfaces may support the required improvement. We compare a repair in place against an upgrade when interface limitations, unsupported dependencies or the wider business case make an upgrade relevant.
Which NAV versions are covered?
Tell us the version if you know it. We confirm the release, cumulative update, customizations and infrastructure during scoping. Vendor support dates and tested interface coverage are specific to that environment; we do not publish a blanket all-version guarantee.
Can NAV connect to AI tools?
Potentially, through a controlled integration exposing selected records or actions. We first check the available interface, identity, permissions and workflow. A read-only exception explanation can be a useful first step; write actions need separate validation and approvals.
What happens when we need a vendor patch?
We identify the relevant Microsoft or partner dependency and your entitlement. Our engineering services do not grant access to vendor patches or extend Microsoft’s lifecycle. Upgrading an affected component may be part of the recommendation.
What do we receive from an assessment?
A release and dependency inventory, one workflow map, customization and ownership findings, prioritized issues and a scoped next step. That can be support in place, an integration repair or a more detailed upgrade plan.
Start where you are
One system.
One useful next step.
Bring the problem. We’ll work through the options with you.
Product references · checked 13 October 2026Microsoft: Dynamics NAV 2018 lifecycle Microsoft: web services and the NAV / Business Central distinction
AIONDATA provides independent engineering services. Product names identify the systems discussed and do not imply vendor endorsement.