How to handle ecommerce when you migrate from Sage X3 to Business Central

Short answer.

The answers usually point clearly at Abakion B2B Ecommerce, at Shopify, or at a rebuilt API integration, and knowing which one you're facing is worth more than assuming Sage X3 forces your hand.

Nothing forces a Sage X3 customer off Sage X3, so a move to Business Central is a deliberate downshift, usually after a divestment or an over-specified implementation. The web shop integration is the easy half: Sage X3's SOAP web services, REST calls and import templates all have Business Central API equivalents, and because Sage X3 runs on SQL Server or Oracle it clears the bar for Microsoft's new Generic Custom migration route, which went GA on 1 April 2026. What has no Business Central equivalent is the shape of the thing being integrated: product-site records, stock statuses, grouped price lists and a single folder holding several legislations.

Two routes stop the storefront becoming a second project: move B2C to Shopify with Microsoft's Shopify Connector, or move B2B into Business Central with Abakion B2B Ecommerce. For some Sage X3 businesses neither is enough, and this article says where that line falls.

What are the three options, and how do they compare?

There are three real options for ecommerce when you migrate from Sage X3 to Business Central, and for a Sage X3 customer the first one is a more serious contender than it is for most readers of this series.

1. Keep the storefront and rebuild the connection as an API integration. Your storefront is probably decent and your integration is probably competent. The connector market splits in a way worth checking: the platform-agnostic commerce vendors follow you, and Experlogix Digital Commerce for example supports both Sage X3 and Business Central, while the vendors that make Sage X3 tolerable operationally often don't exist on the other side, and Datalinx, which describes itself as the only global Sage developer specialising solely in barcoding and warehouse management, is Sage-only. So check your own stack in both directions before assuming continuity. If you keep this route, be clear about what you're buying, because you own the integration, you own the mapping, and you regression test it against a new Business Central major version twice a year.
2. Move B2C to Shopify and use Microsoft's Shopify Connector.
3. Move B2B into Business Central with the Abakion B2B Ecommerce app.

The other two remove that ownership, and they split by who you sell to.

Why would a Sage X3 customer move to Business Central at all?

Because the business changed shape, not because Sage X3 is ending.

If you're reading this, you're probably not being pushed. Sage X3 isn't going anywhere. Sage replatformed it, told shareholders in its 2025 annual report that the aim was a full cloud-native experience, and by the May 2026 half-year results it had launched Sage X3 as a fully managed cloud service. On-premises and private cloud are still sold. The lifecycle policy is a rolling 24 months per release: six months current, twelve standard, six extended, with releases landing around May and November.

So a move from Sage X3 to Business Central is nearly always a deliberate downshift, and there are only a few reasons for it. A division was sold and it came with a Sage X3 folder it can't afford to run. A group standardised on Business Central and one entity is the odd one out. Or Sage X3 was over-specified from the start, and after a few years somebody added up the licences, the hosting, the partner retainer and the two people who understand the dictionary, and asked what it would cost to run the same business on something smaller.

That's an entirely reasonable question. And the web shop is usually where it gets answered, because the storefront is the one part of the estate that asks the ERP a question on every single page load.

Your integration will port. The question is whether your company will fit.

One premise before we go further. Business Central here means Business Central online. Microsoft states that you can't install Marketplace apps on-premises, including in Docker-based deployments, so an on-premises Business Central would strand the entire connector ecosystem, and we won't cover it.

Is there a migration tool from Sage X3 to Business Central?

Not yet, but Sage X3 is the first system in this series that qualifies for one, because Sage X3 runs on SQL Server or Oracle and Microsoft's new migration framework is built for SQL sources.

Microsoft's cloud migration tool supports Business Central on-premises, Dynamics NAV, Dynamics GP 2015 and later, Dynamics SL 2015 and later, and any other SQL source using custom migrations. In 2026 release wave 1 Microsoft added a Generic Custom migration type, GA on 1 April 2026, with a standardised AL interface so a partner can build a reusable migration engine for a SQL-based source system and ship it through Microsoft Marketplace, with the same core capabilities as Microsoft's own engines for Business Central, Dynamics GP and Dynamics SL.

