Neto (Maropost) → to Shopify

Neto to Shopify: moving an operations-heavy Australian store without losing the back office

Neto started in Brisbane in 2009 and became one of the most common platforms for Australian and New Zealand retailers and wholesalers. Maropost bought it in 2021 and folded it into Maropost Commerce Cloud, and today the same platform is sold as Neto by Maropost. Whichever name is on your invoice, a Neto to Shopify migration is rarely just a web store move. Neto stores tend to run wholesale pricing, kits, several warehouses, eBay and Amazon listings and sometimes the shop counter from one control panel. This guide covers how we move all of that to Shopify, what each Neto feature becomes, and what it costs.

Why stores leave Neto

• Cost that grows with every channel. Neto plans are priced by sales channel and by annual revenue. At the time of writing the Essential plan starts at AU$199 a month with one channel, and each additional channel (the online store, eBay, Amazon and POS all count) adds AU$99 a month. Inventory, labeling and pick-and-pack tools are paid add-ons on the lower plans.
• A smaller ecosystem. Neto’s add-on library and partner network are mostly Australian. Shopify’s app store, theme market and developer pool are far larger, so most integrations are an install rather than a project.
• Storefront and checkout. Neto’s own documentation notes the checkout page cannot be tweaked. Shopify’s checkout, Shop Pay and the Horizon theme give a modern front end without custom template work.
• Ownership and direction. The platform has changed name twice since the acquisition, and Maropost now also sells a separate Commerce Cloud product. Some merchants would rather be on a platform whose roadmap is easier to read.
• Fairly, what Neto does well. Native warehouse management, kitting, customer groups and marketplace listing all live in one system. Moving to Shopify means choosing the right native feature or app for each of those, which is exactly what the audit is for.

What migrates from Neto to Shopify

Neto has good data tools. Its import and export wizards handle products, categories, content, customers and orders in CSV or XML, and its API (JSON or XML, with calls such as GetItem, GetOrder and GetCustomer) fills the gaps the CSVs leave.

Data	Source on Neto	Moves to Shopify?
Products with SKU, name, descriptions, prices, cost, barcodes, weights, dimensions, brand, images, SEO fields	Product export wizard (complex export) and GetItem	Yes. SKU stays the join key throughout. Brand becomes vendor; custom fields become metafields.
Variation products (a parent with child SKUs and specifics)	Parent SKU and Specifics columns	Yes. The parent becomes the Shopify product and each child becomes a variant. More than three specifics needs a restructure.
Kits, hampers and bundles	Kitting components on the kit SKU	Yes, rebuilt as bundles with stock worked out from the components.
Categories and content pages	Category and content export wizard	Yes. Categories become collections; information pages and blog posts become pages and articles.
Customers, addresses, customer groups, marketing consent	Customer export wizard and GetCustomer	Yes. Groups become B2B companies, catalogs or tags; consent carries exactly.
Group prices and multi-level (quantity break) pricing	Pricing and multilevel pricing fields per product	Yes, into B2B catalogs with volume pricing, or an app where the structure needs it.
Sales orders with lines, payments, dispatch details and tracking	Sales order export wizard and GetOrder	Yes, as real orders with the original order number, date, payments and tracking numbers. Refunds become real refund records.
Stock per warehouse	Warehouse stock fields	Yes, as inventory per Shopify location.
Gift vouchers, account credit, rewards points	Voucher and customer records	Balances recreated as Shopify gift cards, store credit and loyalty app balances.
Passwords	Not exportable	No. Customers reset on first login or use passwordless sign-in.
Theme and B@SE templates	Neto theme files	No. The design is rebuilt on Shopify.

Neto URLs and the 301 map

Neto builds product URLs from a template (the SITE_URL_FORMAT_PRODUCT setting, with tags such as {lc_name}, {lc_sku} and {lc_path}), and on most stores that means products sit at the root of the domain, for example /womens-slim-fit-scrub-pants. Categories use nested paths with a trailing slash, such as /women/scrub-tops/. When two items would share a URL, Neto adds a suffix, so live stores carry forms like /product-name~84654 and /category/sub-category/~-6210. Stores that changed their URL template or ran “Regenerate URLs” often have older forms still indexed, and Neto’s own documentation warns that regeneration does not create redirects. Shopify uses /products/handle and /collections/handle, and cart and account paths such as /_mycart change too.

We build the map from the product and category exports (which carry each item’s current URL), the store’s own 301 redirect list under Settings & Tools, a crawl of the live site and the Search Console page list. Because product URLs sit at the root with no prefix, we join on SKU and the exported URL field rather than guessing from slugs. Every redirect is requested against the live domain before and after launch.

Tools

Cart2Cart, an RDA partner, and LitExtension both list Neto as a source for Shopify. They are fine for a first pass on products, categories and customers, and we use them where they fit. Where they fall short is the detail that matters on a Neto store: they do not carry tracking numbers on dispatched orders, they tend to model refunded orders as plain paid orders, and their redirects are built from guessed slugs rather than Neto’s real URLs. Nor do they rebuild group pricing, kits or per-warehouse stock the way a Neto store uses them. We finish those parts ourselves from the Neto exports and API, and reconcile every count.

How we run it

