NetSuite SuiteCommerce → to Shopify

NetSuite SuiteCommerce to Shopify: keep the ERP, replace the storefront

Almost nobody migrating off SuiteCommerce is leaving NetSuite. They are keeping NetSuite as the system of record for items, customers, orders and finance, and replacing the SuiteCommerce Advanced or SuiteCommerce Standard storefront with Shopify Plus. That makes this less a data migration than an integration project with a storefront build attached, and the sequencing matters more than the volume. This guide is how we run it.

Why brands leave SuiteCommerce

• Cost of change. SuiteCommerce Advanced customizations need NetSuite developers, releases are slow, and every storefront change touches the ERP.
• Conversion. SuiteCommerce checkout, site speed and mobile experience lag Shopify Plus by a wide margin, and there is no app ecosystem to close the gap.
• Marketing agility. Merchandising, landing pages, promotions and A/B tests that take a sprint on SuiteCommerce take an afternoon on Shopify.
• Oracle’s direction. SuiteCommerce is not where NetSuite invests. The ERP is.

The architecture after the move

Function	System of record	How it connects
Items, pricing, inventory by location	NetSuite	Synced to Shopify products, variants and locations. NetSuite remains the master; Shopify never edits items.
Storefront, cart, checkout, customer accounts	Shopify Plus	Shopify owns the experience. Markets for regions, B2B for wholesale.
Orders	Created on Shopify, posted to NetSuite	Sales orders in NetSuite within minutes, with customer, items, discounts, tax and shipping.
Fulfillment and tracking	NetSuite or WMS	Item fulfillments in NetSuite update Shopify orders with tracking.
Customers	NetSuite for finance, Shopify for the account experience	Two-way sync keyed on email and NetSuite internal ID.
Payments, refunds, cash application	Shopify Payments, posted to NetSuite	Payouts and refunds reconciled through the connector.

The connector is the heart of the project. The mainstream options are Shopify’s NetSuite connector, Celigo, and Boomi or Workato for teams that already run one. We recommend based on your NetSuite customizations, your order volume and what else needs integrating, and we set it up on a sandbox account before anything touches production.

What migrates, and from where

Data	Source	Approach
Items, matrix items, pricing levels, images	NetSuite saved searches and file cabinet	Initial load through the connector or a scripted import from a saved search export. Matrix items become variants; pricing levels become B2B catalogs.
Web-only content: descriptions, specs, SEO fields	SuiteCommerce item fields	Exported and imported to product descriptions and metafields.
Customers with addresses, terms, price levels	NetSuite customer records	Loaded to Shopify with the NetSuite internal ID stored as a metafield for the sync. B2B customers become companies with locations and payment terms.
Order history for the storefront account view	NetSuite sales orders	Optional. Recent history imported so customers see past orders on Shopify; the full ledger stays in NetSuite.
Passwords	Not exportable	Reset on first login or passwordless accounts.
Content pages, blog, landing pages	Site Management Tools	Rebuilt in the Shopify theme and metaobjects.
SEO URLs	SuiteCommerce URL components	Redirect map from the live URL inventory, including item and category URL components and any legacy /s.nl paths still indexed.

How we run it

1. Discovery. NetSuite customizations, item structure, pricing levels, locations, subsidiaries, existing integrations, order volume and the storefront URL inventory. Fixed-price scope for the storefront; the connector is scoped with the integration partner.
2. Sandbox first. Connector configured against a NetSuite sandbox and a Shopify development store. Item, customer and order flows tested end to end before production is touched.
3. Storefront build on Shopify Plus: theme, checkout extensibility, Markets, B2B, payments, shipping, tax with Avalara or Vertex if you use them in NetSuite.
4. Initial data load of items, customers and recent order history, reconciled against NetSuite counts.
5. Parallel run. Test orders flow to NetSuite, fulfill, and update Shopify. Finance signs off on the postings.
6. Redirects tested individually.
7. Cutover with the connector switched to production and DNS moved. SuiteCommerce stays available for a week for reference.
8. Hypercare for 30 days with the integration partner.

Timeline and cost

SuiteCommerce to Shopify Plus projects typically run 14 to 24 weeks, with the connector setup and finance sign-off being the long pole rather than the storefront. Storefront and migration work is quoted as a fixed price after discovery and usually falls between $40,000 and $120,000 depending on Markets, B2B and content scope; connector licensing and configuration are additional and depend on the platform chosen. Payment is 50 percent to begin and 50 percent once the store is live and you are fully satisfied with the figures.

NetSuite item types and how they land on Shopify

NetSuite item	Shopify object	Notes
Inventory item	Product with one variant	The standard case. Item name, display name and sales description map to title and body; the NetSuite internal ID is stored on the product for the sync.
Matrix item (parent with child items)	Product with options and variants	Matrix options become Shopify options. More than three options, or more than 100 children, needs a restructure agreed in discovery.
Kit or package item	Bundle	Shopify Bundles or a bundle app, with the components decremented in NetSuite by the connector.
Assembly item	Product	Sold as a single product; the assembly logic stays in NetSuite.
Non-inventory and service items	Product with inventory tracking off, or a line item added by the connector	Shipping, handling and fee items are usually handled on the NetSuite side rather than as Shopify products.
Price levels and customer-specific pricing	Market prices and B2B price lists	Base price to the default market; alternate price levels to catalogs on Plus.
Inventory by location and subsidiary	Shopify locations, one per fulfillment location, with Markets per subsidiary where needed	Available-to-promise rather than on-hand is what the connector should send.