Microsoft's feature description never names a database platform, so whether an Oracle-backed Sage X3 folder qualifies is an open question rather than a no, and it's worth asking early.

What doesn't exist is an engine. Nobody has written the Sage X3 implementation, so somebody has to, and nothing about the web shop is inside its scope in any case. Master data, opening balances and setup are what these engines carry. Posted document history is a separate decision with its own budget.

Do Sage X3 web services work with Business Central?

No, but every pattern they implement has a Business Central equivalent, so this is a rewrite rather than a redesign.

A Sage X3 storefront is connected through one of four things.

The SOAP web services pool. You create a publication against a Sage X3 object, size a pool in the console, and consume it through the web server. Sage's own user interface now labels this route Classic SOAP web services, which tells you what Sage thinks of its future. Sage's public sample web portal shows the shape of a real integration: SOAP calls for sales orders, products and available stock, alongside GraphQL for purchasing, with JWT replacing basic authentication.

REST, through the classes and representations layer on the Syracuse web server.

Import and export templates. This is where it gets interesting, because a template can be invoked over SOAP through a standard web service. So in a lot of Sage X3 estates, what people call a web service integration is a SOAP call that runs a file-format import template. That works, and it will not be missed.

Direct SQL. Sage doesn't publish a licence clause forbidding it, but its own security guidance rules out the topology you'd need, saying that the server hosting the relational database must not be exposed over the network and that only the application and report servers should reach the database. Business Central online settles that argument permanently, because there's no database to reach and Microsoft states that the only supported option for reading data is using APIs.

There's one operational detail worth carrying into the design conversation. Sage's own sizing guidance says a Node.js process serves about 25 typical interactive user sessions, that a single processor core runs two to four of those processes, and that above 200 concurrent sessions you should be using a dedicated load balancer. Your storefront's API traffic has been competing with human sessions on that tier the whole time.

Business Central has its own ceiling instead, published as operational limits: 600 API requests per minute in production, 6,000 per user in a five-minute sliding window, five concurrent requests and 100 connections per user, 200 webhook subscriptions, and an eight-minute operation timeout. Neither number is a problem for a normal B2B shop. Both are worth writing down before anyone designs a per-page-load integration.

Do product codes still fit when moving from Sage X3 to Business Central?

Yes, mostly, and that makes Sage X3 unusual in this series. The field lengths are fine and the model is what breaks.

A Sage X3 product reference sits on a data type that's 20 characters as standard, and Business Central's item `No.` is `Code[20]`. So for once the SKUs mostly fit, and your product URLs mostly survive.

Two caveats. Sage X3 field lengths come from data types rather than literals, and the code is written to read the length at runtime, which means a long-standing Sage X3 site may have had that data type widened without anyone writing it down. You can't read the length off the product, you have to read it off your own dictionary. And Business Central's `Code` data type converts to uppercase and strips leading and trailing spaces, so mixed-case references change identity on arrival.

What has no Business Central equivalent?

Three things: the product-site record, Sage X3's approach to variants, and the single folder holding several legislations.

The product-site record. In Sage X3, a product exists globally and then exists again per site, carrying suppliers, packaging, replenishment rules and authorisation, which is why Sage X3 can tell you that a product doesn't exist for a particular site. Business Central has no product-site object. Stockkeeping units and item-location fields are the nearest things and they aren't the same. So a storefront that asks whether this product is sellable from this site, in this pack, from this supplier, is asking a question that Business Central answers in three reads rather than one.

Variants. Sage X3 doesn't have Business Central-style variants, it has more product references, and if you use the product configurator it generates them for you from a naming format you defined, so a configured product with three characteristics arrives as its own 20-character reference. Business Central models the same catalogue as one item plus Item Variant records with a `Code[10]` code, and the migration has to decide which of your references were ever really separate products. If Shopify is the destination, note this now rather than later: Microsoft documents plainly that where a Shopify product uses a variant matrix combining two or more options, the connector can't create a variant for it, because Business Central has no option matrix and the connector uses the variant code as the only option.

