Moving From Neto (Maropost Commerce Cloud) to Shopify: What to Plan For

Most Neto stores are more than a website. The same control panel often runs eBay and Amazon listings, wholesale pricing, kits and an in-store POS. That is what makes a move to Shopify harder than copying products and customers across, and it is where the planning needs to go.

Below is what to plan for, in roughly the order it causes trouble.

First, the name

Neto and Maropost Commerce Cloud are the same platform. Maropost acquired Neto, and in July 2021 announced that the Neto ecommerce platform was now part of Maropost Commerce Cloud. Maropost markets it under that name, but its help centre still says Neto in many articles, and most merchants still call it Neto. We do too, below.

There is no one-click importer

Shopify’s free Store Migration app imports product and customer data from Square, WooCommerce, Etsy, Wix, Amazon, eBay, Clover and Lightspeed R/X. Neto is not on the list.

So the data comes out through Neto’s own export wizards, which produce CSV files of products, customers and sales orders. It goes into Shopify through Shopify’s CSV imports, or a bulk import app such as Matrixify, which handles products, customers, orders, redirects and B2B companies. Matrixify does not list Neto as a source, and its documented route for unlisted platforms is to export, convert the files to its template, and import.

That conversion is where the work is. Neto’s variations, kits, price groups and custom fields do not map one to one onto Shopify’s products, bundles and catalogues, so someone has to decide where each field lands before anything is imported.

Every URL changes, and Neto’s redirects stay behind

Neto lets you set a custom URL for any product, category or content page, and the product URL format can be configured for the whole store. So no two Neto stores have quite the same URL structure.

Shopify is the opposite. Products live under /products/ and collections under /collections/. You can edit the handle that follows, but Shopify treats those prefixes as fixed paths. Almost every product and category URL your store has will change, and each one needs a 301 redirect to its new address.

Shopify’s URL redirects accept a CSV import, with room for up to 100,000 redirects on standard plans and 20 million on Plus. The mechanics are easy. The hard part is the list:

• Your current URLs. Neto’s product export can include product URLs, which gives you a starting point. Add every URL Google has indexed, from Search Console, not just what is in the catalogue today.
• Your existing redirects. Neto creates a 301 automatically whenever a page or product URL changes, and keeps them in its 301 Redirects settings. Those do not come across. Old addresses that already redirect once inside Neto need pointing straight at the new Shopify page.

Get this right and rankings settle after reindexing. Get it wrong and years of search equity go on launch day. We treat the redirect map as a deliverable in our e-commerce migration work, not a task at the end.

Customer passwords do not move

Shopify’s help centre is direct about it: because passwords are encrypted outside Shopify, they cannot be migrated from another online store using a CSV. Customer records arrive without them.

Shopify’s new customer accounts soften this. Customers enter their email address and receive a one-time six-digit code, with no password needed. It is still worth an email before launch explaining the change, because a regular customer who cannot log in the way they used to will assume the site is broken.

Neto features that need a home on Shopify

Neto is sold as an all-in-one platform. On Shopify, each of these becomes a built-in feature, an app or custom work. List the ones you use, in business terms, before choosing anything.

eBay, Amazon and other marketplaces. Neto has integrations for eBay, Amazon Australia and Amazon US, and for local marketplaces such as Kogan and Bunnings. Shopify’s Marketplace Connect app connects a store to Amazon and eBay and manages listings, orders and inventory from the Shopify admin. Check that it covers the Amazon and eBay sites you sell on, and find a separate connector for any other marketplace.

Wholesale and price groups. Neto’s Customer Groups add-on shows different prices to different groups, alongside multi-level quantity pricing and payment terms. Shopify’s B2B features cover most of this. Since 2 April 2026 the Basic, Grow and Advanced plans include company profiles, payment terms, volume pricing and up to 3 active B2B catalogues. Unlimited catalogues and catalogues assigned directly to a company are Plus only. If you run more than three price groups, or price per customer, the plan decision belongs at the start of the project.

Kits and bundles. Neto kits are built from component SKUs, and standard kits can be listed on eBay as well as the webstore. Shopify Bundles is a free Shopify app for fixed bundles and multipacks, available on all plans. Its help page says bundles must use the Online Store or a headless storefront and other sales channels are unsupported, so a kit you sell on a marketplace today needs a plan of its own.

Point of sale. Neto POS is a paid add-on, available in Australia and New Zealand only. Shopify has its own POS, with card readers for Australia that take payments through Shopify Payments. If your shops run Retail Express instead, Maropost sells a Shopify Connector for it that syncs products, customers and orders, so the tills do not have to move with the website. It has gaps worth knowing about: order notes do not sync, which we covered in getting Shopify order notes into Retail Express.

Custom rules. Anything that needs custom pricing, shipping or checkout logic is built with Shopify Functions, either through a public app from the App Store or a custom app. The plan matters here: public apps containing Functions work on any plan, but custom apps containing them run only on Shopify Plus. Two 2026 changes matter too. Shopify Scripts stopped running on 30 June 2026, so any plan built on Scripts is out of date. And new custom apps are created in Shopify’s Dev Dashboard, not in the store admin.

Product structure may need rethinking

Shopify allows up to 2,048 variants per product, but only three options, such as size, colour and material. A Neto product that varies on more than three things needs restructuring, either into separate products or with some details moved into metafields. Decide early, because it affects filters, the storefront design and the URLs you are redirecting to.

Where to start

Before anyone quotes, gather four things:

1. Every Neto add-on and sales channel you use, and what each does for the business.
2. Your price groups, and any customers with their own pricing.
3. A full URL list: the Neto product export plus Search Console.
4. How stock moves between the website, marketplaces and shops.

Our e-commerce replatforming checklist covers the rest. Three of our developers hold Shopify certifications, and we plan migrations around URLs, data and integrations first and the storefront second. More on our Shopify development work, and our work as a Maropost partner.

---

Sources: Maropost: Neto is now part of Maropost Commerce Cloud, Maropost: update the URL for pages and products, Maropost: wholesale and B2B features, Shopify Store Migration app, Shopify Help Center: URL redirects, Shopify Help Center: importing customers, Shopify changelog: B2B features on non-Plus plans, Shopify Help Center: Shopify Bundles and Shopify developer changelog: Shopify Scripts deprecation.