Neto to Shopify: What the Move Actually Costs an Australian Retailer

Neto's merchant base is shrinking and Shopify is where the leavers go, but the product itself is alive. Store detection data from StoreLeads shows a peak of 2,401 active Neto stores in the third quarter of 2022 against 1,790 in the second quarter of 2026, which StoreLeads puts at down 9 per cent year on year. Australia accounts for 81.9 per cent of those stores. Over a trailing 90 day window, 19 merchants left Neto and 13 arrived, and 14 of the 19 departures went to Shopify. Detection-based data undercounts by nature, since it depends on recognising a platform's fingerprint on a live site. Read those numbers as direction rather than as a census. Neto's own figures point the same way. Coverage of the Maropost acquisition, announced on 18 March 2021, described Neto as serving over 3,000 retailers and wholesalers worldwide. The current site claims 2,000-plus merchants. A vendor's own headline number coming down by roughly a third in five years is meaningful, because marketing figures usually flatter. None of that means the product is dead. Maropost publishes dated Neto release notes, including one dated 12 January 2026, and a 14-day free trial with no credit card required was open at the time of writing. There is no announced end of life. Neto is smaller than it was, still sold and still developed.

The hard part of leaving Neto is replacing what it bundles into one subscription. Neto's own feature material covers native point of sale for shopfront and mobile selling, warehouse management with goods-in, goods-out, returns and a mobile pick and pack app, sync across 30-plus marketplace integrations including eBay, Amazon and Catch against a single inventory pool, Australia Post, eParcel and NZ Post logistics, Tyro terminals and Elo Paypoint hardware, and B2B wholesale portals with per-customer access. These are vendor feature claims rather than independently tested results, but they describe what the subscription covers. On Shopify, most of that lives outside the platform. Shopify's strength is the storefront, the checkout and the app market; multichannel selling, warehouse management and deep inventory are app territory, and B2B sits mainly in the Plus tier. We deliberately did not name specific Shopify apps or their prices for the Australian market. Shopify's eBay and Catch channel situation has changed repeatedly over the years and naming the wrong app is worse than naming none. Price it yourself, and do it before you compare subscriptions: list the Neto features your operation genuinely uses, then get a real monthly figure and a real integration estimate for each Shopify replacement. Neto is also the only major Australian-built platform in its competitive set, so AU tax handling, shipping and marketplace connections are native rather than localised afterwards. If your revenue depends on Catch or on eParcel, confirm the replacement exists and is maintained before you commit to anything.

Shopify's published subscription prices undercut the top of Neto's range, and the comparison is not like for like. All figures below are AUD per month, published by each vendor, and exclude tax. | Plan | Monthly (AUD) | Annual billing (AUD per month) | |---|---|---| | Neto Essential | $199 | not published | | Neto Professional | $789 | not published | | Shopify Basic | $56 | $42 | | Shopify Grow | $149 | $114 | | Shopify Advanced | $575 | $431 | | Shopify Plus | from $3,700 | custom | The useful line in that table is that a Neto Professional merchant paying $789 a month is paying more than Shopify Advanced at $575. Read past it carefully, though, because the two vendors gate on different things. Neto gates on revenue and channel count: Essential covers one sales channel and up to $250,000 of revenue a year, Professional covers three channels and up to $1 million. Shopify gates on features and card rates. Once you add the Shopify apps that replace Neto's bundled inventory, POS and marketplace features, the columns stop being comparable. Add Neto's own add-ons on the other side if you use them, at $99 a month per extra sales channel, $199 for Neto Inventory, $99 each for Neto Ship and Pick and Pack, and $199 for Glew Analytics. Build the real monthly total for your own store rather than comparing the headline plan prices.

