Cloud-ready product architecture
Legacy on-premises patterns are redesigned into maintainable, upgrade-safe solutions suitable for cloud or hybrid deployment.
ISV-to-SaaS transformation for Business Central solutions
Transform an established NAV or Business Central solution into a maintainable, extension-based product. Xpand supports the complete technical journey, from product assessment and architecture redesign to AL development, QA, Microsoft Marketplace preparation, and ongoing releases.
Modernize the product, not only the code
Moving an established ISV solution forward requires more than converting C/AL objects into AL. Architecture, dependencies, integrations, data handling, testing, deployment, and release processes must also support the modern Business Central model.
Xpand assesses the existing product, redesigns unsupported patterns, reduces technical debt, and prepares it for cloud delivery, Microsoft Marketplace, customer-specific deployment, or continued on-premises use.
The codebase, architecture, integrations, dependencies, data model, installation process, and cloud-readiness issues are analysed to define the transformation scope, risks, and delivery roadmap.
Legacy and monolithic patterns are reorganized into maintainable extension-based components designed for easier development, testing, deployment, and future Business Central updates.
C/AL code, base-application modifications, deprecated components, and unsupported dependencies are converted, replaced, refactored, or removed according to the agreed target architecture.
Functional, technical, regression, integration, installation, upgrade, and release testing help confirm that the modernized product preserves required functionality and remains stable.
The app is checked against applicable Microsoft technical requirements, analyzer rules, packaging requirements, dependencies, and product-specific validation criteria before submission.
Xpand supports technical packaging, validation, issue correction, release preparation, and communication during the submission process. Microsoft retains final responsibility for certification and publication.
After release, Xpand can support compatibility updates, technical maintenance, release validation, recertification activities, defect resolution, and new feature development.
Turn your ISV solution into a cloud-ready product with Xpand
The codebase, architecture, integrations, dependencies, data model, installation process, and cloud-readiness issues are analysed to define the transformation scope, risks, and delivery roadmap.
Do you recognize this customer case?
Product modernization may be needed when:
The solution still depends on C/AL
Legacy code, direct base-application modifications, or obsolete components prevent the product from moving to the current Business Central architecture.
Cloud-readiness checks produce extensive errors
The product team understands the business functionality but lacks the capacity to resolve interconnected architecture, code, and dependency issues.
The converted solution remains difficult to maintain
The product may compile in AL, but its structure still makes testing, deployment, updates, and feature development slow or risky.
Marketplace validation keeps finding new issues
Analyzer errors, dependencies, packaging, compatibility, or technical requirements repeatedly delay submission.
Business Central updates create recurring pressure
The team must repeatedly correct compatibility issues because release preparation and automated validation are not yet part of a stable product lifecycle.
Technical debt limits product growth
Too much development capacity is spent maintaining old architecture instead of improving the product, supporting customers, or entering new markets.
Onboarding and process
A complete path from legacy architecture to a maintainable, cloud-ready product prepared for Microsoft Marketplace or your chosen delivery model, with continued support as Business Central evolves.
Step 1
Your solution
Share your existing on-premises solution, current Microsoft Dynamics NAV or Microsoft Dynamics 365 Business Central version, architecture, integrations, dependencies, and target delivery model. This gives Xpand the context needed to understand the product and its modernization goals before defining the technical scope.
Step 2
We assess
Xpand analyses the legacy code and architecture to identify what is preventing the solution from moving forward. The assessment covers cloud incompatibilities, direct application modifications, deprecated code, obsolete dependencies, integration constraints, technical debt, and potential Marketplace validation issues.
Step 3
Our roadmap
Receive a clear transformation roadmap covering the target architecture, technical-debt elimination scope, development stages, testing approach, responsibilities, timeline, and budget. The roadmap can prepare the product for Microsoft Marketplace publication, private cloud distribution, hybrid delivery, or continued on-premises use.
Step 4
Your approval
Review the proposed architecture, modernization scope, delivery priorities, timeline, and budget. Work begins only after you approve the transformation plan and both teams agree on responsibilities, deliverables, and acceptance criteria.
Step 5
We modernize
Xpand redesigns unsupported architecture, converts or redevelops legacy functionality in AL, removes obsolete dependencies, adapts integrations, and establishes the required testing and release processes. Throughout delivery, the solution is checked against the applicable Microsoft technical validation requirements and AppSourceCop rules. Business Central is now extension-based, and apps submitted to Microsoft Marketplace must meet Microsoft’s current technical validation checklist.
Step 6
You validate and launch
You validate the modernized product against your functional, technical, installation, integration, and upgrade criteria. For Microsoft Marketplace products, Xpand prepares the app for submission and supports the resolution of validation findings, while Microsoft retains final approval authority. Products not intended for public publication can be prepared for the agreed private, customer-specific, cloud, hybrid, or on-premises delivery model.
Step 7
Continuous evolution and support
A complete path from legacy architecture to a maintainable, cloud-ready product prepared for Microsoft Marketplace or your chosen delivery model, with continued support as the platform evolves.
Contact us in any way you prefer
Frequently asked questions
Find answers to common questions about our services and solutions
Still have questions? We're here to help!
What is an ISV-to-SaaS transformation?
It is the technical modernization of an existing software product so it can be developed, deployed, updated, and maintained within a cloud-based product lifecycle.
Is converting C/AL code to AL enough?
Usually not. Language conversion does not automatically modernize architecture, dependencies, integrations, data handling, testing, packaging, deployment, or release management.
Must the app be published in Microsoft Marketplace?
No. Marketplace is one option. A solution may also be maintained on-premises or deployed as a customer-specific per-tenant extension where that model is appropriate.
Can Xpand guarantee Marketplace approval?
No. Xpand can assess, modernize, validate, package, and prepare the product, but Microsoft controls the final certification and publication decision.
Can Xpand support an existing Marketplace app?
Yes. The scope can include version compatibility, analyzer issues, technical debt, new releases, integrations, QA, and continued product development.