Solve business challenges with one long-term technology partner
From Microsoft Dynamics 365 Business Central implementation to continuous improvement, optimization, and ongoing support
One partnership across the entire Business Central landscape
Xpand partners with companies to solve operational challenges, improve system performance, and develop new capabilities as their business evolves. From Microsoft Dynamics 365 Business Central implementation and onboarding to integrations, upgrades, optimization, development, and ongoing support, we take long-term responsibility for the entire connected system landscape. Business Central, NAV, WMS, EDI, APIs, portals, Azure, Power Platform, and related solutions are managed within one structured partnership that protects critical operations, resolves incidents, and keeps the business moving forward.
What’s included in Xpand’s long-term Microsoft Dynamics 365 Business Central support
Incident
Functional and technical resolution
Root-cause
analysis
Proactive monitoring and risk management
Key-user
assistance
Knowledge
retention
Reporting
and oversight
Improvement planning
Make Business Central support a long-term operational partnership
Choose the level of protection your logistics business needs today, with a clear path to broader support as your operations, integrations, and Business Central environment grow.
Do you recognize this customer case?
Business Central is essential to daily operations, but responsibility is fragmented
One provider supports Business Central, another handles WMS or integrations, and important system knowledge remains with individual employees or former consultants.
Support begins only after something breaks
The current provider resolves individual tickets but does not actively identify recurring problems, technical risks, performance concerns, or upgrade requirements.
The same issues keep returning
Problems are fixed temporarily, but root causes, known errors, and workarounds are not consistently investigated or documented.
Changes and upgrades arrive as unexpected projects
Technical debt, version requirements, and system limitations are discussed only when they have already become urgent or expensive.
Support costs are difficult to predict
Every incident, question, investigation, or deployment creates a separate invoice, with little visibility into the expected monthly cost.
Your internal team cannot cover every competency
Microsoft Dynamics 365 Business Central increasingly depends on functional knowledge, AL development, integrations, infrastructure, testing, DevOps, reporting, and industry-specific experience.
Your operations have outgrown the original system setup
New warehouses, companies, customers, integrations, services, or compliance requirements have made the Business Central landscape more complex than it was at go-live.
You want one team to understand the complete picture
The business needs a long-term partner that understands how Business Central supports finance, warehouses, shipments, invoicing, reporting, and connected logistics processes.
One long-term Microsoft Dynamics 365 Business Central partnership
New to Microsoft Dynamics 365 Business Central
Start with a Business Central implementation.
We design and implement the solution, transfer it into ongoing support, and continue protecting and developing the environment after go-live.
Implementation → Support plan → Continuous development
Already using Microsoft Dynamics 365 Business Central
Start with structured onboarding.
We assess your current Business Central environment, customizations, integrations, critical business processes, support history, and operational risks before establishing the ongoing support model.
Onboarding → Support plan → Continuous development
Both paths lead to the same long-term relationship.
Once your environment is supported by Xpand, incidents, improvements, upgrades, integrations, and future projects are managed through one shared operating model.
How we work with Partners
Support subscription models
Basic
Defined platforms, applications, components, and functional areas linked to agreed Critical Operational Scenarios.
The monthly fee covers proactive protection of agreed Critical Operational Scenarios (COS) and blockers.
Other incidents are handled within SLA and billed per engagement.
The Coordinator reports and bills; managers handle escalation and limited advisory.
One intake point for Key Users, with fast triage, routing, and ticket tracking.
Functional and technical experts own blockers and incidents through stable resolution.
with planned after-hours blocker deployments when agreed.
All P1 critical blockers are covered by the fixed fee under the Essential SLA.
The client governs change requests; CR execution is also excluded.
2. Listed critical business flows
3. Listed Critical Operational Scenarios
Essential
Defined platforms, applications, components, and functional areas linked to selected business flows and Critical Operational Scenarios.
The monthly fee covers proactive protection and incidents within selected flows/COS.
Other support is handled within SLA and billed per engagement. The Coordinator reports and bills; managers handle escalation and limited advisory.
One intake point for Key Users, with fast triage, routing, and ticket tracking.
Functional and technical experts own blockers and incidents through stable resolution.
with a limited number of planned after-hours blocker deployments.
All P1 critical blockers are covered by the fixed fee under the Essential SLA.
The client governs change requests; CR execution is also excluded.
Optional paid basic Copilot access provides curated instructions, definitions, known issues, and daily guidance.
2. Listed critical business flows
3. Listed Critical Operational Scenarios
Managed
Defined platforms, applications, components, and functional areas across all known business flows within supported technologies.
The monthly fee covers all incidents and blockers.
Change requests are monitored, analysed, and planned, with the Coordinator, Support Manager, and Account Manager actively involved.
One intake point for Key Users, with fast triage, routing, and ticket tracking.
Functional and technical experts own blockers and incidents through stable resolution.
Broad preventive monitoring and early warnings across the supported scope.
Strategic reviews, improvement planning, and architecture guidance support long-term system evolution.
optional extended hours for agreed critical cases, and a dedicated after-hours deployment plan.
Critical blockers can use an agreed-upon after-hours emergency deployment; other items follow a client-aligned schedule.
All blockers are covered by the fixed fee under the Managed SLA.
2. Listed business flows
3. Listed Critical Operational Scenarios
4. First knowledge-base version
Managed Support starts on Day 1, with onboarding completed in parallel.
News & events
Demystifying security compliance in Europe: what leaders need to know
Security compliance in Europe is no longer optional it directly impacts customer trust, legal exposure, and business continuity, as Anzhela Pozdniakova, Chief of Product at Xpand Portal , explores in this article. Leaders are increasingly expected to understand not just the rules, but who is responsible for meeting them. The key principle : security is a shared responsibility. Some controls belong to the infrastructure or hosting provider, some to the product vendor, some to the customer organization. The exact split depends on the deployment model – in SaaS, more operational responsibility usually sits with the provider; in self-hosted environments, more remains with the customer or hosting partner. For leaders, the goal is not to become security experts. The goal is to know which questions to ask, who owns each area, and whether responsibilities are clearly understood. Below are the key compliance areas in plain terms, organized by what infrastructure and product teams are each expected to cover.
Gate capacity planner
The logistics terminal reduced truck congestion and unnecessary downtime during peak hours by implementing Xpand Portal. This allowed for optimized truck processing, real-time alerts on available time slots, and easy access to cargo information for both terminal employees and transport company representatives. The result was a stress-free unloading process and reduced employee burden.
Xpand Portal version 4.5.0.0.
Xpand Portal continues to grow with each release, bringing meaningful improvements that help teams work smarter — and version 4.5 is no exception. This release focuses on making daily workflows smoother: from localization to data entry and workspace clarity. What this release brings: - Productivity enhancements. Faster, more consistent localization with less manual effort. - Data input and presentation. Cleaner editors and a distraction-free View mode for quicker data work. - UI optimization. Better use of screen space and more efficient navigation.
Contact us in any way you prefer
Frequently asked questions
What is included in Business Central support?
The exact scope depends on the selected plan and documented system landscape. It may include incident management, key-user guidance, troubleshooting, root cause analysis, monitoring, knowledge management, backlog governance, reporting, and strategic advisory.
Can Xpand support a Business Central environment implemented by another partner?
Yes. Existing Business Central clients enter through structured onboarding. We review the environment, customizations, integrations, business flows, known risks, and available documentation before establishing the final support scope.
Do you support both Business Central SaaS and on-premises?
Yes. Xpand supports Business Central online, Business Central on-premises, and legacy Dynamics NAV environments.
Can you support custom extensions and integrations?
Yes, provided that the components are active, licensed, technically accessible, and included in the documented support scope. We can also coordinate with third-party vendors where an issue originates outside the systems directly supported by Xpand.
Are Business Central upgrades included in the monthly support fee?
Upgrade readiness and recommendations may be included in Managed Support. The execution of an upgrade is planned as a separate project.
The requirement is identified through ongoing system observation, added to the shared backlog, and discussed before project planning begins.