Shopify charges an extra fee on every transaction processed through a payment gateway other than Shopify Payments, and it is the line that changes the whole comparison. The published rates are 2 per cent on Basic, 1 per cent on Grow, 0.6 per cent on Advanced and 0.2 per cent on Plus. Neto charges no transaction fee of its own, so if you move and keep your existing gateway, that percentage is new money leaving the business on every order. Work it through at a million dollars a year of online revenue. On Shopify Basic, a 2 per cent third-party gateway fee is $20,000 a year, roughly thirty times the annual subscription at $42 a month. On Advanced at 0.6 per cent it is $6,000. Neither number appears in a migration quote. Shopify Payments is available in Australia, with published AUD rates of 1.75 per cent plus 30 cents online on Basic, 1.6 per cent plus 30 cents on Grow and 1.4 per cent plus 30 cents on Advanced. Switching to it avoids the penalty, but understand what you are agreeing to: that is a change of payment provider stacked on top of a replatform, with its own settlement timing, chargeback handling and reconciliation changes for whoever does your books. If you are replacing Neto's bundled point of sale, add Shopify POS Pro at $129 a month per location.

Cart2Cart explicitly supports Neto as a source and Neto to Shopify as a named migration path, covering products, customers, categories and orders. LitExtension and Next-Cart market the same route. Every one of those companies sells migrations, so read their timelines, success rates and prices as sales material rather than as findings. We could not find a single independent, methodologically transparent account of a Neto to Shopify migration anywhere. One correction is worth having, because a lot of published advice gets it wrong: Matrixify does not support Neto as a source. Matrixify is a Shopify-side bulk loader that imports and exports Shopify data through spreadsheets. Using it in a Neto migration means exporting from Neto yourself and reshaping the data into Matrixify's template format. It is genuinely useful on the destination side, where you will load and reload large product files while the field mapping settles, but it is not a Neto connector and treating it as one will cost you a planning cycle. We also found no evidence of a Shopify-built importer specific to Neto. Assume generic CSV for products and customers unless Shopify tells you otherwise, and get that confirmed in writing rather than assumed in a proposal.

Stored payment and card details never migrate, and that is the item most likely to hurt. Card credentials do not move between platforms for payment security and privacy reasons, so saved cards are gone and any subscription or recurring billing arrangement has to be rebuilt with every customer re-authorised. If a meaningful share of your revenue recurs, that is a customer communications project with churn risk attached, not a data task, and it belongs in the plan with its own owner and its own dates. Anything built with plugins or custom code is rebuilt rather than moved. Subscriptions, loyalty programs, product customisers and one-off integrations live inside your current platform's extensions, and there is nothing to export. Price them as new builds. Tax rules and shipping zones are configuration, not data. They start fresh and someone has to re-enter and test them, including free shipping thresholds, remote-area surcharges, bulky item rules and any wholesale tax handling. Order history usually can move, and it is worth moving even as read-only reference. Migration vendors recommend bringing at least 12 to 24 months so support staff can answer a question about an order from six months ago. That is vendor advice, but it is sound, because the alternative is paying to keep the old platform running purely as a lookup tool.

Shopify forces `/products/` and `/collections/` into its URL paths and the structure is not fully configurable, so a one-to-one URL match with your Neto site is generally impossible. That makes a full 301 redirect map mandatory rather than optional, and it is the most common way a replatform loses money quietly, because nothing looks broken. Build the map before cutover, not after. Crawl the live Neto site in full, pull top URL data from Google Search Console, and map every URL that has ever earned a click or an inbound link to its Shopify equivalent. Where no equivalent exists, make a deliberate decision and send it to the nearest relevant collection rather than the homepage, because a homepage redirect for a dead product page behaves like a soft 404 and earns you nothing. On the numbers, be sceptical of everyone including us. There is no credible published figure for organic traffic loss after a same-domain replatform. The percentages circulating in migration content trace back to vendor internal research with no stated methodology. The most-cited study, covering 892 migrations with an average of around 523 days to recover, measures domain changes, and a replatform normally keeps the same domain and changes only paths, so that curve is the wrong construct and will overstate your risk. Argue the mechanism with your supplier instead of trading statistics. Ask to see the redirect map and the crawl it was built from before a cutover date is agreed.

