Shopify + Microsoft Dynamics AX in 2026: Why Integration Shouldn’t Wait for Migration 

Microsoft pulled the plug on extended support for Dynamics AX back in January 2023. No more patches, no more updates, nothing. But that’s not the same as AX being unusable. A lot of businesses still run it every single day without issue. What’s changed is what it means to connect that system to a modern storefront. Shopify can integrate with Dynamics AX right now through existing middleware, so you don’t have to choose between “rip out the ERP” and “put the Shopify plans on hold.” You can build the modern storefront today and figure out the Dynamics 365 move whenever it actually makes sense for your business. 

If you’re running AX and selling on Shopify, or thinking about it, here’s the thing worth actually sitting with: Microsoft isn’t patching this software anymore. Full stop. That doesn’t mean AX has broken down or stopped doing its job. It hasn’t. But it does mean the calculus around connecting it to a modern storefront looks different than it did a few years ago. 

Microsoft’s extended support for Dynamics AX 2012 R3, the final version of the platform, ended on January 10, 2023. Every earlier version lost support before that. In practical terms: no more non-security hotfixes, no regulatory updates, no official technical support for any Dynamics AX release. 

Despite that, legacy systems remain common. A 2025 Saritasa survey of 500 U.S. IT professionals found that 62% of organizations still rely on legacy software systems. If your business is one of them, you’re not an outlier. But the risk calculus around how you modernize around that system has changed. 

Dynamics AX is an enterprise resource planning system that handles finance, inventory, order processing, procurement, and operations for mid-market and large businesses. It was Microsoft’s flagship on-premises ERP for years, and a lot of companies built their entire operation around it: pricing logic tuned to their contracts, warehouse workflows that match how their floor actually runs, approval chains, reports nobody remembers building but everybody depends on. 

None of that transfers cleanly to a new system. Rebuilding it is months, sometimes years, of work, and “it still works, why touch it” holds up fine until the day it doesn’t. 

Dynamics 365 Finance & Operations (D365 F&O) is what Microsoft built to replace AX. Same core finance and supply chain functions underneath, but cloud-based, with continuous updates, built-in AI features, and real-time analytics. Every dollar Microsoft puts into feature development, security, and platform work goes to D365 F&O now. AX gets none of it. 

AX didn’t stop working the day Microsoft stopped supporting it. It’s still running fine for a lot of shops, same as it always has. Microsoft just stopped paying attention to it. The gap between AX and wherever Microsoft’s actually investing widens every year, and eventually that catches up with you, usually at the worst possible time. If you’re ready to actually map out what comes next, our covers timeline, scoping, and where these projects tend to fall apart. 

Shopify is good at the storefront. It was never meant to be your system of record for finance, multi-warehouse inventory, or B2B pricing that has ten different rules depending on the customer. Without a connection back to your ERP, that gap gets filled by a person: someone re-keying orders by hand, reconciling stock counts between two screens, answering “is this actually in stock” by physically checking. 

That doesn’t scale. More orders just means more manual work, more chances for a mistake to slip through. An integration layer between Shopify and Dynamics AX keeps product, inventory, customer, and order data moving automatically, so what your storefront shows actually matches what’s happening in the warehouse. 

In practice, that means syncing things like SKUs and product data, on-hand inventory across warehouses, customer records, and sales orders as they come in, typically pulled through AX’s Application Integration Framework (AIF) or its OData-based services, depending on your AX version and how it’s configured. 

“AX is unsupported, so let’s pause everything until the D365 migration is done” sounds cautious. Usually it’s the more expensive option. ERP migrations run long, often close to a year once you count planning, testing, and change management. Every month you wait is another month of someone manually re-entering orders, inventory counts that don’t match reality, and a storefront that has no idea what’s actually happening in the warehouse. 

Integrating Shopify with your current AX environment now doesn’t lock you out of a future migration. A properly built integration layer is designed to be adapted when the underlying ERP changes, not rebuilt from zero, so the investment you make today keeps paying off after you eventually move to D365 F&O. 

Not all Shopify-to-ERP connections are built the same way. Understanding the three common approaches helps you evaluate any vendor’s proposal, including i95Dev’s. 

Approach	How it works	Best fit
Point-to-point	Custom code connects Shopify and AX directly, one integration built for one specific data flow	Very simple, single-purpose needs, but brittle and expensive to extend as requirements grow
iPaaS / managed middleware	A dedicated integration layer sits between Shopify and AX, handling data mapping, error handling, and monitoring centrally	Most growing businesses, especially those expecting to add channels, warehouses, or eventually migrate ERPs
Custom middleware	A purpose-built integration layer designed around your specific AX customizations and business logic	Businesses with heavily customized AX environments that generic connectors can’t map cleanly

• Waiting for a “perfect” migration timeline before integrating anything, while manual costs keep accumulating 
• Choosing a generic, off-the-shelf connector that can’t accommodate years of AX customization, then discovering the gap mid-implementation 
• Treating integration as a one-time project instead of an ongoing operational system that needs monitoring and support 
• Underestimating how much institutional knowledge is embedded in custom AX workflows, and losing it in a rushed migration 

There’s no universal answer, but a few questions help clarify the right sequence for your business: 

• How urgent is your Shopify go-live or replatforming timeline compared to your ERP migration timeline? 
• How customized is your current AX environment, and how well-documented is that customization? 
• What’s the realistic cost of continuing manual processes for the duration of a full ERP migration? 
• Does your team have the bandwidth to manage a storefront launch and an ERP migration at the same time? 

For most businesses still evaluating a Dynamics 365 timeline, integrating Shopify with AX now and migrating the ERP on a separate, deliberate schedule is the lower-risk path. It delivers operational value immediately without tying your commerce roadmap to your ERP roadmap. 

i95Dev has been connecting Shopify to Dynamics AX for years, including AX environments customized well past what generic connectors can handle. If you want the specifics, what data syncs, how a project gets scoped, how the work you do now holds up once you eventually move to D365, that’s covered on our dedicated Shopify + Dynamics AX integration page. 

See how i95Dev connects Shopify to Dynamics AX  

Dynamics AX being unsupported doesn’t mean your commerce strategy has to wait for your ERP strategy. The businesses getting this right are integrating Shopify with the AX environment they already have, capturing the operational and customer-experience benefits now, and migrating to Dynamics 365 on a timeline that fits their business, not the other way around. 

Ready to see what that looks like for your business? Explore Shopify + Dynamics AX integration with i95Dev