1. Audit. Exports, API access, URL crawl, variation and kit analysis, customer groups, warehouses, marketplaces, POS and integrations, ending in a fixed-price scope.
2. Build in a free Shopify development store. As a Shopify Plus Partner we build there, so you pay Shopify nothing until launch. Theme, checkout, payments, GST, shipping and Markets are set up here.
3. Catalog. Products, variations, kits, images, custom fields and collections, with any products over Shopify’s option limits restructured.
4. Customers and price groups. Customer records, consent, groups mapped to companies, catalogs or tags, and group and quantity pricing.
5. Orders. Full history with original numbers, payments, refunds and tracking.
6. Marketplace listings. eBay and Amazon listings linked to the new Shopify products so listing history is kept.
7. Redirects. The full 301 map, tested.
8. Sample, then full import, with reconciliation. A sample of every data type for your sign-off, then the full run, reconciled against the Neto export counts.
9. Cutover with delta sync. DNS switch, then a final pass for orders, customers and stock that changed on Neto after the main import.
10. Post-launch SEO evaluation. Once Google has re-crawled the store and the first real analytics exist, we review indexing, 404s, rankings and traffic against the pre-launch baseline and fix what it shows.

Cost and timeline

A Neto to Shopify migration starts from $2,500 (US dollars) for stores under 500 products and 5,000 orders ($3,500 for larger stores), and typically takes six to eight weeks. Larger catalogs, marketplace channels, POS and integrations such as Xero or MYOB are quoted as a fixed price after the audit. Terms are 50 percent to begin and 50 percent once the store is live and you are fully satisfied with the figures. We work across time zones with Australian and New Zealand merchants, with cutovers timed for your quietest trading window.

Variations, kits and custom fields

Neto variation products are a non-purchasable parent with child SKUs, each with its own name, price, stock, images and dimensions, linked by the Parent SKU and described by specifics such as Colour:Red;Size:Medium;. That maps cleanly to a Shopify product with variants, with two limits to plan for. A Shopify product has at most three options, and Neto allows more specifics than that, so a child described by color, size, style and fit needs one specific folded into another or moved to separate products. Shopify now allows up to 2,048 variants per product, so large size and color grids are rarely a problem, although some older apps still read only the first 100. Child-level names and descriptions do not exist on Shopify variants, so where they carry real information we keep it in variant metafields.

Standard kits become bundles through Shopify’s free Bundles app, which also works out availability from the components, just as Neto does. Editable kits, where the customer picks components, need a bundle app that supports customer choice, and we pick one in the audit. Neto custom fields, specifics used for filtering and eBay item specifics become metafields, so the filters on the new store and the marketplace listings both keep their data.

Customer groups, price groups and B2B

Neto’s customer groups (six by default, up to 64) drive group prices on every product, group-specific quantity breaks, hidden products and categories, payment methods and minimum order values. Many Neto wholesalers also use payment terms, credit limits and account credit. Shopify B2B now runs on the Basic, Grow and Advanced plans as well as Plus, with company profiles, net payment terms, quantity rules and volume pricing on all of them. The limit that matters is catalogs: non-Plus plans allow three active B2B catalogs, while Plus is unlimited.

So the mapping depends on how many groups really have their own prices. Two or three price groups fit native B2B catalogs on any plan. A dozen distinct price lists needs Plus or a wholesale app. Retail-only groups such as VIP discounts usually become customer tags with automatic discounts. Account credit moves to Shopify store credit, and credit limits, which Shopify B2B does not enforce natively, are recorded on the company and handled by an app where you rely on them. Group assignments come straight from the customer export, so no trade customer loses their pricing.

Marketplaces, warehouses and POS

Neto lists to eBay, Amazon and several Australian marketplaces from the product record and pulls those orders back in. On Shopify, Marketplace Connect (built by Shopify and free to install) links each product to its existing eBay or Amazon listing and syncs stock, prices and orders. We link listings rather than relisting, so sales history and watchers stay with the listing. Kogan, MyDeal and Bunnings run through their own connectors or a feed app, and we confirm each channel and region in the audit.

Each Neto warehouse becomes a Shopify location with its own stock. Neto’s built-in pick-and-pack, bin locations and purchase orders are the parts most likely to need an app or a warehouse system alongside Shopify, and we size that honestly before you commit. If you use Neto POS, the counter moves to Shopify POS, with one inventory and customer list shared with the web store. POS Pro is priced per location, and we confirm your iPads, scanners, printers and card reader in the audit, then switch on a quiet day with a stock count.

GST, AUD and shipping in Australia and New Zealand

The store is set up in AUD with GST-inclusive prices, matching what Neto customers already see. If you sell into New Zealand, Shopify Markets adds it as a second market with NZD pricing, and a separate domain per market (your .com.au and .co.nz) is available on every plan. Basic, Grow and Advanced include three markets, which covers Australia, New Zealand and one more.

Shopify Shipping in Australia includes Australia Post labels and rates on any plan through a MyPost Business account, and Sendle labels and rates are built in. Australia Post eParcel is not supported natively, so eParcel, StarTrack and couriers such as CouriersPlease run through a shipping app. Live rates from your own third-party carrier accounts at checkout need the Advanced or Plus plan, or Grow with annual billing or an extra monthly fee, so we compare that against a well-built rate table before recommending an upgrade.

What you get at handover

Every Neto migration ends with a reconciliation ledger from the Neto export counts to the live Shopify counts for products, variants, kits, customers, orders and stock per location, with every exclusion named; the redirect verification list with the status each URL returned; the customer group and price mapping; the marketplace listing link report; a record of which Neto features moved to which Shopify feature or app; and a recorded walkthrough of the Shopify admin for your team.

Questions we settle in the survey

• Which customer groups have their own prices, and how many trade accounts use payment terms or credit limits?
• Which marketplaces do you list on, and in which regions?
• How many warehouses hold stock, and do you rely on Neto’s pick-and-pack or purchase orders?
• Do you use Neto POS, and on what hardware?
• Do you need live carrier rates at checkout, which decides the Shopify plan?
• Which accounting system is connected, and should history re-sync or start fresh at cutover?

Frequently asked questions

Start with the migration survey. If marketplaces are a big part of your trade, read our Shopify and eBay integration guide, and for another store with wholesale pricing and deep order history, see the BigCommerce to Shopify migration guide.