The folder. Sage X3 holds multiple companies, legal entities and business units in a single instance, with intercompany transactions and, in Sage's own words, multi-legislation compliance in 30 or more countries. Business Central holds up to 300 companies in an environment, which sounds ample until you notice that an environment carries one country localisation, and the standard Essentials or Premium subscription includes one production environment and three sandboxes. A group that runs three legislations in one Sage X3 folder doesn't become one Business Central environment, it becomes three, and the storefront that used to read one system now reads three.

How do Sage X3 price lists map to Business Central pricing?

Most of it maps, but grouped price lists have no Business Central object at all, and Business Central's rule is a single comparison where Sage X3's is a configurable search.

A Sage X3 price list isn't a rate table, it's a structure you configure: a calculation base, a price type, and criteria you choose, returning results that include the price, discounts and charges together. There are normal price lists that resolve on the line, and grouped price lists that act across several document lines and produce header-level results such as freight. Price lists can be approved through workflow, can differ between group entities, and can be mass-updated by tag.

And there's a dedicated price search function that performs a real-time simulation against live data, resolving by date, currency, site, quantity and the product and customer pair. Sage X3 ships a simulator because the answer isn't obvious. That function also can't simulate grouped price lists, which tells you something else.

Business Central's rule is one sentence. The best price is the lowest price with the highest line discount allowed on a given date, evaluated against customer or customer price group, item or item discount group, minimum quantity, unit of measure, currency and dates.

Most Sage X3 estates can be expressed in that. Some can't, and the grouped price list is the clearest example, because a result that only exists once the whole basket is known has no Business Central object and no catalogue-publishing connector can represent it.

If Shopify is on your shortlist, there's a hard limit to know about before you get attached to the idea. Microsoft documents that when the connector exports a price to Shopify it creates a temporary sales quote for a quantity of one and uses standard price calculation, so only prices and discounts applicable at quantity one are used, and you can't export different prices or discounts based on quantity. For a B2B business with volume breaks, that sentence decides the architecture on its own.

Which leaves the question worth answering before anything else. If your web shop calculates its own prices today, you don't have one pricing engine. You have two, and they disagree at the worst possible moment, which is the moment a customer compares the basket to the invoice. And if your shop asks Sage X3 for the price of every line, then whatever replaces it has to be able to ask the same question of Business Central, per basket, live.

Why does stock availability behave differently in Business Central?

Because stock in Sage X3 carries a condition as well as a location, and Business Central has no field for the condition of a quantity.

A Sage X3 quantity is approved, in quality control, or rejected, with further markers for partial processing and incomplete sampling, and organisations can add their own two-character sub-statuses. Which statuses are legal is controlled at supplier, product-site and product category level, which is why a Sage X3 user can be told that a stock status is unauthorised. Allocation comes in two shapes as well, global against a product-site and detailed against a stock line.

Business Central can express where stock is with real precision: locations, zones, bins, bin types including a QC type, class codes, ranking and capacity, across six licence-controlled complexity levels up to full warehouse management. It can block a lot or a serial number. What it can't do is carry the condition of a quantity as a queryable attribute with your own sub-statuses.

A Sage X3 shop that shows approved stock at one site is asking two questions Business Central answers in neither one field nor one call. And availability with a date attached comes from order promising, which is an action a person runs on selected sales lines and accepts rather than an endpoint a storefront can call. What the Shopify Connector actually publishes is one of two calculations, projected available balance at today or free inventory not reserved.

Is Business Central's product content weaker than Sage X3's?

No. Product content is the one place where this migration is a genuine step up, which is the opposite of what happens moving off older Dynamics systems.

Sage X3's product record is operationally and regulatorily rich, with categories carrying allocation and issue rules, notes, a translation mechanism, and in process industries safety data sheets and substance master data. What it isn't especially good at is web merchandising.

