Shopify Business Central Integration After NAV Migration: A Complete Guide 

Short Answer 

No, your Shopify integration does not carry over when you migrate from Dynamics NAV to Business Central. Business Central uses REST APIs, OAuth through Microsoft Entra ID and an extension model, so NAV-era connectors must be rebuilt and re-tested. Plan the rebuild as part of the migration project, not after go-live.

Moving from Microsoft Dynamics NAV to Dynamics 365 Business Central does not move your Shopify integration with it. Because Business Central is NAV’s direct successor, your core processes (posting, inventory, sales orders, customer and item records) will feel familiar. But familiar is not the same as unchanged. NAV customizations written in C/AL have to be rebuilt as AL extensions, some features work differently (customer pricing, for example, now runs through price lists), and the technical connection to Shopify starts over: APIs, authentication, customizations and record mappings all need to be rebuilt and re-tested. 

That is why the Shopify integration belongs in the migration project from day one: in the scope, the budget, the timeline and the test plan. If you treat it as a clean-up task after go-live, the gap shows up where it costs the most: missed orders, inventory that doesn’t match what Shopify is selling, and B2B customers seeing the wrong prices. The merchants who get this right plan the integration rebuild alongside the data migration, test it against real order scenarios before cutover, and go live with both systems connected on the same day. 

This guide explains what changes, what breaks, which integration path fits, and gives you a 10-step plan to rebuild the connection without losing orders, inventory accuracy or customer-specific pricing. 

The migration puts your store at risk because your existing connector was built for NAV’s web services, NAV’s authentication model and your NAV customizations. Pointed at Business Central, it either fails loudly on day one, drops orders or misreports stock quietly, or appears to work until a customized field, price list or warehouse rule is used. 

For years, orders flowed from Shopify into NAV and inventory flowed back. Then the migration starts, and the ERP team focuses on financials, posting setups and data cleansing. The Shopify integration ends up as one line in the plan: “reconnect Shopify.” That line hides most of the risk. 

Timing adds urgency. Extended support for NAV 2016 ended on April 14, 2026. NAV 2017 follows on January 11, 2027, and NAV 2018, the final release, on January 11, 2028. If your migration date is set, your Shopify rebuild date should be set with it. 

i95Dev builds and maintains ERP-to-eCommerce integrations for merchants running Shopify, BigCommerce and Adobe Commerce on Microsoft Dynamics ERPs including Shopify with Dynamics NAV, Dynamics GP, Dynamics F&O and Business Central. We have been in business for 25+ years and have delivered 1,200+ projects, so we see what surfaces after cutover, not just what the plan predicted.  

A Shopify Business Central integration automatically exchanges products, inventory, prices, customers and orders between your store and Business Central, so staff stop re-keying data and shoppers see accurate stock and pricing. 

After a NAV migration, the job is different. You are replacing a working, customized NAV integration with one that must reproduce its behavior on another platform while the business keeps taking orders. That means: 

• Inheriting customizations that live in NAV code and may be undocumented. 
• Mapping old item, customer and location identifiers to the migrated Business Central data. 
• Cutting over without a gap in order flow. 

For a broader comparison of options, see our guide on how to choose the right Shopify and Business Central integration. 

Rebuilding alongside the migration, rather than after it, turns a risky cutover into a planned one. 

• No gap in order flow. A tested integration is ready on cutover day, so nobody re-keys orders or adjusts stock by hand. 
• Data is mapped once. Item numbers, customer numbers, locations and price lists are already being finalized for Business Central, so mapping them to Shopify now avoids a second round of corrections. 
• Old flows get questioned. Years of customization leave flows nobody uses. A migration forces the question of what to keep, giving you a leaner integration. 
• Authentication is modernized. OAuth through Microsoft Entra ID replaces long-lived access keys with short-lived tokens and a defined credential owner. 
• Testing is shared. Your sandbox, test data and migration team already exist, so Shopify scenarios can be tested alongside finance and operations. 
• Standard features may cover more. Microsoft’s Shopify Connector now includes B2B company sync and market catalogs, so some logic that needed custom NAV code may now be standard. Our Shopify ERP integration services can help you judge what still needs custom work. 

