Migrating to Shopify? Keep NetSuite Intact

The scenario: new storefront, same ERP

You have a running ecommerce operation on Magento, WooCommerce, BigCommerce, or SuiteCommerce. Orders flow into NetSuite. Inventory syncs back. Fulfillment triggers shipping notifications. Financial data reconciles nightly. The whole pipeline works.

Now you want to move to Shopify.

The storefront changes. The ERP stays. That sounds straightforward until you realize that every integration touchpoint between your current platform and NetSuite needs to be rebuilt. Not migrated — rebuilt. The connector or middleware that maps orders from Magento into NetSuite sales orders has zero understanding of how Shopify structures its order payload. Different field names, different data formats, different webhook events, different API authentication.

This is the part that catches teams off guard. They budget six weeks for the Shopify build and forget that the integration layer is a separate project with its own timeline.

---

What breaks during a platform migration

When you swap out the ecommerce platform, you are ripping out one side of every integration flow. Here is what stops working:

Order sync. Your current integration maps order data from your existing platform's schema into NetSuite sales orders. Shopify structures orders differently — line items, discount applications, tax lines, shipping lines, and payment details all use a different data model. Every mapping needs to be rebuilt.

Inventory sync. If you are pushing available quantities from NetSuite to your storefront, the receiving end changes completely. Shopify uses inventory levels tied to locations and variants. If your current setup pushes a flat quantity per SKU, you need to account for Shopify's multi-location inventory model.

Customer sync. Customer records in Shopify carry different default fields than Magento or WooCommerce. Address formats, customer tags, metafields, and account activation flows all differ. If you were syncing customer groups or pricing tiers, that logic needs to be rethought for Shopify's customer segment model.

Custom field mappings. Any custom attributes you mapped between your current platform and NetSuite — custom item fields, order-level custom fields, customer-specific pricing — need new mappings. Shopify uses metafields for custom data, which is a fundamentally different structure than Magento custom attributes or WooCommerce meta.

Tax configuration. If your integration passes tax amounts from the storefront to NetSuite (instead of letting NetSuite calculate tax), you need to verify that Shopify's tax engine produces the same results. Discrepancies here cause reconciliation headaches that show up weeks after go-live.

Historical data references. Your NetSuite records reference order numbers, customer IDs, and transaction IDs from your current platform. After migration, new orders come in with Shopify order numbers. Reports that filter by channel, linked records that reference old platform IDs, and saved searches that rely on external document numbers all need attention.

---

Migration phases: the actual sequence

Phase 1: Audit the current integration

Before building anything new, document what you have. Map every data flow between your current platform and NetSuite. For each flow, capture:

• Direction (which system is source of truth)
• Frequency (real-time, scheduled, batch)
• Field mappings (source field → NetSuite field)
• Transformation logic (concatenations, lookups, conditional mappings)
• Error handling (what happens when a sync fails)

If you are running Celigo, export your flow configurations. If you are running custom SuiteScript or middleware, get the technical documentation — or reverse-engineer it from the code. You cannot rebuild what you do not understand.

Phase 2: Set up the Shopify store

This runs in parallel with the integration work. Theme development, product catalog setup, navigation, checkout configuration, payment gateways, shipping rules, and tax settings. If you are moving to Shopify Plus, this includes checkout extensibility, B2B features, and Shopify Functions configuration.

The Shopify build team and the integration team need to coordinate on data structure decisions early. How you set up product variants, metafields, and customer metafields in Shopify directly affects the integration mappings.

Phase 3: Rebuild the integration layer

This is the critical path. If you were using Celigo on your previous platform, you are not migrating your Celigo flows — you are building new ones. Celigo flows are platform-specific. A Magento-to-NetSuite order flow and a Shopify-to-NetSuite order flow share the destination but nothing else. The source connection, data extraction, field mappings, and error handling are all different.

If you were running a custom integration (SuiteScript, Node.js middleware, or a legacy connector), you are rebuilding from scratch against Shopify's Admin API and webhook system.

The core flows to rebuild:

Flow	Direction	Priority
Order creation	Shopify → NetSuite	Critical — day one
Inventory levels	NetSuite → Shopify	Critical — day one
Fulfillment/tracking	NetSuite → Shopify	Critical — day one
Product sync	NetSuite → Shopify	High — needed for ongoing catalog management
Customer sync	Bidirectional	High — needed for account-based pricing
Returns/refunds	Shopify → NetSuite	Medium — can be manual briefly
Gift cards/store credit	Shopify → NetSuite	Medium — depends on volume

Phase 4: Data migration

Decide what moves to Shopify and what stays behind.

Products. Variants, images, descriptions, SEO metadata, metafields. If you have hundreds of products with complex variant structures, budget time for data cleanup. Shopify has a 100-variant limit per product (3 option types with limited combinations). Products that exceeded this on your old platform need restructuring.

Customers. Customer accounts, addresses, order history. You can import customers into Shopify, but passwords do not transfer — every customer needs to reset their password or be invited to activate their account. Plan for this in your communications.

Historical orders. You probably do not need these in Shopify. They live in NetSuite. Importing historical orders into Shopify adds complexity with minimal value. Your customer service team can look up old orders in NetSuite. The exception is if you need order history visible in the customer's Shopify account portal — evaluate whether that is worth the effort.

URL redirects. Every URL on your current site that has external links, search engine rankings, or bookmarks needs a 301 redirect to the equivalent Shopify URL. Product pages, category pages, blog posts, CMS pages. Miss this and you lose organic traffic overnight.

Phase 5: Parallel run

Run both platforms simultaneously for one to two weeks. New orders flow through Shopify and into NetSuite via the new integration. The old platform stays up but no longer takes orders (or takes orders from a subset of traffic for comparison).

During the parallel run, verify:

• Orders land in NetSuite with correct amounts, tax, and customer data
• Inventory updates from NetSuite reflect accurately on Shopify
• Fulfillment triggers update Shopify tracking correctly
• Refund and cancellation flows work end to end
• Edge cases: orders with multiple shipping addresses, partial fulfillments, orders with custom line items, B2B orders with net terms

Phase 6: Cutover

DNS switch, final redirect verification, old platform shutdown. Have a rollback plan. Know exactly what "rolling back" means — it is not as simple as pointing DNS back, because orders placed on Shopify during the cutover window need to be accounted for.

---

Timeline reality

Here is what this actually takes, assuming a mid-market operation (500-5,000 orders per month, 1,000+ SKUs):

• Shopify build: 4-8 weeks (theme, configuration, content migration)
• Integration rebuild: 2-4 weeks (runs in parallel with the Shopify build after Phase 1)
• Data migration: 1-2 weeks (products, customers, redirects)
• Parallel run and testing: 1-2 weeks
• Total: 8-14 weeks minimum

The integration rebuild is the variable. Simple flows (orders in, inventory out) with a standard connector take two weeks. Complex flows (multi-subsidiary, multi-currency, custom pricing, B2B and DTC on the same store) take four weeks or more.

---

Common mistakes that cost weeks

Forgetting URL redirects. This is an SEO disaster. If your current site has domain authority and organic rankings, broken URLs mean those rankings disappear. Build a comprehensive redirect map before go-live. Audit it post-launch. Check for 404s weekly for the first month.

Not testing order edge cases. Standard orders work. Then a customer places an order with a coupon, a gift card payment, split shipping to two addresses, and a backordered item — and the integration chokes. Test the weird orders before go-live, not after.

Going live on a Friday. You will discover integration issues under real traffic. Discover them on a Tuesday when your full team is available, not on a Friday afternoon when everyone is heading out.

Treating the integration as a follow-up. Teams sometimes launch Shopify with manual processes ("we'll sync orders manually for the first week while integration gets sorted"). Manual order entry at scale is how you get data entry errors, missed fulfillments, and incorrect inventory counts. Launch with the integration working or do not launch.

Skipping the parallel run. Going straight from the old platform to Shopify with no overlap period removes your safety net. If the integration has a bug that silently drops 5% of orders, you want to catch that while you still have the old system running.

---

Frequently Asked Questions

Can I migrate my existing Celigo flows from Magento to Shopify?expand_more

Will my customers lose their order history after migrating to Shopify?expand_more

How long does a Shopify migration take when NetSuite integration is involved?expand_more

Should I migrate to Shopify or Shopify Plus?expand_more

What happens to my SEO rankings during the migration?expand_more