Business Central has item attributes, typed as option or free text, assignable to items and to item categories with inheritance to child categories, filterable, and variants that can carry their own pictures and attribute values. Microsoft's own documentation names integrated web shops as the reason item attributes exist.

So don't budget for a content downgrade. Budget for moving the regulatory content somewhere it still gets maintained.

What happens to order history and customer logins on go-live day?

Web logins survive if the storefront survives, because they live in the shop platform rather than in Sage X3. Live reads are what break.

If your shop shows credit limits, statements, open orders and invoices by reading Sage X3 in real time, every one of those reads has to exist against Business Central before cutover, or the account page goes blank on the first morning. If the shop stores its own copy of order history, it survives and immediately starts disagreeing with the new ERP until the two are reconciled.

There's a practical guard worth setting on day one if Shopify is involved. Microsoft warns that the connector can create or modify items and customers and can create sales documents that are difficult to undo, and recommends leaving Auto Create Unknown Items, Auto Create Unknown Customers and Auto Create Sales Documents switched off.

When does the Microsoft Shopify Connector fit?

When you sell to consumers, or to business customers whose pricing works at a single quantity tier.

Architecture. The Shopify Connector is built by Microsoft, ships preinstalled with Business Central online, and runs on the job queue. There's no middleware to licence, no server, and nobody in the middle. It isn't available for on-premises deployments.

Data flow. Item sync is bidirectional and covers variants, images, barcodes, vendor item numbers, tags and metafields, and it exports item attributes, extended and marketing texts and translations. Inventory syncs across the locations you select, using projected available balance or free inventory. Customers and companies sync both ways, with mapping on email, phone or registration number.

Orders. Order import covers the Shopify online store, Shopify POS and Shopify B2B, and brings shipping costs, gift cards, tips, refunds, cancellations and payouts from Shopify Payments. Fulfilment tracking goes back to Shopify, and posted sales invoices are exported.

Tax. If you sell into the US, Shopify calculates sales tax at checkout and an engine such as Avalara sits behind Business Central for posting and filing.

Limits, and for a Sage X3 reader these are deciding factors rather than footnotes. Prices export at quantity one only, so volume breaks don't travel. A Shopify variant matrix combining two or more options can't be created by the connector, because Business Central has no option matrix. Extension points are deliberately few, so Microsoft can follow Shopify's release pace without breaking changes. It's one shop per configuration, so other marketplaces need something else. B2B works through Shopify companies and catalogues, and company sync reached the Basic, Grow and Advanced plans on 8 July 2026 with up to three active market catalogue assignments on those plans and unlimited on Plus, but complex contract pricing still strains it. And you have to stay current on Business Central versions.

When does Abakion B2B Ecommerce fit?

When your prices are customer-specific, your customers reorder, and the shop needs to ask the ERP rather than read a published catalogue.

Architecture. Abakion B2B Ecommerce installs as an app in Business Central, the site runs on Azure, and the storefront reads live data from Business Central. There's no synchronisation job, no staging database, no integration to own, and nothing to regression test twice a year.

Data flow. Customer-specific catalogues, prices, agreements and currencies come straight from the ERP, and delivery dates come from Business Central's own availability calculation. Order history and reorder work from actual posted documents.

Product content. The accompanying Master Data Information app handles product content and variant matrices, which matters more here than it does elsewhere, because collapsing Sage X3 product references into items and variants is exactly the exercise this migration forces.

Tax. Avalara is supported for US sales tax.

Commercial shape. Fixed price on the initial project, then a subscription tiered by the number of active customers and the number of items in the shop.

The argument that lands hardest for a Sage X3 customer. A storefront reading Business Central directly can ask for a customer's own price on a basket, live, rather than looking it up in a catalogue published at quantity one. There's nothing to push out to the shop, because there's no out.

In what order should you sequence the two projects?

The ERP first, and the storefront once, afterwards. You have more time than most readers of this series, and the way to waste it is to spend the extra year improving something you're leaving.