Business Central keeps NAV’s business concepts, but the integration surface is different. 

Area	Typical Shopify – NAV setup	Business Central
Interface	SOAP codeunits and OData pages	REST API v2.0 (OData v4) plus custom API pages. SOAP and OData still exist, but REST is Microsoft’s standard route
Authentication	User name and password, or web service access key	OAuth 2.0 through Microsoft Entra ID. Access keys (basic auth) have been unsupported in Business Central online since October 2022
Customizations	Changes to base objects and custom codeunits	Extensions layered on the standard application, so custom logic must be re-implemented or replaced
Updates	Version upgrades on your schedule	Major updates twice a year (release waves) in Business Central online
Shopify connectivity	Custom or third-party connectors	Microsoft’s Shopify Connector is included

An integration that depends on NAV-specific objects, access keys or customized fields needs a rebuild, not a reconfiguration. Microsoft documents the interfaces and the access-key deprecation in its Business Central web services reference. 

These failure points are the most common. Each can be avoided if you plan before cutover. 

• Authentication stops working. Connectors that signed in with an access key cannot do so against Business Central online. They need OAuth, and someone must own app registration and secret rotation. 
• Custom fields go missing. Fields NAV developers added may not exist in Business Central or may exist as extension fields with different names. The sync handles standard data and mishandles anything customized. 
• Identifiers no longer line up. If item, customer or location codes were cleaned or renumbered, Shopify references can point at the wrong record or at nothing. 
• Pricing logic changes. NAV price groups, discounts and customer price tables must be re-created in Business Central’s price structures before they sync correctly. 
• Tax, payment and inventory setups differ. Posting groups, tax configuration, payment terms and warehouse structures are often redesigned. If Shopify’s mapping is not updated, invoices drift and stock can oversell. 
• No one owns the next release. Business Central online updates arrive twice a year, and an unmaintained connector can lose functionality without warning. Our deep dive on why integrations fail in the real world covers this pattern. 

A migration is the best moment to question what the old integration synced, because you are about to pay to rebuild all of it. 

• Always sync: product catalog, inventory, orders and order status, and customer records. 
• Depends on your setup: returns, promotions, multi-warehouse allocation, and B2B data such as credit terms and negotiated pricing. 
• Keep out: general ledger entries, internal cost fields and supplier pricing. 

Decide data ownership at the same time. Usually, Business Central is the master for product and pricing data, Shopify is the origin for orders with Business Central as the system of record for fulfillment and accounting, and customer ownership depends on D2C versus B2B. Two flows need extra attention: customer-specific pricing from your ERP and multi-location inventory sync, because both depend on setups that are often redesigned. For ownership rules in depth, see multi-store integration architecture. 

	Native Shopify Connector	App Store connector	Managed integration
Cost	Included with Business Central	Low, usually monthly	Medium to high
Who maintains it	You	You, when it breaks	The vendor
Built for Business Central	Yes	Often generic “Dynamics 365”	Yes, including extensions
Handles NAV customizations	Only through your own extension work	Rarely	Yes, scoped in discovery
Best fit	Single store, standard catalog and pricing	Simple, low-volume stores	B2B-heavy, multi-warehouse, multi-store or heavily customized setups

The native connector has grown. Microsoft’s release notes describe B2B company sync and market catalogs on all Shopify plans, while direct company catalogs, which give a company its own pricing, require Shopify Advanced or Plus. That is a real improvement, but it assumes your pricing, locations and customizations fit the connector’s model. Heavily customized NAV merchants often find they are the exception. 

See our comparison of the native connector versus a managed integration, or our Microsoft Shopify Connector support services if you already run it. Wholesale merchants often add an ERP-connected B2B portal for Shopify for self-service ordering backed by ERP data. 

• Before (build in parallel). Build and test in a sandbox while NAV and the old connector keep running. This is safest for stores with meaningful volume, because cutover becomes a switch, not a project. 
• During. This compresses testing into hours and only suits very small catalogs with simple logic. 
• After. Manual order entry and spreadsheet reconciliation while you rebuild is the highest-risk path, and its cost climbs with SKUs, warehouses and B2B accounts. 