Assume overrun and fund it deliberately rather than discovering it in month four. Bloor Research's work on data migration reports roughly 30 per cent average cost overrun, roughly 41 per cent average schedule slippage, and more than 80 per cent of projects running over time, over budget or both. Two honest caveats: that research covers enterprise data migration generally rather than e-commerce replatforming, and the widely circulated version does not carry a publication year we could confirm. It is still the only figure in this area that traces to a named research organisation rather than to a company selling migrations. Applied to a Neto move, the overrun is rarely in the product and customer export. That part is well-trodden and tool-supported. The cost lands in app selection, marketplace reconnection, POS hardware and staff retraining, the redirect map, and rebuilding whatever was custom. So get itemised quotes for those things specifically, and treat a migration quote that prices only the data transfer as pricing the easy part. Ask each supplier what happens to your eBay listings, your pick and pack process and your wholesale customers' logins on the morning after cutover. The quality of those three answers tells you more than the number at the bottom.

Stay on Neto if you lean on the bundled back office. Marketplace sync against a single inventory pool, native warehouse management with pick and pack, and B2B wholesale portals are the three that are expensive and fiddly to reassemble elsewhere. If your operation runs on those, the platform is doing real work for $789 a month and the case to leave is weak. Consider moving if you are essentially using Neto as a storefront, if you need a large app or developer market, or if your team cannot get the support it needs to keep trading. The API shape is a factor as well: Neto's single fixed endpoint with a header-selected action means most generic tooling needs custom handling, so each new integration costs more than it would on a mainstream REST API. If your plans involve connecting a lot of tools, that compounds. On support quality the evidence is thin and dated. Capterra rates the product 4.2 out of 5 from 72 reviews, which is a respectable score. The more interesting observation is that review flow has gone quiet: the most recent review we could see was November 2024, with the bulk clustered between 2018 and 2022. For a platform with roughly 1,800 detected live stores, near silence across 2025 and 2026 is an observation about review volume rather than proof of anything. Judge the support on your own tickets, over a month, before you spend anything on moving.

Is Neto being shut down? No. There is no announced end of life, Maropost publishes dated Neto release notes including one on 12 January 2026, and a 14-day free trial was open at the time of writing. Both "Neto by Maropost" and "Maropost Commerce Cloud" are live names for the same product. The merchant base is shrinking, which is a commercial signal, not a shutdown. Is Shopify cheaper than Neto? On subscription alone, usually. Shopify Advanced is $575 a month against Neto Professional at $789, both AUD. That flips once you add the apps replacing Neto's bundled marketplace sync, warehouse management and POS, and again if you keep a non-Shopify payment gateway and pay Shopify's third-party gateway fee of 2 per cent on Basic down to 0.2 per cent on Plus. Will migrating cost me search traffic? It can, and the mechanism is URL change rather than anything mysterious. Shopify forces `/products/` and `/collections/` path prefixes, so a one-to-one match with your Neto URLs is generally impossible and a full 301 redirect map is mandatory. No credible figure exists for traffic loss after a same-domain replatform; the widely quoted percentages are vendor research without methodology. Can I use Matrixify to migrate from Neto? Not as a Neto connector. Matrixify does not support Neto as a source. It is a Shopify-side bulk loader that works through spreadsheets, so you would export from Neto yourself and reshape the data into its template. Cart2Cart does name Neto to Shopify as a supported path, as do LitExtension and Next-Cart, and all three sell migrations. What will not come across? Stored card details never migrate, so saved cards and any recurring billing must be rebuilt with customers re-authorised. Anything built with plugins or custom code, including subscriptions, loyalty and product customisers, is rebuilt rather than moved. Tax rules and shipping zones are configuration and start fresh. How long does a Neto to Shopify migration take? Nobody without a commercial interest has published a defensible figure, so treat any timeline you are quoted as a sales estimate. For planning, Bloor Research reports roughly 41 per cent average schedule slippage on data migration projects generally, and more than 80 per cent running over time or budget. Fund a contingency and stage the cutover.