Moving from Sana Commerce to Shopify? Your ERP setup is an important part of planning the transition.
We review how your current store uses SAP or Microsoft Dynamics for product information, customer pricing, inventory, and orders. If you plan to keep using your ERP, we'll identify the integrations needed to connect it with Shopify. If you're looking to simplify your setup, we'll help you assess which functions Shopify can handle on its own.
or call 888-711-2347
Includes 60 days of free migration support after launch. We stay with you once the move is done.
Official Shopify Partner
Since 2015 · Shopify store migration, design and development. View profile ↗
Illustrative workflow, not a live project
Attention: 6 items need attention.
Is every layout or checkout tweak harder than it should be because the store hangs off the ERP?
G2 reviewers say the front end and user experience have little room to move, since the store is built around ERP constraints. Sana’s own documentation says the ERP does the basket calculations and holds the business logic.
Think about how often you actually want to test layouts, content or checkout changes. Shopify themes and apps give you plenty of room on the storefront, but pricing and order rules would have to be rebuilt outside your ERP.
Does the subscription creep up faster than your sales do?
Sana lists three plans and shows no public prices. A few G2 reviewers call the platform expensive, with pricing that’s hard to budget for. Third party sites guess at costs in different ways, so treat any figure you see as unverified.
Pull out your current contract and add hosting, the ERP add-on and partner fees. Then set that against a Shopify plan plus apps and ongoing development, because Shopify has recurring costs too. That comparison is the Sana Commerce pricing question worth answering.
Can your online store only do what the ERP behind it allows?
Sana is built as an add-on inside the ERP. Its documentation says products, customers, prices, tax and sales documents live in the ERP and not in Sana. It is a deliberate design and a strength for some businesses, but it does tie the store to the ERP.
If you plan to change ERP, or you want selling rules the ERP doesn’t hold, this coupling matters. On Shopify the ERP link becomes an integration you maintain, so find out what that costs.
Do custom features take a long time and need a specialist?
Migration agencies report that users often describe weak technical support and custom changes that are slow and costly. Those are agency claims, so experiences vary, and G2 reviewers also praise ease of use and the range of integrations.
Write down your last few change requests and how long each took. Shopify has a large pool of apps and developers, though custom work there costs time as well.
Do you want business and consumer sales in one store instead of two systems?
One migration agency says Sana ties the storefront straight to the ERP, and that adding direct to consumer sales can mean a separate platform. That’s agency positioning, so check it against your own contract and setup.
If you want both, Shopify can serve business and consumer customers from one store using Markets and B2B features. Plan limits apply, so we look at the details for your case.
Is there an SEO or image optimization control you keep wishing you had?
A small number of G2 reviewers mention missing SEO and image optimization features, and weak product image search. It’s a small sample, so experiences vary.
Write down the SEO controls you need, such as redirects, metadata and structured data. Shopify handles many natively and apps cover more, though results still depend on how it’s set up.
Pet supplies
Advance Pet Mart started on WooCommerce, but plugin and hosting problems kept getting in the way. We moved the store to Shopify, and they are very happy with the move. We also worked with them on design, SEO, AI SEO and marketing.
Visit the live store
Electronics & gaming retail
We moved City of Games from a broken OpenCart store to Shopify in four weeks, kept its look, rebuilt the features it had lost and protected its search rankings with 301 redirects.
Read the case study
We moved Contours Rx from BigCommerce to Shopify and redesigned the website with a sleek, user-friendly interface and enhanced product pages.
Visit the live storeMove and rebuild. Best when your data has to move and the storefront has to be rebuilt on Shopify.
Quoted after a free store review
Move a complex business. Built for large or heavily customized stores and the systems wired into them.
Custom quote once discovery is done
Included in every migration. Redirects for your old URLs, titles and descriptions carried over, and 60 days of free support after launch. Quotes don’t cover your Shopify plan, apps or other third party costs.
Variants and cross-system IDs
From ERP, PIM or Sana
Files checked for access
Rebuilt agreed content
Translations and markets
Companies, locations, buyers
Catalogs or connected logic
Import, connection or archive
Portal access or retained
An agreed transition
Available consent only
A tested redirect map
Where each item ends up and what we check before launch.
| Sana Commerce / ERP | Where it goes in Shopify | What we check |
|---|---|---|
| Products, variants & identifiers | Live Shopify data covering products, variants and agreed custom fields. | How records relate, their units, and IDs that match across ERP, PIM and Shopify. |
| Specifications, images & documents | Product fields, files and presentation as agreed. | Which source wins (ERP, PIM or Sana), whether files open, and whether anything is missing. |
| Pages, navigation & localized content | The agreed content, rebuilt in Shopify. | The real public URLs, translations and design needs. |
| Sana Commerce / ERP | Where it goes in Shopify | What we check |
|---|---|---|
| ERP customers & web accounts | Companies, locations and customer records as agreed. | Account relationships survive and don’t get reduced to an email list. |
| Prices & commercial rules | Agreed catalogs, rebuilt features or a price calculated by the connected ERP. | The price each customer actually pays, and which rules are covered, tested on representative accounts. |
| Active quotes & agreements | A supported handover, or a process that stays where it is. | Who owns each one, when it expires, and what is committed or still open. |
| Sana Commerce / ERP | Where it goes in Shopify | What we check |
|---|---|---|
| Historical orders | A supported import, access through the connected ERP or an agreed archive. | Whether each order was online or offline, plus dates, line items, totals and source references, and no new ERP orders created. |
| Invoices, credit notes & shipments | Access through a connected portal, or records kept as they are. | Not every ERP document should become a Shopify order. |
| Sana Commerce / ERP | Where it goes in Shopify | What we check |
|---|---|---|
| Marketing preferences | Consent you actually have, mapped to subscriber status. | ERP contacts don’t get subscribed automatically. |
| SEO information | Useful content and a tested map of where each URL lands. | Which content is public and which is restricted, and whether the redirects can work. |
A CSV of Sana shop accounts doesn’t hold the whole business dataset. Imported orders don’t carry their original payment transactions, saved payment credentials aren’t assumed to be portable, customer records don’t automatically become marketing subscribers, and imported history doesn’t recreate operational rules.
A record might become live Shopify data, get rebuilt as a working feature, or stay in the ERP behind a connection or in an agreed archive.
Which ERP, which version, and how it has been customized.
Pricing, agreements, units and credit controls.
Logins, approvals, quotes and repeat orders.
Where it lives, what shape it’s in, media and translations.
The ERP connection, and who builds and supports it.
Order history, documents and who does what at launch.
Your proposal keeps our project fee apart from the costs of Shopify, connectors, integration providers, apps, themes, ERP licenses and ERP partners. Price and schedule are confirmed once the review is done.
FreeA store review and quote before you hire us
60 daysFree migration support after launch, included
Tell us how your customers order and which ERP runs your business. We look over the storefront and the connections behind it, then lay out the route, what moves, what gets rebuilt and what the project will cost.
You don’t need technical knowledge or any idea how your integrations are architected. Exports, price lists and logins aren’t needed to start, and we arrange secure access later.
Products, customer accounts, prices, discounts, stock, terms, orders, invoices and shipments that come from SAP or Microsoft Dynamics.
We confirm the product, version and customizations.Pages, navigation, settings, shop accounts and content you manage in Sana, and which Sana deployment you run, Sana Cloud or an older one.
Some useful information never reaches the ERP.Richer descriptions, specifications, images and documents kept in a PIM, outside file storage or other connected systems.
Pulled from the right source.Who looks after each integration today, how it’s deployed and accessed, and which ERP partner supports your environment.
We agree early who handles the ERP side.They can’t be swapped for one another. A connector built for Business Central says nothing about NAV or SAP, and a general SAP claim doesn’t reach every SAP product or customization.
Unsure of the exact ERP version? Give us the names you know and describe how your customers order. We work out the rest in the review with your team and ERP partner.
Sana can connect to SAP ERP products, yet it runs as its own commerce platform with its own data and methods. This page is about Sana Commerce storefronts, whichever ERP sits behind them.
What we assess
What we review
We go through each requirement and agree how it will work after launch. Then we confirm the Shopify plan, the integrations, the cost and the acceptance tests. Some complex workflows make a full move a poor fit, and the review is where we’d say so.
Every record has one owning system. We note where your team edits it and who supports the connection once you’re live.
We settle products, prices, stock, customers, orders, fulfillment updates and documents one at a time.
A value can be copied into Shopify ahead of time, or the ERP can work it out the moment a customer orders. We pick per value.
What happens if an update fails, how retries run, and how we compare the two systems afterwards.
| Dataset | Source → destination | Status |
|---|---|---|
| Products & content | ERP + PIM → Shopify | Agreed |
| Customer prices | ERP calculation or sync | Decide |
| Stock & availability | ERP → Shopify, scheduled | Agree timing |
| Companies & buyers | ERP ↔ Shopify | Map |
| Orders | Shopify → ERP | Test |
| Fulfillment updates | ERP → Shopify | Test |
| Invoices & documents | Check the approach | Not assumed |
A price copied into Shopify is not the same as a price the ERP calculates for the current order, and scheduled stock updates are not live availability. We set the delays you can accept and what the customer sees if the connection fails. Installing an integration app doesn’t reproduce Sana’s real time behavior on its own.
Connector, integration platform or custom development? Each one fits a different environment. We won’t name a middleware product until we’ve gone through your ERP, version and requirements with the responsible team, and an installed connector doesn’t prove every business rule is covered.
Who qualifies, quantity breaks, effective dates, currency, tax treatment, minimums, rounding and how discounts stack.
We test on representative customers.Committed quantities or amounts, what has been released and what remains, expiry dates and order references. A sales agreement works nothing like a discount code.
What’s possible depends on your ERP and version.Alternative units, pack sizes, minimum quantities, and the quantity that really reaches the ERP and fulfillment.
Renaming a unit doesn’t convert it.Net payment terms, account blocks, credit limits, credit exposure, unpaid invoices and purchasing approvals, each handled on its own.
We test every control separately.The panel on the right is a sample. Field names, units and values depend on your ERP and setup.
| Customer account | Northside Branch |
|---|---|
| Selling unit pack | Case of 12 |
| Contract price per case | 38.40 |
| Quantity sent to ERP | 2 cases |
| Company location | Northside Branch |
|---|---|
| Variant | Case of 12 |
| Price | 38.40 |
| Line in ERP order | 2 cases |
The test passes only if the ERP receives 2 cases, not 24 units, at the agreed price.
Shopify’s B2B features are spread across several plans, and catalog assignment and some advanced features differ between them. Its current documentation keeps direct company specific catalogs for Shopify Plus, and no connector can add a platform feature your plan lacks. We check Shopify’s current plan terms and the connector version you’d use, then recommend a setup. Plus isn’t required for every Sana merchant.
Limits on sub accounts, authorization stages, approvers, pending orders and the ERP status changes that go with them.
Shopify roles don’t map across automatically.How sales agents act for customers and place orders, with permissions and accountability agreed up front.
We don’t assume Sana’s behavior carries over.Quote requests, acceptance and quotes still open. Shopify draft orders can’t reproduce every Sana quotation behavior.
Each open quote gets an owner.Quick ordering, shopping lists, reorders and any recurring purchasing, judged on how your customers really use them.
Unusual workflows get checked one by one.Passwords and single sign on won’t carry over by themselves. We plan the Shopify customer account setup you choose and assess any identity provider requirements on their own, so customers know how they’ll sign in after launch.
Online and offline orders, invoices, shipments, credit notes, returns and any other document customers view or download.
Not every ERP document belongs in Shopify as an order.Finding the document, matching the right customer, the outstanding balance, the payment provider, partial payments, allocating each payment to the ERP document and reconciling it.
A payment link doesn’t prove allocation.Open quotes, partly fulfilled orders, returns, credits and unpaid balances, each given an owner we agree on.
Services you still need stay on until it’s resolved.We test access by company and by person so nobody sees another account’s prices or documents.
We try it with a login from the wrong account.We don’t promise a complete native invoice portal until the implementation has been validated. The agreed destination might be a supported integration, a portal or an archive, and the ERP remains the financial system of record.
When the connection goes live and which orders it may send.
Imported history gets marked, stays out of the order flow and triggers no customer notifications.
We agree and test source references, retry behavior and duplicate detection.
Shopify and ERP orders get compared with each other after testing and again after launch.
| Scenario | Expected result | Type |
|---|---|---|
| Correct account & contract price | Order reaches the ERP once | Core |
| Required approval | Held until approved | If required |
| Unauthorized buyer | Can’t order or see prices | Core |
| Blocked account | Stopped at the agreed stage | If required |
| Integration failure | Error flagged, no lost order | Core |
| Retry | No duplicate ERP order | Core |
| Historical import | No new ERP order or email | Core |
A customer picks the correct account, orders two cases at its contract price and goes through the required approval. After that we check the ERP acknowledgement, the stock, the shipment and the customer’s access to the resulting documents. It shows how we test and isn’t a client result.
Product templates, navigation, customer friendly content and editable sections, or agreed parts of your current design.
Explore theme & design →Scoped workflows and integrations for when no existing solution meets the requirement.
Explore app development →The migration checks we agree for URLs, content and metadata, with ongoing optimization sold as a separate service.
Explore Shopify SEO →SEO, paid advertising, email and other channels that fit wholesale, direct selling or both.
Explore ecommerce marketing →The migration gets its own quote. Redesign, extra development and ongoing marketing come in only if you want them, each with its own scope and price.
Importing a catalog doesn’t bring these connections along. After launch we check the feeds, tracking and consent settings we agreed to cover.
Shopify has its own URL structure and redirect limits. Rankings can move after any migration, so we don’t promise identical URLs, steady rankings or traffic growth that happens by itself.
Sample checks we run. A hidden menu doesn’t restrict access on its own.
Before choosing the Shopify setup, we go through your domains, legal entities, ERP companies, currencies, catalogs and shared operations. Shopify Markets doesn’t automatically mirror the company structure in your ERP.
Pointing a domain at Shopify doesn’t transfer its registration. A domain you own can usually connect without a change of registrar, and we look at DNS first.
Shopify doesn’t host email inboxes. If mailboxes or other services rely on the same domain settings, we plan for them before touching anything.
We hang on to the agreed content, records and system access until the dependencies and open obligations are cleared.
We always arrange access to Sana, your ERP or connected systems securely, and never through the public enquiry form.
Migration tools and ERP connectors can move or synchronize common records, and many come with good support. If one fits your data and ERP, we can use it inside the project. Our responsibility covers the agreed work around it, which is source review, business rule mapping, data preparation, storefront, integration decisions, representative testing, launch and agreed support.
| Your question | Tool or connector on its own | Migration managed by WEP |
|---|---|---|
| Who works out the sources? | You pick from the records and fields the tool supports. | We go through the ERP, Sana, PIM and file sources and write down what moves. |
| And pricing and terms? | Supported fields synchronize, and you check the business rules yourself. | We map the commercial rules and test with representative customers. |
| And accounts and documents? | Usually depends on the connector and extra setup. | Every relationship, permission and document need gets a destination we agree on. |
| Who builds the new storefront? | Normally a separate job. | Theme setup or customization planned alongside the data. |
| Who handles launch? | Your team coordinates the cut off, routing, domain and checks. | We run the agreed launch, reconcile late orders and give you 60 days of free support. |
The online store migration was seamless without having 0 downtime. The staff is properly trained, well communicated and proactive Highly recommended
Web commerce pros created a really lovely design for our website. They also changed the layout for our images and updated/resized images so that the site is overall much more attractive. We have been receiving a lot of positive feedback from customers on the ease of use and the overall look of our site. In addition, we are very grateful to Roy for coming up with a creative solution for allowing customers to easily create their own quotes, which has been very helpful to both our operations and our customers.
Arfat and team were proficient with BigCommerce Page Builder and Shogun to create and modify pages. We successfully completed the migration with their assistance and were happy with their work. We would hire again soon for our next project.
We pin down the Sana, ERP and PIM sources, the customer workflows, connector options, responsibilities and costs.
Shopify gets built on its own, then we test representative records, account access, commercial rules and an order all the way through to fulfillment.
A catalog control or change log, chosen final updates, the transaction cut off, integration routing and who owns open orders, quotes and invoices.
We handle the domain and connections, confirm that each agreed new order reaches the ERP once, and account for any late Sana orders.
That way the switch is planned ahead.
We coordinate the migration around a defined cut off, and the new ERP connection is its own piece of work with agreed operating rules. We reduce the risks. We don’t promise an uninterrupted switch, or ongoing automatic two way synchronization beyond what is scoped.
No, your ERP can stay exactly where it is. On Shopify it connects through an integration app or middleware in place of the Sana add-on, and we plan that connection with you.
The data model changes. Sana’s documentation says it reads product, price and order data live from the ERP, while a Shopify store holds its own catalog and prices. You decide what syncs from the ERP and how often.
Yes, up to a point. Shopify B2B supports company accounts, catalogs, volume pricing, quantity rules and payment terms, though some limits depend on your plan. Complex ERP pricing logic may need an app or a custom build, and we look at your pricing in the free store review.
We do. Our team handles the data move, theme build, integration planning, testing and launch, and keeps you involved in decisions. Your ERP partner may be needed for the integration side.
Mostly in your ERP. Sana’s documentation says product and customer data is managed there, so the ERP is usually the best source for an export. Web content and settings managed in Sana Admin may need to be rebuilt by hand, and we confirm what you have during the free store review.
Usually, yes. Sana documentation says orders and sales documents are stored in the ERP, so history can normally come from there. Whether it fits Shopify’s order import depends on how it is structured, and we confirm that during the review.
Customer and contact records can usually be exported from the ERP and mapped to Shopify companies and customers. Passwords don’t come across because Shopify does not import them, so each person sets a new one through an account invite.
Possibly, with extra work. Sana documents these as ERP records shown in the webstore. Shopify has its own order, invoice and returns features, and showing ERP documents may need an app or integration. We confirm what is practical for your setup.
Possibly. Page addresses differ between platforms, so we map old URLs to new ones with redirects. A move can cause temporary ranking changes, and we can’t promise unchanged rankings.
We can’t promise zero downtime, but we aim to keep any gap short. The new store is built and tested separately while the current one keeps selling, then we switch at a planned time.
Usually not as an exact copy. We design the Shopify theme to fit your brand and what your customers need, and you can keep the key elements you like.
Yes. You keep your domain and point it at the new store at launch, and your email settings stay untouched unless you ask for changes.
That depends on your ERP integration, pricing rules and catalog size. You get a realistic timeline from us after the free store review.
Maybe, so compare the numbers. Sana pricing is quote based, so set your actual contract beside a Shopify plan, apps, integration costs and our build work. A written estimate follows the review.
Not always. Shopify says many B2B features come with several plans, and a few, such as unlimited catalogs and partial payments, are limited to Plus. Plan rules change, so we check them against what you need.
Yes. We go through your store, ERP setup and pricing, then tell you what moves, what needs rebuilding and what it may cost, with no obligation.
Send your store URL, the ERP name and a short note on how your customers buy. We arrange deeper access securely once we’ve talked, and every migration includes 60 days of free post-launch migration support within the agreed scope.
Tell us how your customers order and which ERP runs your business. We’ll look at the storefront and the connections you need, then propose a route, a scope and a quote.
Or call 888-711-2347
60 days of free migration support after launch, within the agreed scope.