The most expensive mistake available to you is investing in the Sage X3 integration in the year before you leave Sage X3. Publishing another SOAP object, extending an import template, adding another batch task: all of it is written off on go-live day. Design any change to the current setup as thin and disposable, and let the storefront land once, after the ERP move, on the model you intend to keep. Two web projects in two years is the outcome nobody plans for and plenty of companies get.

Because nothing is switching off, use the extra time to answer the scope question properly instead, since the ERP decision is reversible on paper and expensive in practice.

When is neither Shopify nor Abakion B2B Ecommerce enough?

There are two lists for a Sage X3 reader, and the second one isn't about the web shop at all.

Neither ecommerce route fits if you:

• sell configurable products
• run punchout or EDI into your customers' procurement systems
• sell across several marketplaces
• operate a subscription model
• run a design-led consumer brand where the storefront is the marketing
• need volume break pricing published to a Shopify catalogue
• need a two-option variant matrix on Shopify

And Business Central itself is a different size of system if your business depends on:

• multiple legislations in one instance with intercompany posting
• process manufacturing with formulas, recipe versioning and batch traceability
• quality control with your own stock statuses and authorisation rules
• a product configurator generating new product references
• warehouse capability delivered by a Sage-only ISV
• Oracle as the database platform

Microsoft describes Business Central as a business management solution for small and mid-sized organisations, and that positioning is doing real work. Some Sage X3 customers reading this should not move, and their web shop is not the reason.

But plenty of others assume they're in that group without testing it, keep paying for capability they stopped using three restructures ago, and never find out that the storefront was the easy part.

Where to start

Five questions, and the people who can answer them already work for you.

1. How many legislations sit in your Sage X3 folder, and does anything post between companies? That answers the environment question, and the environment question answers most of the others.
2. Does your web shop ask Sage X3 for the price of every line, or does it hold a published catalogue? And do your customers get volume breaks?
3. Do you use grouped price lists, and does the storefront show a result that depends on the whole basket?
4. Does the shop read stock status, or product-site availability, or a promise date?
5. Has anyone widened the product reference data type in your dictionary?

The answers usually point clearly at Abakion B2B Ecommerce, at Shopify, or at a rebuilt API integration, and knowing which one you're facing is worth more than assuming Sage X3 forces your hand.

Frequently asked questions

Both apps are on Microsoft Marketplace

• Shopify Connector, published by Microsoft
• Abakion B2B Ecommerce
• Abakion B2B Ecommerce product page

Sources

• Sage annual report 2025, Sage
• Sage half year 2026 results, Sage
• Sage X3 Version 12 latest release information, Sage Community Hub
• Sage X3 lifecycle policy, Sage
• Sage X3 prerequisites overview, Sage online help
• Sage X3 security best practices, Sage online help
• Sage X3 Node.js sizing, Sage online help
• Sage X3 financial capabilities, Sage
• Sage X3 supply chain capabilities, Sage
• Sage X3 production management capabilities, Sage
• Sage sample X3 web services PHP portal, Sage on GitHub
• Migrate on-premises data to Business Central online, Microsoft Learn
• Migrate to the cloud from any SQL database, 2026 release wave 1, Microsoft Learn
• Operational limits for Business Central online, Microsoft Learn
• Manage environments, Business Central admin centre, Microsoft Learn
• Business Central overview, Microsoft Learn
• Item table reference, Business Central, Microsoft Learn
• Record sales price, discount and payment agreements, Microsoft Learn
• Design details, warehouse setup, Microsoft Learn
• Work with item tracking, Microsoft Learn
• Work with item attributes, Microsoft Learn
• Calculate order promising dates, Microsoft Learn
• Synchronise items with Shopify, Microsoft Learn
• Get started with the Shopify Connector, Microsoft Learn
• Sell to business customers on more Shopify plans with B2B company sync, 2026 release wave 1, Microsoft Learn
• Installing and uninstalling extensions in Business Central, Microsoft Learn
• Experlogix Digital Commerce for Sage X3, Experlogix
• Datalinx Warehouse Manager for Sage X3, Datalinx
• Adobe Commerce release versions and lifecycle, Adobe Experience League