Our recommendation: build in parallel, rehearse the cutover, and go live with the integration on the same day as the ERP. 

Step 1: Confirm Your Migration Path and Dates 

Find out whether you are upgrading in place, moving to a new tenant or migrating to the cloud, and which NAV version you run. Lock the cutover date so every later step can work backwards from it. If you are also replatforming your storefront, see our eCommerce platform migration services. 

Step 2: Inventory Every Shopify-to-NAV Touchpoint 

List each data flow: what moves, which direction, how often and who owns it. Include forgotten ones such as nightly price updates or tracking write-backs. Our integration requirements template gives you a structure. 

Step 3: Audit NAV Customizations 

Identify the custom fields, modified objects and codeunits feeding the integration. Decide for each whether it is still needed, whether standard Business Central now covers it, or whether it must become an extension. 

Step 4: Decide Data Ownership 

Write down the system of record for products, prices, inventory, customers, orders and fulfillment. Ownership conflicts are the most common cause of overwritten data after go-live. 

Step 5: Choose Your Integration Path 

Use the comparison above plus Steps 2 and 3. Standard flows and simple pricing may suit the native connector. Customizations, multi-warehouse routing or account-specific pricing point to a managed integration, and our integration experts service can supply specialists. 

Step 6: Set Up Access and Authentication 

Plan for OAuth 2.0 through Microsoft Entra ID, not carried-over access keys. Create a dedicated integration user with minimum permissions and assign someone to renew credentials so the sync does not fail silently. 

Step 7: Clean and Map Your Data 

Map migrated item and customer numbers, price lists, locations, tax settings and payment terms to their Shopify counterparts. Resolve duplicates and renumbered records before the first sync. 

Step 8: Test in a Sandbox With Real Scenarios 

Test beyond the happy path: a partial shipment, a refund, a B2B order with negotiated pricing, a multi-warehouse allocation and an order that fails validation. Run the new integration alongside NAV long enough to compare results. 

Step 9: Plan and Rehearse the Cutover 

Decide when order sync pauses, how in-flight orders are handled, how you run a delta sync after the freeze and what triggers a rollback. Rehearse at least once. 

Step 10: Monitor and Test Every Release Wave 

Watch the error queue daily for the first weeks, reconcile orders, inventory and payments against Shopify, and schedule a regression test for each Business Central release wave. 

• Give the integration an owner, a timeline and a test plan, not a line under “other systems.” 
• Involve eCommerce, finance and operations early. Each team sees different failure points, from tax errors to oversold stock. 
• Document as you go. Field mappings, ownership decisions and exception rules will be needed again at the next release wave. 
• Prioritize visibility. Real-time error alerting means you hear about a failed sync from your system, not from a customer. 
• Quantify the cost of waiting. Run your numbers through our integration ROI calculator. 
• Review after 90 days. Remove flows nobody uses and tighten the ones that cause exceptions. 

• Is the connector built specifically for Business Central, or adapted from another Dynamics product? 
• Have they migrated Shopify integrations from NAV before, and can they show references? 
• Who owns maintenance when the next release wave ships? 
• What does error visibility look like: real-time alerts with retry, or customer complaints? 
• How will they handle your actual customizations, not just standard sync? 

Our eCommerce vendor evaluation checklist offers a fuller scorecard. 

i95Dev’s managed Shopify and Business Central integration is built for the work this guide describes. It typically includes: 

• Bidirectional sync of products, inventory, prices, customers and orders. 
• Field mapping built for Business Central’s extension model, including migrated customizations. 
• An error queue with retry and alerting. 
• Ownership of release-wave maintenance. 
• Support for multi-warehouse routing, B2B account pricing and multi-store setups. 

Our ERP modernization approach covers upgrading ERP and commerce layers together, and you can see the platform on the i95Dev Connect page.  

Migrating from NAV to Business Central is an opportunity to modernize your eCommerce operations, but your Shopify integration needs careful planning. Reviewing existing customizations, updating data mappings and testing the new connection before cutover can help prevent disruptions. 

The right integration approach ensures reliable order processing, accurate inventory and consistent pricing while supporting your future business needs. Plan your Shopify integration alongside the ERP migration, not after go-live.