The order lifecycle after the move

The question finance asks first is what happens to an order once it is placed, so here is the sequence we set up and test in the sandbox.

1. A customer checks out on Shopify. Payment is authorized or captured by Shopify Payments or your gateway.
2. The connector creates a NetSuite sales order within minutes, with the customer matched on the internal ID or created if new, items by SKU, discounts as discount items or line-level rates, shipping as a shipping item, and tax as calculated by Shopify Tax or by Avalara or Vertex if those are your tax engine in NetSuite.
3. NetSuite or the WMS fulfills the order. The item fulfillment posts back to Shopify as a fulfillment with the tracking number, which triggers the shipping email.
4. The invoice and cash sale post in NetSuite. Shopify Payments payouts are reconciled as deposits with fees, so the bank matches.
5. Refunds and returns raised on Shopify create credit memos or return authorizations in NetSuite; returns raised in NetSuite update the Shopify order.

Each of these flows has a failure mode, from a SKU that exists in one system only to a tax code mismatch, and the connector’s error queue is monitored during hypercare so nothing sits unposted.

Common mistakes in SuiteCommerce migrations

• Starting with the storefront design and leaving the integration to the end, which is where the schedule slips.
• Letting both systems edit product data. NetSuite is the master; Shopify is a display and sales surface.
• Sending on-hand rather than available inventory, which oversells the moment a pick is in progress.
• Skipping the customer key. Without the internal ID on the Shopify customer, the connector creates duplicates in NetSuite.
• Migrating every historical order into Shopify. Customers need recent history; finance needs NetSuite, which already has it.

Choosing the connector

Option	Fits when	Trade-offs
Shopify’s NetSuite connector	A standard NetSuite setup with modest customization and a single subsidiary or a simple multi-subsidiary structure	Fastest to configure and supported by Shopify. Less room for custom field mapping and unusual order flows.
Celigo	The most common choice for mid-market NetSuite customers; handles custom fields, multiple subsidiaries, kits, returns and payouts with prebuilt flows you can edit	Licensed separately, priced by flows and volume. Needs someone who owns it internally or through us.
Boomi, Workato or MuleSoft	Teams that already run one of these for other integrations and want Shopify on the same platform	Most flexible, most expensive, longest to build. Rarely the right answer for Shopify alone.
Custom integration on the Shopify Admin API and SuiteTalk	Very unusual requirements that no connector models	You own the code and its maintenance. We advise against it unless a connector has genuinely been ruled out.

Whichever you choose, the same sandbox-first sequence applies, and the sync direction for every entity is written down before configuration starts: items, prices and inventory flow from NetSuite to Shopify; orders and customers flow from Shopify to NetSuite; fulfillments and refunds flow both ways depending on where they are raised.

Customers, companies and the account experience

SuiteCommerce MyAccount gives customers order history, invoices, statements, saved addresses and, for B2B, purchase on account. Shopify’s customer accounts cover order history, addresses and returns, and Shopify B2B on Plus adds company accounts with multiple buyers, locations, net payment terms, invoice payment through checkout and company-specific catalogs. Two things do not exist natively and are handled deliberately: account statements, which are either generated in NetSuite and emailed, or surfaced through a B2B portal app; and quotes, which are created as draft orders and sent for approval. NetSuite customer records become Shopify customers or companies with the NetSuite internal ID and terms stored on the record, so when a buyer places an order the connector already knows which NetSuite customer and subsidiary it belongs to.

What you get at handover

The project closes with the integration design document covering every entity, its direction of sync and its field mapping; the sandbox test log showing each order, fulfillment, refund and payout scenario and its NetSuite posting; the reconciliation ledger for items, customers and imported order history; the redirect verification list; the hypercare log with every connector error and its resolution; and a recorded walkthrough of the Shopify admin for the ecommerce team and of the connector dashboard for whoever monitors it. Finance receives a one-page description of how Shopify orders, payouts and refunds appear in NetSuite, which is usually the document they ask for first.

Questions we settle in the survey

• NetSuite edition, subsidiaries, locations and whether SuiteTax or a third-party tax engine is in use.
• Item types in the catalog and how many matrix items exceed three attributes.
• Whether an iPaaS is already licensed, and who owns integrations internally.
• Order volume per day, which sets the connector’s sync cadence.
• How much order history customers need to see on the storefront.
• Which B2B features the current MyAccount provides that buyers depend on.

The answers shape the connector choice and the phase plan, and they are the difference between a fixed price and a range. If you are unsure of any of them, say so on the survey and we will work them out with your NetSuite administrator on the first call.

Frequently asked questions

Start with the migration survey and note which NetSuite modules and connectors you run. The Shopify Plus migration page covers the enterprise process, and our integration services cover ERP connections in more depth.