# Solving Dynamics 365 — Migration guides, full text > A practical reference for Microsoft Dynamics 365, Business Central, and the Microsoft business apps ecosystem — guides, comparisons, pricing, troubleshooting, and a glossary. 7 guides in this category. Author: Emil Björk, Microsoft business apps consultant, Gothenburg. Site index: https://www.solvingdynamics365.com/llms.txt. Every guide, every category: https://www.solvingdynamics365.com/llms-full.txt. --- # Business Central vs Dynamics NAV What changed in the move from Dynamics NAV to Business Central, and what that means for organisations still running NAV. Source: https://www.solvingdynamics365.com/guides/business-central-vs-dynamics-nav Section: Migrations Published: 2026-05-01 Updated: 2026-08-31 ### Key facts - The application core is unchanged — posting groups, dimensions, the general journal, and item costing carry over from NAV almost entirely; what changed is the wrapper: web client, AL extensions, twice-yearly updates, and per-user subscription licensing. - NAV's last version (NAV 2018) is in extended support only into 2028, after which there are no further security patches at all — mainstream support has already ended for every NAV version. - No C/AL customisation ports directly to Business Central — every base-object modification must be rebuilt as an AL extension, which is why heavily customised NAV migrations run as re-implementations, not database upgrades. - There is no alternative successor to NAV — the only realistic paths are Business Central Online (the default Microsoft's tooling targets), Business Central on-premises, or staying on NAV as a short, defensible bridge of at most a couple of years. Business Central is the direct successor to Dynamics NAV — same posting routines, same dimensions, same general ledger logic — but the operating model around it is fundamentally different. If you're still running NAV, understanding those differences is the key to scoping a sensible upgrade project. ## Deployment NAV was overwhelmingly on-premise, installed on customer-managed Windows servers and SQL Server. Business Central is **SaaS-first**: Business Central Online runs on Azure in Microsoft data centres, with Microsoft owning patching, infrastructure, and twice-yearly platform updates. On-premise Business Central exists but the vast majority of new implementations are cloud. ## Customisation model This is the biggest single change. NAV was customised through the **C/AL** language and the *base object* model: partners modified Microsoft's own objects directly. Upgrades were slow and expensive because every modification had to be re-merged. Business Central replaces C/AL with **AL** and an **extension** model — partners ship code as separate, side-by-side AL extensions, and the base application stays untouched. Upgrades happen automatically twice a year, with extensions tested against the new platform in advance. ## User interface NAV's Windows client is gone. Business Central is fully web-based, with first-class **mobile**, **Outlook**, and **Teams** experiences, plus an embedded **Copilot** for sales line suggestions, bank reconciliation, and other tasks. ## Release cadence NAV shipped roughly once a year with a long support tail. Business Central ships **two major updates per year** (Wave 1 in April, Wave 2 in October) plus monthly hotfixes, with mandatory updates on a customer-defined window. ## Licensing NAV was a perpetual license with annual maintenance. Business Central is a per-user subscription — Essentials, Premium, or Team Member. ## What stays the same It's worth saying clearly, because the marketing makes BC sound like a different product: the application core is NAV. Posting groups, dimensions, the general journal, item costing, the way a sales order flows to a posted invoice — a NAV finance user sits down in Business Central and recognises everything within an hour. NAV skills transfer almost completely; what changes is the technology wrapper and the commercial model. That matters when you plan training: budget for "where did my button go" web-client orientation, not for re-learning the ERP. ## The support clock Mainstream support for every NAV version has ended; the last version, NAV 2018, is in extended support, and that runs out too — into 2028, after which there are no security patches at all. Nothing stops a NAV system from running past that date, but each year the surrounding world moves: TLS requirements, bank formats, e-invoicing mandates, Windows Server versions, and the shrinking pool of C/AL developers willing to maintain it. Most organisations don't leave NAV because it stopped working; they leave because compliance or integration requirements finally demand something the old platform can't do, usually at the least convenient moment. Planning the move on your own schedule is strictly better than doing it under a deadline. ## The three realistic paths 1. **NAV → Business Central Online (SaaS).** The default and what Microsoft's tooling targets. Data migrates via the [cloud migration tooling](https://www.solvingdynamics365.com/guides/migrating-from-nav-on-premise-to-bc-saas); code gets rebuilt as AL extensions. You give up direct database access and server control, and gain automatic updates and the full cloud surface (Copilot, Power Platform connectors, telemetry). 2. **NAV → Business Central on-premise.** Same modern application, self-hosted. Legitimate when data residency or a hard dependency on direct SQL access forces it, but you keep the infrastructure burden and lose the cloud-only features — see [BC on-premise vs SaaS](https://www.solvingdynamics365.com/guides/business-central-onprem-vs-saas) before choosing this deliberately rather than by inertia. 3. **Stay on NAV, contained.** Defensible only as a short bridge — e.g. a company being sold or absorbed within two years. As a strategy it just moves the project later and makes it more expensive. ## The upgrade path in practice Microsoft provides tooling that lifts NAV data into Business Central, but custom C/AL modifications must be **re-built as AL extensions**. For heavily customised NAV deployments, the project often looks more like a re-implementation than a database upgrade, which is why many customers use the move as an opportunity to clean house. That clean-house step is where projects are won. A typical fifteen-year NAV database carries hundreds of modifications nobody can explain, half of which duplicate features Business Central now ships standard (approval workflows, item attributes, bank feeds) or that an AppSource app covers. The right sequence is: inventory the customisations, kill everything that standard BC or an [ISV add-on](https://www.solvingdynamics365.com/guides/common-business-central-isv-addons) covers, and rebuild only the genuinely differentiating remainder in AL. Teams that skip the inventory and port everything one-to-one pay twice — once to rebuild code they didn't need, and again at every [release wave](https://www.solvingdynamics365.com/guides/business-central-release-waves) when it has to be maintained. ## How to decide If you're on NAV today, the question is no longer *whether* Business Central — Microsoft ships no alternative successor — but *when* and *how much to re-implement*. Lightly customised NAV: migrate data, adopt standard, done in months. Heavily customised NAV: treat it as a re-implementation with data history migration as a scoped decision (many teams bring opening balances and open documents only, keeping the NAV database read-only for lookups). Either way, the cost driver is your customisation debt, not the software. ### Frequently asked questions **Is Business Central the same product as Dynamics NAV?** The application core is NAV — posting groups, dimensions, the general journal, item costing, and document flows are recognisable within an hour. What changed is the wrapper: a web client instead of Windows, AL extensions instead of C/AL base-object modification, twice-yearly automatic updates, and per-user subscription licensing. **When does NAV support end?** Mainstream support has ended for every NAV version. NAV 2018, the last release, is in extended support into 2028, after which there are no security patches at all. Most organisations leave earlier because a compliance, banking, or e-invoicing requirement forces the move. **Do NAV customisations carry over to Business Central?** No. C/AL modifications to base objects must be rebuilt as AL extensions. Inventory the customisations first, drop everything that standard Business Central or an AppSource app now covers, and rebuild only the genuinely differentiating remainder. **What are the realistic paths off NAV?** NAV to Business Central online (the default that Microsoft's tooling targets), NAV to Business Central on-premises when data residency or direct SQL access truly forces it, or staying on NAV as a short bridge of at most a couple of years. There is no alternative successor. --- # Business Central vs Finance and Operations When Business Central is the right ERP, when you've outgrown it, and how the move to Dynamics 365 Finance and Supply Chain Management actually goes. Source: https://www.solvingdynamics365.com/guides/business-central-vs-finance-and-operations Section: Migrations Published: 2026-08-27 Updated: 2026-08-27 ### Key facts - Rough size line: under about 100 concurrent ERP users and around €200M revenue, Business Central almost always fits; above about 500 users and €500M+ revenue, F&O almost always fits — the middle zone is decided by operational shape, not headcount. - There is no in-place upgrade path from Business Central to Finance and Operations — moving is a re-implementation with a different data model and tooling, not a migration wizard. - A typical F&O migration runs 10+ months to go-live for mid-size scope, up to 24 months for a global template, at roughly 3-10x a comparable Business Central implementation cost. - F&O's Dual-write gives real-time bidirectional sync to Dataverse-based CRM apps (Sales, Customer Service); Business Central integrates to them via connectors and Power Automate flows instead. The "Business Central or Finance and Operations" question comes up in almost every Microsoft ERP conversation, and the honest answer is that they solve different problems for different organisations. This guide walks the criteria that actually decide, in the shape they surface in real projects. Business Central (BC) is the SaaS ERP for small and mid-sized businesses — descendant of Dynamics NAV. Dynamics 365 Finance and Supply Chain Management (F&O) is the enterprise ERP — descendant of Dynamics AX. Both are Microsoft products, both are Dynamics 365, both run on Azure. Everything else about them is different: architecture, extensibility model, licensing, and the shape of the implementation. ## The rough size line For fast triage, the rules of thumb: below roughly 100 concurrent ERP users and around €200M revenue, Business Central is almost always the right choice. Above roughly 500 users and €500M+ revenue, F&O is almost always right. In between is the interesting zone, and headcount alone does not decide. The deciding factors above the numbers are the shape of the operations, not the raw scale. ## When Business Central is right Business Central fits when the business: - Runs in a small number of legal entities — one, maybe a handful. - Has straightforward accounting: one chart of accounts per country, one currency dominant, standard VAT / sales tax with a country localisation available. - Has moderate operational complexity: multi-location warehousing, light assembly or trade goods, jobs and project accounting for services. - Wants a fast time-to-value: a 3–6 month implementation is the expected shape. - Has a partner-led model rather than an internal ERP platform team. A business at 300 users running BC well is normal. A business at 800 users running BC well exists but is less common — usually because the operational complexity is genuinely simple even at scale. The extensibility model (AL extensions, monthly updates, non-breaking upgrades) is the platform's biggest structural advantage. Once configured, BC keeps updating itself and the extensions come along for the ride. The trade-off is a lower ceiling on customisation depth. ## When Finance and Operations is right F&O fits when the business has one or more of: **Multi-entity complexity.** More than a handful of legal entities, especially across countries with different currencies, statutory frameworks, and tax rules. F&O's shared master data (data-sharing policies, global address book) and its per-entity posting layers were built for this. **Deep manufacturing.** Process manufacturing with formulas, co-products, batch attributes, and catch weight. Advanced discrete manufacturing with engineering change management and configure-to-order. Manufacturing execution integration. BC has light manufacturing; F&O has enterprise manufacturing. **Advanced warehousing.** Directed put-away and picking, wave and load management, license plate tracking, cluster picking, high-volume warehouse operations. BC has basic warehousing; F&O's Advanced Warehouse Management is a serious WMS in its own right. **Retail / commerce.** POS, e-commerce, clienteling — Dynamics 365 Commerce runs on F&O infrastructure. If the business is retail-first, F&O is the platform whether or not the finance workload alone would justify it. **Regulatory complexity.** Public sector, defence contracting, life sciences with FDA validation, industries with heavy audit and reporting requirements. F&O's localisation depth, Electronic Reporting framework, and audit trail were built for this workload. **Internal platform capability.** F&O implementations succeed when there is an internal team who own the platform — configuration, governance, upgrades, integrations. Without that team, even the best SI can only carry the deployment so far. If the business does not have and will not build that capability, F&O will be a mismatch regardless of the requirements. ## Where the choice is genuinely hard The middle zone — say 100 to 500 users, one to five legal entities, moderate complexity — is where both platforms plausibly work. What breaks the tie: **Is the operational complexity growing?** If the business is growing into more entities, more countries, more product complexity, F&O's ceiling matters more than BC's speed. If the business is stable in shape, BC's simpler operating model wins. **Is there a manufacturing story?** BC can handle light manufacturing but the depth ends quickly. If manufacturing is central and non-trivial, lean toward F&O even at lower headcount. **How much integration to Microsoft business apps?** Both integrate to Sales, Customer Service, Marketing, Copilot Studio. F&O has **Dual-write** for real-time bidirectional sync to Dataverse; BC uses connectors and Power Automate flows. For deep integration to the CRM apps, F&O has the edge. **How mature is the internal IT team?** F&O demands more platform maturity from the customer. A team that runs a couple of SaaS applications well is BC-ready; F&O needs the muscle to run a genuine enterprise platform. ## What the migration looks like The "we've outgrown BC" migration to F&O is a re-implementation, not an upgrade. There is no in-place migration path — the data models, the extensibility model, and the tooling are fundamentally different. Typical shape: 1. **Business case and platform decision.** Six weeks to three months. Confirms F&O is the target and quantifies the change. 2. **Design and build.** Six to eighteen months, depending on scope. A global template gets built, tested against the current business processes, and refined. 3. **Data migration.** Master data (customers, vendors, items, chart of accounts) moves first, transactional data last. History typically stays in BC in read-only form; only current-year balances and open transactions move. 4. **Cutover.** A weekend cutover for a single entity, phased for multi-entity groups. 5. **Steady state.** F&O runs on the Wave release cadence like BC — but the internal team has to keep up with a much larger platform. Ten-plus months from signature to go-live is typical for a mid-size migration; twenty-four months is not unusual for a global template. Budget rule of thumb: the F&O implementation costs 3–10× a comparable BC one. Because of that cost profile, "migrate to F&O" is almost never the right answer if BC still meets the requirements. Force the "why now" question. The best migrations are triggered by concrete requirements BC cannot meet — a new acquisition adding twenty entities, a manufacturing site whose complexity BC cannot model, a compliance regime that BC's localisation does not cover. ## Running both Some groups run both. F&O centrally for the large entities where the depth is needed, BC in smaller subsidiaries where a full F&O footprint is overkill. Microsoft's guidance in this scenario is that BC subsidiaries consolidate into F&O for group reporting through standard integrations, and that the manufacturing / operational depth stays where it belongs. It is a valid pattern for global groups; it also adds an integration layer that has to be owned by someone. ## The short version Pick BC when the business is under a few hundred users, has straightforward operations, wants a fast implementation, and does not have — or want to build — an internal ERP platform team. Pick F&O when the business runs across many entities and countries, has deep manufacturing or warehousing, sits in a regulated industry, or already has the internal muscle to own an enterprise platform. In the middle, force the "what specifically about the operations requires F&O" question. If nothing specific requires it, BC almost always wins on total cost of ownership. ## Where to go next Unsure which way your answers lean? The [BC vs F&O fit scorer](https://www.solvingdynamics365.com/tools/bc-vs-fo-fit) is an eight-question directional check. For each product in depth, [what is Business Central](https://www.solvingdynamics365.com/guides/what-is-business-central) and [what is Dynamics 365 Finance](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-finance). If you are already on Business Central and hitting the line, [growing from Business Central to Finance and SCM](https://www.solvingdynamics365.com/guides/growing-from-business-central-to-finance-and-scm) covers the move. The licensing side is [Dynamics 365 licensing explained](https://www.solvingdynamics365.com/guides/dynamics-365-licensing-explained), with current prices for [Business Central](https://www.solvingdynamics365.com/pricing/business-central) and [Finance and Operations](https://www.solvingdynamics365.com/pricing/finance-and-operations). ### Frequently asked questions **What is the rough size line between BC and F&O?** Below roughly 100 concurrent ERP users and around 200M euro revenue, Business Central is almost always right. Above roughly 500 users and 500M+ euro revenue, F&O is almost always right. In between, the deciding factor is operational shape — entities, manufacturing depth, warehousing, regulatory load — not headcount. **Can a large company run Business Central?** Yes. A business at 300 users running BC well is normal, and 800-user BC deployments exist — usually where the operational complexity is genuinely simple even at scale. Raw user count alone does not force F&O. **What does F&O demand that BC does not?** An internal platform team. F&O implementations succeed when an internal team owns configuration, governance, upgrades and integrations. Without that capability, F&O is a mismatch regardless of requirements — BC's partner-led model is far more forgiving. **When does deep manufacturing force F&O?** Process manufacturing with formulas, co-products, batch attributes and catch weight, or advanced discrete manufacturing with engineering change management and configure-to-order. BC has light manufacturing; F&O has enterprise manufacturing. --- # Growing from Business Central to Finance and SCM When and how to move from Business Central up to Dynamics 365 Finance and Supply Chain Management — signals, scope, and the migration path. Source: https://www.solvingdynamics365.com/guides/growing-from-business-central-to-finance-and-scm Section: Migrations Published: 2026-05-01 ### Key facts - Business Central handles five to twenty legal entities comfortably, with thirty becoming friction and fifty painful, while Finance and Supply Chain Management is built to handle hundreds. - Moving from Business Central to F&SCM is a full re-implementation, not a data migration — master data migrates with substantial mapping, but transactions typically migrate only as opening balances. - BC's AL extensions do not run on F&SCM and require X++ rebuilds, while Power Platform-based customisations such as flows and apps port more cleanly since they sit above the application. - F&SCM's operating rhythm differs culturally from BC's — Service Updates roughly every six weeks instead of two release waves a year, Lifecycle Services for environment management, and role-based security with segregation of duties. - A middle option exists for many growing companies: stay on Business Central and add ISV modules or sister products like Dynamics 365 Sales, since a premature move to F&SCM is one of the most expensive mistakes a growing business can make. For most SMB customers, Business Central is the long-term home — they grow into it, customise it, and stay there. But a meaningful minority outgrow BC and need to step up to **Dynamics 365 Finance and Supply Chain Management** (F&SCM, the F&O apps). Recognising the right moment, planning the transition properly, and avoiding doing it prematurely all matter. **Signals that you're outgrowing BC.** - **Legal-entity count.** BC handles five to twenty legal entities comfortably; thirty becomes friction; fifty is painful. F&SCM handles hundreds. - **User count.** Over 200–300 named users in a single tenant, BC starts to feel constrained even though Microsoft supports more on paper. F&SCM is built for thousands of users. - **Statutory reporting complexity.** When you operate in 10+ countries with complex local requirements, BC's localization-by-localization model gets hard. F&SCM has broader country coverage built-in and an Electronic Reporting engine for the gaps. - **Operational complexity.** Multi-mode manufacturing (discrete + process + lean in one company), advanced warehouse with high-volume automation, sophisticated demand sensing, multi-country transportation management — these are what F&SCM has and BC doesn't. - **Consolidations.** BC handles consolidation of a small group; for 30+ subsidiaries with intercompany complexity, F&SCM is better suited. - **Volume.** BC scales to many gigabytes; F&SCM scales to multi-terabyte transactional databases. ## Signals that you're not Don't move up because: - You've heard F&SCM is "the proper ERP". Both are real ERPs; the right choice depends on fit. - A consultant is recommending it without specific evidence of BC limits you're hitting. - You want flexibility "in case". F&SCM's complexity and cost don't justify hypothetical future needs. ## The migration path A BC → F&SCM move is a full re-implementation, not a data migration. The two products share concepts but very different schemas, processes, and customisation models. - **Data.** Master data (chart of accounts, customers, vendors, items) migrates with substantial mapping; transactions typically migrate as opening balances only. - **Customisations.** BC's AL extensions don't run on F&SCM. X++ rebuilds are required. Power Platform-based customisations (flows, apps) port more cleanly because they sit above the application. - **Integration.** Most integrations rebuild because the APIs and connectors differ. - **Time and cost.** Multi-month to multi-year project. Plan for re-running implementation, including business process design, training, and substantial change management. ## The cultural shift F&SCM operates differently from BC. Service Updates every six weeks (not twice a year), LCS for lifecycle management, role-based security with SoD, X++ for in-platform code — these are all real differences in how teams work. ## The middle option Some customers stay on BC and run F&SCM-style modules through ISV add-ons or sister-product subscriptions (e.g. Dynamics 365 Sales for CRM-side scale alongside BC for ERP). This keeps a foot in both. ## Decide deliberately A premature move from BC to F&SCM is one of the most expensive mistakes a growing business can make. A delayed move is a missed opportunity for scale. The honest signal of "we're hitting BC's limits in *this specific way*" is what should drive the decision. ## Where to go next The comparison that frames the decision is [Business Central vs Finance and Operations](https://www.solvingdynamics365.com/guides/business-central-vs-finance-and-operations); the destination is described in [what is Dynamics 365 Finance](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-finance) and [what is Supply Chain Management](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-supply-chain). The operating model you are moving into is [One Version and updates](https://www.solvingdynamics365.com/guides/dynamics-365-one-version-and-updates), and the cost is on the [Finance and Operations pricing page](https://www.solvingdynamics365.com/pricing/finance-and-operations). ### Frequently asked questions **What signals that a company has outgrown Business Central?** Thirty or more legal entities, more than 200–300 named users in one tenant, statutory complexity across 10+ countries, multi-mode manufacturing or high-volume warehouse automation, complex consolidations of 30+ subsidiaries, or multi-terabyte transaction volumes. **Is moving to Finance and Supply Chain a data migration?** No — it is a full re-implementation. Master data migrates with substantial mapping, transactions usually go as opening balances only, AL extensions do not run on F&SCM and need X++ rebuilds, and most integrations are rebuilt. Power Platform customisations port more cleanly. **What changes culturally?** Service updates roughly every six weeks instead of two waves a year, Lifecycle Services for environment management, role-based security with segregation of duties, and X++ for in-platform code. **Is there a middle option?** Yes: stay on Business Central and add ISV modules or sister products such as Dynamics 365 Sales for CRM-side scale. A premature move up is one of the most expensive mistakes a growing business can make. --- # Migrating from NAV on-premise to Business Central SaaS Moving from Dynamics NAV on-premise to Business Central SaaS — the cloud migration tool, AL code rebuild, and the operational changes that come with it. Source: https://www.solvingdynamics365.com/guides/migrating-from-nav-on-premise-to-bc-saas Section: Migrations Published: 2026-05-01 ### Key facts - Microsoft's Cloud Migration tool supports NAV 2015 and later out of the box; earlier versions need an intermediate upgrade first before the tool can connect. - Every C/AL customisation, however small, must be rewritten as an AL extension, since direct modification of Microsoft's base objects does not exist in Business Central SaaS. - A lightly-customised NAV estate typically takes a few months to rebuild, while a heavily-customised one with thousands of modifications takes a year or more — and is also the moment to rationalise unused customisations. - BC SaaS exposes only the v2.0 REST API and custom AL API pages, so NAV integrations built on C/AL web services, NAS services, or third-party middleware must be rebuilt against those endpoints. - End-to-end migration typically takes 6 to 18 months depending on customisation depth — the migration tool itself moves data in days, but rebuilding customisations, integrations, and reports is the actual project. A large installed base of Dynamics NAV customers — running NAV 2013 through NAV 2018 on their own infrastructure — is steadily moving to Business Central SaaS. Microsoft has invested heavily in this path because every NAV-to-BC migration consolidates a customer into the modern, managed cloud where Microsoft prefers them. Tooling has improved substantially over the past few years. ## The official path Microsoft ships the **Cloud Migration tool** for NAV → Business Central SaaS. It: - Connects to the on-premise NAV database via an installed extension. - Maps NAV tables to BC tables, including standard application data and customer customisations. - Replicates the data into a BC SaaS tenant. - Supports an iterative model: re-run the migration, refining over time until the BC tenant is good to cut over to. Supported NAV versions are NAV 2015 and later; earlier versions need an intermediate upgrade. ## The two big challenges Data is the lesser of the two. The bigger ones are: 1. **Customisations in C/AL must be rebuilt as AL extensions.** NAV's customisation model — direct modification of Microsoft's base objects in C/AL — doesn't exist in BC SaaS. Every customisation, however small, must be rewritten as an AL extension. For lightly-customised customers (a few dozen modifications) this is a few months of work. For heavily-customised customers (thousands of modifications), it's a year or more — and an opportunity to rationalise. 2. **Operational habits change.** On-premise NAV ran on the customer's own SQL Server, with full DBA access, server-side jobs, and the ability to modify anything. BC SaaS runs in Microsoft's cloud, with no SQL access, mandatory release waves, API-only integration, and constrained extensibility. Customers used to direct database access must adapt to standard APIs and AL extensibility. **Strategic options.** - **Lift and shift.** Migrate data and rebuild customisations as exact AL replicas. Fastest path but carries forward bloat. - **Fit-to-standard.** Use the migration to re-evaluate every customisation against modern standard BC. Many turn out to be unnecessary (BC has caught up with what custom code used to do). Slower migration but cleaner long-term position. - **Hybrid.** Critical-path customisations get rebuilt; nice-to-haves get re-evaluated and often dropped. Most successful migrations are hybrid. ## Integration rebuild NAV integrations were typically built with **C/AL web services**, **NAS services**, or **third-party middleware**. BC SaaS exposes only the v2.0 REST API and custom AL API pages. Most integrations rebuild; in many cases simpler than before. ## Reporting rebuild NAV's classic RDLC reports and Excel layouts mostly survive in BC SaaS, but C/AL-based report customisations need re-implementation in AL. ## Customer expectations Set them up front. On the day of cutover, the BC SaaS tenant has fewer features than the old NAV (everything that wasn't ported) and a different operating cadence (release waves). This is the cost of getting to a maintained, modern, managed system; communicate it clearly. ## Time to live 6 to 18 months depending on customisation depth. The migration tool moves the data in days; the rebuild is the project. ## Where to go next The context for the move is [Business Central vs Dynamics NAV](https://www.solvingdynamics365.com/guides/business-central-vs-dynamics-nav), and the choice you are also making is [on-premises vs SaaS](https://www.solvingdynamics365.com/guides/business-central-onprem-vs-saas). Rebuilding customisations starts with [writing your first AL extension](https://www.solvingdynamics365.com/guides/writing-your-first-al-extension) and replacing many of them with [ISV add-ons](https://www.solvingdynamics365.com/guides/common-business-central-isv-addons); the data side is [Business Central data migration](https://www.solvingdynamics365.com/guides/business-central-data-migration). ### Frequently asked questions **Which NAV versions can use the cloud migration tool?** NAV 2015 and later. Earlier versions need an intermediate upgrade first. The tool connects to the on-premises database, maps NAV tables to Business Central, replicates iteratively, and lets you re-run until the SaaS tenant is ready for cutover. **What happens to C/AL customisations?** They must be rewritten as AL extensions — there is no direct modification of base objects in Business Central online. A lightly customised NAV takes a few months; thousands of modifications take a year or more and are an opportunity to rationalise. **What operational habits change after the move?** No SQL access, mandatory release waves, API-only integration, and constrained extensibility. Teams used to direct database access and server-side jobs must adapt to standard APIs and AL. **How long does a NAV to Business Central migration take?** Six to eighteen months depending on customisation depth. The tool moves data in days; rebuilding customisations, integrations, and report logic is the project. --- # Migrating from NetSuite to Business Central Moving from NetSuite to Business Central — the data and customisation challenges, the cost angle, and what to expect from the project. Source: https://www.solvingdynamics365.com/guides/migrating-from-netsuite-to-business-central Section: Migrations Published: 2026-05-01 ### Key facts - NetSuite classes, departments, and locations map to Business Central dimensions, while the chart of accounts, items, customers, and vendors map directly across. - No NetSuite customisation ports directly — SuiteScript becomes AL codeunits with event subscribers, SuiteFlow becomes BC workflows or Power Automate, SuiteAnalytics reports become Power BI, and SuiteCommerce is typically replaced by Shopify, Sana, or a headless front end. - Customers running 20 or more legal entities with complex consolidations should evaluate Dynamics 365 Finance rather than Business Central; for 5-15 entities with moderate complexity, BC is usually sufficient. - Data comes out of NetSuite through SuiteAnalytics or saved searches, is transformed in Data Factory or Power Query, and loads into BC through configuration packages or the REST API, with historical detail usually staying in NetSuite read-only. - A typical NetSuite-to-Business-Central migration for a mid-sized customer runs 6 to 18 months, dominated by configuration, customisation rebuild, and parallel running. NetSuite-to-Business-Central migrations are not as common as QuickBooks or SAP B1 migrations, but they do happen — typically driven by cost (NetSuite per-user pricing scales aggressively), by Microsoft 365 integration preferences, or by partner ecosystem in specific countries. The migration is doable but not trivial; both products are real ERPs and the data and customisation footprints are usually substantial. ## Why customers consider it Common triggers: - **Total cost of ownership.** NetSuite list pricing tends to escalate as user count and module footprint grow. Business Central licence costs are usually meaningfully lower for the same headcount. - **Microsoft 365 alignment.** Customers heavily invested in Microsoft 365 (Teams, SharePoint, Power BI) often find BC's tighter integration more productive than NetSuite's connectors. - **Partner ecosystem.** In some markets (DACH, Nordics, parts of Asia), the Microsoft partner base is broader and more accessible than the NetSuite consulting base. ## Why customers stay on NetSuite Equally common: deep customisation already in place, industry-specific NetSuite modules (SuiteCommerce, advanced revenue management) without direct BC equivalents, or established global multi-entity consolidations. ## Data migration NetSuite exports cleanly via its **SuiteAnalytics** API or **Saved Searches** exports. Standard approach: 1. Inventory the NetSuite data model — standard objects, custom records, custom fields. 2. Map to BC equivalents — chart of accounts, dimensions (NetSuite *classes*, *departments*, *locations* map to BC dimensions), items, customers, vendors. 3. Pull data via the API, transform with Azure Data Factory or Power Query, load to BC via Configuration Packages or REST API. Open transactions, balances, and the master data migrate; historical detail typically stays in NetSuite read-only. ## Customisation NetSuite customisations live in SuiteScript (JavaScript), SuiteFlow, and SuiteBuilder. None of this ports directly. The rebuild path: - Standard fields and forms → BC's table extensions and page extensions in AL. - SuiteFlow workflows → BC's built-in workflows or Power Automate flows. - SuiteScript business logic → AL codeunits with event subscribers. - SuiteAnalytics reports → Power BI. - SuiteCommerce e-commerce → typically Shopify, Sana, or a custom Power Pages + headless front end. Many customisations turn out to be workarounds for NetSuite features BC implements differently — re-do the fit-gap honestly before committing to rebuild. ## Multi-entity and consolidations NetSuite OneWorld is strong at multi-subsidiary consolidations. BC's multi-company is real but less feature-rich. Customers running 20+ legal entities with complex consolidations should evaluate whether **Dynamics 365 Finance** is the right step rather than BC. For 5–15 entities with moderate complexity, BC is usually sufficient. ## Integration rebuild NetSuite's connector library is wide; BC's is wide too but the specific connectors differ. Audit every NetSuite integration and budget the rebuild. ## Time to live Substantial. Typical NetSuite-to-BC migrations are 6 to 18 months for a mid-sized customer, dominated by configuration, customisation rebuild, and parallel running. ## Where to go next The decision itself is [Business Central vs NetSuite](https://www.solvingdynamics365.com/guides/business-central-vs-netsuite); running both during the move is [integrating with NetSuite during migration](https://www.solvingdynamics365.com/guides/integrating-dynamics-365-with-netsuite-during-migration). Design the target with [dimensions design](https://www.solvingdynamics365.com/guides/business-central-dimensions-design) and [multi-company setup](https://www.solvingdynamics365.com/guides/business-central-multi-company-setup) — and if the entity count is high, read [growing from Business Central to Finance and SCM](https://www.solvingdynamics365.com/guides/growing-from-business-central-to-finance-and-scm) before committing. ### Frequently asked questions **Why do companies move from NetSuite to Business Central?** Total cost of ownership as NetSuite per-user pricing escalates, tighter Microsoft 365 integration, and broader Microsoft partner coverage in markets such as DACH, the Nordics, and parts of Asia. Companies with deep SuiteScript customisation or SuiteCommerce dependencies often stay. **How does NetSuite data map to Business Central?** Classes, departments, and locations become Business Central dimensions; the chart of accounts, items, customers, and vendors map directly. Data comes out through SuiteAnalytics or saved searches, is transformed in Data Factory or Power Query, and loads through configuration packages or the REST API. Historical detail usually stays in NetSuite read-only. **What happens to SuiteScript and SuiteFlow customisations?** Nothing ports. SuiteScript logic becomes AL codeunits with event subscribers, SuiteFlow becomes BC workflows or Power Automate, SuiteAnalytics reports become Power BI, and SuiteCommerce is typically replaced by Shopify, Sana, or a headless front end. **Is Business Central the right target for a large NetSuite OneWorld group?** For 5–15 entities with moderate consolidation complexity, yes. For 20+ legal entities with complex consolidations, evaluate Dynamics 365 Finance instead. --- # Migrating from QuickBooks to Business Central Moving from QuickBooks to Business Central — the data migration wizard, scope decisions, parallel running, and the gotchas that catch people out. Source: https://www.solvingdynamics365.com/guides/migrating-from-quickbooks-to-business-central Section: Migrations Published: 2026-05-01 ### Key facts - Business Central's Data Migration assisted setup includes a first-party QuickBooks Online connector that reads data through the Intuit API and migrates the chart of accounts, customers, vendors, items, employees, bank accounts, and opening balances. - Most projects migrate trial balance plus open transactions at a fiscal period boundary rather than full historical detail, keeping QuickBooks read-only for a year for historical inquiries, audit, and tax filing. - Inventory should be physically counted and reconciled in QuickBooks before it is migrated, since QuickBooks inventory tracking is famously light and many customers carry years of inaccuracy in it. - SMB customers typically do a hard cut at month-end rather than run parallel, since parallel running both systems at once is rarely practical at that scale. - A focused QuickBooks-to-Business-Central migration typically runs 8 to 16 weeks for a small SMB, including configuration, testing, and training. QuickBooks-to-Business-Central is one of the most common Dynamics 365 migration paths — typical of SMBs that have outgrown QuickBooks Online or QuickBooks Desktop and need real ERP capability. Microsoft ships a **first-party data migration wizard** for the QuickBooks Online source specifically, which lowers the technical bar substantially. ## Why customers move Common triggers: multi-entity needs (QB struggles past a handful), inventory complexity beyond QB's modest inventory module, multi-currency at scale, integration burden between QB and other systems, advanced reporting that QB can't deliver, and the desire to consolidate to Microsoft 365 + ERP under one vendor. ## The migration wizard From Business Central, the **Data Migration** assisted setup includes a QuickBooks Online connector that: - Reads QuickBooks data via the Intuit API. - Maps the chart of accounts (with manual review for the inevitable mismatches). - Migrates customers, vendors, items, employees, and bank accounts. - Brings opening balances at a chosen cut-off date. - Optionally brings transactional history (open invoices, open bills, open POs). The wizard handles the mechanical translation; the customer handles the strategic decisions. **Scope decisions.** - **Cut-off date.** Most projects pick a fiscal period boundary (month-end, quarter-end, year-end). Year-end gives the cleanest start; mid-year is feasible but requires more reconciliation. - **Historical detail.** Trial balance only? Open transactions? Full historical detail? The wizard can pull full detail but the labour to validate and reconcile rises sharply with depth. Most projects migrate balances + open transactions, leaving full detail in QuickBooks (read-only) for reference. - **Chart of accounts.** Business Central's chart of accounts is more structured than QuickBooks' and supports dimensions. Use the migration as an opportunity to clean up — but don't conflate cleanup and migration; cleanse in QuickBooks first, then migrate the clean version. ## Inventory caveat QuickBooks inventory is famously light; many customers carry inventory inaccuracies for years. Don't migrate the inventory state until it's been physically counted and reconciled. Going live with wrong inventory is a one-way ticket to chaos. ## Parallel running vs hard cut SMB customers typically do a **hard cut** at month-end — stop QuickBooks postings, run the migration, start Business Central. Parallel running (both systems live simultaneously) is rarely practical at SMB scale; the team can't absorb double the work. ## Time to live A focused QB→BC migration runs 8 to 16 weeks for a small SMB, including configuration, testing, and training. Bigger or more complex businesses run longer. ## After migration QuickBooks stays available read-only for at least a year for historical inquiries, audit, and tax filing. Eventually it can be decommissioned with the data archived. ## The pitfall to avoid Don't treat this as a like-for-like swap. Business Central's strengths (dimensions, multi-entity, real inventory, posting controls) are different from QuickBooks's strengths. Configure to take advantage of BC, not to mimic QuickBooks. ## Where to go next Whether to move at all is [Business Central vs QuickBooks](https://www.solvingdynamics365.com/guides/business-central-vs-quickbooks); what it costs is on the [pricing page](https://www.solvingdynamics365.com/pricing/business-central). The design decisions that make the new system better than the old one are [dimensions design](https://www.solvingdynamics365.com/guides/business-central-dimensions-design) and [costing methods](https://www.solvingdynamics365.com/guides/business-central-costing-methods-compared); the mechanics are [Business Central data migration](https://www.solvingdynamics365.com/guides/business-central-data-migration). ### Frequently asked questions **Is there a built-in QuickBooks migration tool?** Yes. Business Central's Data Migration assisted setup includes a QuickBooks Online connector that reads data through the Intuit API and migrates the chart of accounts, customers, vendors, items, employees, bank accounts, opening balances, and optionally open transactions. **How much history should I migrate?** Most projects migrate balances plus open transactions at a fiscal period boundary and keep QuickBooks read-only for a year for historical inquiries, audit, and tax. Full historical detail is possible but the reconciliation labour rises sharply. **What should I fix before migrating?** Clean the chart of accounts in QuickBooks first — do not conflate cleanup with migration — and physically count and reconcile inventory before moving it. Going live with wrong inventory is a one-way ticket to chaos. **How long does a QuickBooks to Business Central project take?** Eight to sixteen weeks for a small SMB including configuration, testing, and training, usually with a hard cut at month-end rather than parallel running. --- # Migrating from SAP Business One to Business Central Moving from SAP Business One to Business Central — the practical mapping, data migration approach, and the choices that decide the project's complexity. Source: https://www.solvingdynamics365.com/guides/migrating-from-sap-business-one-to-business-central Section: Migrations Published: 2026-05-01 ### Key facts - Business Central ships no first-party migration wizard for SAP Business One, unlike the QuickBooks path — the standard approach exports data via CSV or direct SQL against HANA or SQL Server, cleanses offline, and imports through configuration packages or the REST API. - B1's cost centres and profit centres map to Business Central dimensions, which are richer, and most projects redesign the dimension structure and chart of accounts deliberately rather than carrying B1's shape forward unchanged. - B1 customisations built in the SAP B1 SDK, SQL queries, or formatted searches do not port and must be rebuilt as AL extensions where still needed after an honest fit-gap review. - Crystal Reports, which B1 relies on for reporting, do not run in Business Central and are replaced by Power BI for analytics and Word layouts for document reports. - A typical B1-to-Business-Central migration takes 4 to 9 months including configuration, integration rebuild, and testing, with training that specifically addresses B1's differing vocabulary and workflow. SAP Business One (B1) and Business Central compete for the same SMB ERP slot. Migrations between them go in both directions, but the more common direction in markets where Microsoft has strong partner coverage is **B1 → Business Central** — often driven by total-cost-of-ownership, Microsoft 365 integration, or partner preference. ## The functional fit SAP B1 and BC overlap heavily in scope: financials, sales, purchasing, inventory, light manufacturing, basic CRM, service management. Country localizations exist on both. The data models are different in detail (B1's posting model, item structure, and dimension equivalents diverge from BC's), but the conceptual mapping is straightforward. **Migration strategy.** - **Cut-off date.** Year-end is cleanest; quarter-end is feasible. Mid-year requires careful opening-balance handling. - **History.** Typically migrate balances + open transactions; leave detailed history in B1 read-only. - **Tools.** Unlike QuickBooks, BC does not ship a first-party B1 migration wizard. The standard approach is: - Export B1 data to CSV/Excel using B1's standard export tools or direct SQL queries against the HANA or SQL Server database. - Cleanse and transform offline. - Import to BC via Configuration Packages or the REST API. - Several ISVs publish dedicated B1-to-BC migration accelerators that automate the bulk of this. **Mapping concerns.** - **Chart of accounts.** B1's account structure and posting groups differ from BC's. Most projects redesign the chart of accounts using the migration as the catalyst. - **Dimensions.** B1 has dimension-like *cost centres* and *profit centres*; BC's dimensions are richer. Map deliberately — don't carry forward B1's structure unchanged. - **Items.** B1 has detailed item attributes (configurable), BOMs, prices, and tracking. BC's item card has different but largely equivalent functionality. Variants, attributes, and tracking need explicit mapping. - **Sales and purchasing documents.** Both products use a quote → order → delivery → invoice flow with similar mechanics. Open documents migrate as open BC documents with quantities and amounts preserved. - **Banking.** B1's bank module is more sophisticated in some countries; BC's bank reconciliation has caught up and now includes AI matching. ## Customisation rebuild B1 customisations are usually built in **SAP B1 SDK / SQL queries / formatted searches** — not portable to BC. Re-build them as **AL extensions** in BC. Many B1 customisations turn out to be unnecessary in BC once standard features are properly used; do the fit-gap honestly before committing to rebuild. ## Reporting B1 reports built in Crystal Reports won't run in BC. Replace with Power BI for analytical reporting and Word layouts for document reports. ## The change-management challenge B1 users are accustomed to a specific UI and a particular vocabulary. BC's terminology and workflow are similar but not identical. Plan training that explicitly addresses the differences, not generic BC training. ## Time to live A typical B1-to-BC migration is 4 to 9 months including configuration, integration rebuild, and testing. ## Where to go next The wider SAP-versus-Microsoft picture is [Dynamics 365 vs SAP](https://www.solvingdynamics365.com/guides/dynamics-365-vs-sap). Design the target with [dimensions design](https://www.solvingdynamics365.com/guides/business-central-dimensions-design), migrate with [Business Central data migration](https://www.solvingdynamics365.com/guides/business-central-data-migration), rebuild Crystal Reports with [document layouts and report design](https://www.solvingdynamics365.com/guides/document-layouts-and-report-design-in-business-central), and plan the difference-focused training with [training strategies](https://www.solvingdynamics365.com/guides/training-strategies-for-dynamics-365-rollouts). ### Frequently asked questions **Is there a Microsoft migration wizard for SAP Business One?** No. Unlike QuickBooks, Business Central ships no first-party B1 connector. The standard approach exports from B1 to CSV or via SQL against HANA or SQL Server, cleanses offline, and imports through configuration packages or the REST API; several ISVs sell B1-to-BC accelerators. **How do B1 cost centres and profit centres map?** To Business Central dimensions, which are richer. Redesign the dimension structure deliberately rather than carrying B1's forward unchanged, and most projects also redesign the chart of accounts. **What happens to B1 customisations and reports?** SDK code, SQL queries, and formatted searches do not port and are rebuilt as AL extensions where still needed. Crystal Reports are replaced by Power BI for analytics and Word layouts for documents. **How long does a B1 to Business Central migration take?** Four to nine months including configuration, integration rebuild, and testing, with training that explicitly addresses vocabulary and workflow differences.