Shopify migration agency

    NICCOS is a Shopify migration agency from Germany. We move stores from Shopware, Magento, OXID, WooCommerce and custom platforms to Shopify and Shopify Plus, for international brands entering the DACH market and DACH brands expanding abroad. You end up with a store whose data is reconciled against the old system, whose old URLs resolve and whose orders reach the ERP.
    Glass ampoules moving through a filling line in Heel's productionWoman sitting against a terracotta wall on gravel, wearing Groundies shoesHands opening a brown leather Gusti messenger bag and showing the inner compartmentsCoffee drink with milk foam and pistachios, with small bowls of pistachio creamSmiling man with cleansing foam on his face holding the face cleanser bottle.Two young women in white lying on a bed holding perfume bottles.Hand holding a vitamin D dropper bottle above a green quilted throw on a sofa.Hands inspecting a stone disc and lifting a block of wood from a stack in the Holzkern workshopThree young people in streetwear jackets and knitwear in front of the Eiffel TowerMan in a white T-shirt and black boxer briefs sitting on the floor of a loft by a window frontBack view of a green striped knit jumper with Deputy lettering and a dark beanie in front of a mountain lake and chaletModel turning in a dark green SMILODOX set of bra top and leggings against a white backgroundTable tennis bat with red rubber standing on a dark surface in a pool of lightFreshly roasted coffee beans pouring from a metal scoop

    Brands we work for

    MYCR7 logo
    CAT logo
    O'Neal logo
    FRITZ! logo
    Groundies logo
    Gusti Leder logo
    Smilodox logo
    Sirocco logo
    Olakala logo
    Deputy logo
    Bikemailorder logo
    Prepmymeal logo
    Freiluftkind logo
    Bloomingloft logo
    Heel logo
    We record every address with visitors or backlinks, in every language version, map each one to a page with matching content and test the redirects against staging before go-live.
    Every old URL has a target
    Products, customers, orders and discount codes run into Shopify several times as a trial and are reconciled with the legacy system after each run.
    Data is counted
    ERP, shipping, payment and tracking are connected and checked with test orders before the first customer buys in the new store.
    Orders reach the ERP

    What does a Shopify migration agency take responsibility for?

    A migration moves a store that is already selling. Customers have accounts, orders are open, and pages rank in several countries. A Shopify migration agency is responsible for four things during that move: which system owns which data afterwards, where every old URL points, how ERP, shipping and payment are connected, and what the sign-off is measured against. The theme is the smaller part of the work.

    We start with an inventory of the legacy system. It covers products with variants and attributes, customers, order history, discount codes, content, extensions and every address that search engines or other sites link to, in each language. From that list we derive the target model in Shopify with variants, metafields, collections and markets. The data then runs into a staging environment several times and is counted against the old system. If you want to know before the project which data and functions are critical, the migration audit comes first.

    NICCOS has been a Shopify Plus Partner since April 2022 and holds 19 reviews with a 5.0 rating in the Shopify Partner Directory. Eight of our 12 published case studies describe a move from another shop system: Shopware, Magento, OXID, PrestaShop and Plentymarkets. The page on our work as a Shopify Plus agency covers what Shopify Plus carries beyond the move.

    Replatform or rebuild: which one fits?

    Replatforming fits when your team spends its time on updates, hosting and extension compatibility while the business itself fits a standard. Rebuilding, or staying on the current system, is right when pricing logic, configuration or order processing form the core of the business and no platform can represent them.

    Your backlog is the test. If last year's tasks were mostly patches, server issues and repairs after updates, the architecture works against you. If they were functions customers find only in your store, the custom build is an asset. The common case sits between the two: the store moves to Shopify and the few special functions are built as a custom app. At Sirocco that was the club logic with login and loyalty discount, at Gusti Leder the engraving configurator. The page on Shopify app development describes how such extensions are built.

    A move without a goal becomes a relaunch with higher risk. Before the start we agree what should change afterwards: the time it takes to publish a campaign page, the number of systems in operation, or the launch in a new country. If it is open whether Shopify is the right platform, the platform comparison helps. If we advise against the move, we say so before the quote.

    Which platforms do we migrate from?

    We migrate from Shopware, Magento and Adobe Commerce, OXID, WooCommerce, PrestaShop, Plentymarkets and custom builds. The method stays the same and the pitfalls differ by platform, so each of the four most common source systems has its own page.

    OXID to Shopify covers modules, customer groups and language-specific SEO URLs. Groundies ran OXID for the US and Shopware internationally, and merged both onto one Shopify Plus codebase in 6 months, which cut cost by 50%. Shopware to Shopify deals with Shopping Experiences, properties and plugins. Magento to Shopify centres on attribute sets, store views and extensions. Sirocco brought 40,000+ customer records with their order history from Magento. WooCommerce to Shopify covers plugins, WordPress content and permalinks.

    Not every migration replaces the legacy system completely. Hairshop Pro moved from Plentymarkets to Shopify Plus and kept Plentymarkets as its PIM. An interface synchronises product data, stock, prices and orders between the two. The store was live after 3 months, with a 35% higher conversion rate and a 20% higher average order value from bundles and cart upsells. The page on system integration describes how such connections are built.

    What has to be signed off before go-live?

    A migration is signed off after four checks. The data matches the legacy system. Every old URL reaches a target with matching content. Test orders arrive in ERP and shipping. Tracking measures the same events as before. We run these checks in staging before the cutover date is fixed.

    Kanela shows what that means for a large, multilingual catalogue. The Swiss online pharmacy ran PrestaShop with more than 40,000 products, an ERP and three marketplaces. We reconciled and transferred products, categories, stock, customers, bonus balances, orders and reviews, analysed 337,891 product-category relationships, and set up and read back 147,753 legacy URL mappings from four language versions. The live integrations stayed in place until each replacement was verified. Today Shopify Plus connects the catalogue with the ERP and the marketplaces Zur Rose, Galaxus and Manor.

    The cutover follows a plan with a content freeze, a final data extract, the DNS switch and a way back. It does not have to be one date for all countries. Groundies launched in stages, the US first and international 60 days later. BlumeIdeal moved without a hard cutover, and the DNS switch took about 5 minutes. Gusti Leder went live after 8 weeks with Shopify Markets for DACH, France and the UK.

    Nobody can promise unchanged rankings in a platform change. Search engines have to assign the new addresses first, and positions move during that time. We are responsible for a complete redirect list and for fixing the 404 errors that appear after launch. The page on Shopify SEO describes the work on visibility afterwards, and the page on tracking setups the measurement.

    Which source systems have their own page?

    The method is the same for every platform. Data model, URL structure and extensions differ. For these source systems we describe the specifics in detail.

    • Shopware to Shopify

      Shopware 5 and 6: Shopping Experiences, properties, plugins and the Rule Builder are rebuilt in Shopify structures.

      Shopware to Shopify
    • Magento to Shopify

      Magento and Adobe Commerce: attribute sets, configurable products, store views and extensions.

      Magento to Shopify
    • WooCommerce to Shopify

      WooCommerce on WordPress: plugins, blog content, permalinks and order data held in the WordPress database.

      WooCommerce to Shopify
    • OXID to Shopify

      OXID eShop: modules, customer groups, scale prices and language-specific SEO URLs.

      OXID to Shopify
    • Salesforce Commerce Cloud to Shopify

      Cartridges, promotions and order logic from SFCC are assessed and replaced one by one.

      Salesforce Commerce Cloud to Shopify
    • Oracle ATG to Shopify

      Replacing a legacy system in which catalogue and pricing logic are tightly interwoven.

      Oracle ATG to Shopify
    • Adobe Experience Manager to Shopify

      Content and commerce are separated while editorial workflows stay in place.

      Adobe Experience Manager to Shopify
    • Custom build to Shopify

      Custom platforms whose documentation exists only in the code.

      Custom build to Shopify
    • Headless to Shopify theme

      The route back to a theme when running the headless frontend costs more than it returns.

      Headless to Shopify theme
    • Global-e to Shopify Markets

      International selling with markets, prices and duties inside Shopify itself.

      Global-e to Shopify Markets
    • POS migration

      Store tills move to Shopify POS with inventory, customers and returns.

      POS migration

    Where do Shopify migrations fail?

    • Redirects are written last

      The list is built from a spreadsheet shortly before go-live. Filter, image, campaign and language URLs are missing from it, and the damage appears weeks later in Search Console.

    • Nobody counts the data

      Variants, customer groups, discount codes and order history are imported and never counted against the legacy system. Customer service finds the gaps first.

    • Integrations arrive in the final sprint

      ERP, warehouse and payment providers are connected shortly before go-live. By then nobody tests cancellations, partial shipments and returns.

    When is moving to Shopify worth it, and when is it not?

    • Updates block the business

      Every platform update is a project of its own. Extensions break, and new features wait for the next maintenance window.

    • Hosting and security tie up budget

      Servers, patches and traffic peaks cost money and attention that are missing from assortment and marketing.

    • Every new market is a project

      New countries, B2B or retail stores each need their own extension on the legacy system. On Shopify, Markets, B2B and POS are part of the platform.

    • The custom logic is the business model

      If configuration, pricing logic or contract models form the core, we first check whether Shopify can carry it. If it cannot, we say so.

    • There is no goal beyond a newer system

      A move without a measurable goal becomes a relaunch with higher risk. In that case we first settle what is supposed to change.

    • The data model is unclear

      If nobody knows which system owns which data, the work starts with an audit and the import waits.

    How does a Shopify migration run?

    1. Inventory and data model

      We record systems, data flows, URLs and custom logic and decide point by point what moves to Shopify, what is replaced and what is dropped.

    2. URL plan

      Relevant URLs, redirects, canonicals and hreflang are fixed before the first template is built.

    3. Trial migration

      Data runs into a staging environment several times and is counted against the legacy system: products, customers, orders, discount codes.

    4. Integrations and tests

      ERP, PIM, shipping, payment and tracking are connected and checked with test orders, including cancellations and returns.

    5. Cutover

      An agreed plan covers the content freeze, the final data extract, the DNS switch and the way back.

    6. After go-live

      We watch crawling, redirects, order flow and error logs and fix what shows up in live operation.

    • Road cyclist backlit on a mountain roadBikemailorder
    • Brown leather Groundies Chelsea boots stepping into frame on a concrete floorGroundies
    • Green Freiluftkind barefoot shoes on rocks in the woodsFreiluftkind

    What is part of every migration?

    • Tracking rebuilt

      Events, consent and server-side signals are built again in Shopify. They cannot be copied from the legacy system.

    • Customer accounts carried over

      Customers move with their consent status and are invited to activate their account.

    • Legal texts and mandatory information

      Imprint, right of withdrawal, unit prices and delivery information sit where EU and German law expects them in the purchase flow.

    • Handover to your team

      Your team is trained in the new admin and maintains products, pages and promotions itself afterwards.

    What did migrations change for our clients?

    The figures appear in this form in the case studies. Each one belongs to a named project.

    Is now the right time to move to Shopify?

    Then a lot speaks for the move

    • The platform is reaching end of life

      The source system no longer receives updates, or the next major update would amount to a rebuild.

    • Development has turned into maintenance

      A large share of the budget goes into patches, hosting and conflicts between extensions. Little is left for new features.

    • New markets are planned

      New countries, currencies, B2B or retail stores are coming and would each be a project of its own on the old platform.

    • Your team wants to work on its own

      Marketing and e-commerce want to maintain pages, campaigns and products without waiting for a developer.

    Then something else comes first

    • You are already on Shopify

      If the question is a new theme or new features, you do not need a platform move. A relaunch is the right frame.

      To Shopify development
    • The decision is still open

      If it is not settled whether Shopify fits, we first clarify requirements and alternatives.

      To Shopify consulting
    • The problem is the integration

      If the store runs but data does not flow to the ERP or PIM, the work starts at the interface and a move is the wrong lever.

      To system integration

    How can we approach your migration?

    You need clarity on scope and risks first, want to hand over the whole move, or are looking for help after go-live. That gives three formats.

    Results from client projects

    Every figure appears in the case study, where you can verify it.

    View all projects

    Brands we build for on Shopify.

    Groundies, MYCR7 and Gusti Leder are three of twelve projects we have published with starting point, delivery and result.

    Frequently asked questions about working with a Shopify migration agency

    Can a Shopify migration agency in Germany handle a multi-country store?

    Yes. Groundies ran OXID for the US and Shopware for its international markets. Both were merged onto one Shopify Plus codebase. Gusti Leder sells to DACH, France and the UK through Shopify Markets. At Kanela, 147,753 URL mappings from four language versions were set up and read back.

    What changes when we start selling into Germany after the migration?

    Price display, legal texts and payment methods. German law requires unit prices and, for price reductions, the lowest prior price under the Price Indication Ordinance (PAngV). For that we publish our own app, Best Price Indicator (PAngV), in the Shopify App Store. Imprint, right of withdrawal and delivery information belong in the purchase flow.

    How long did published migrations take?

    From our case studies: Gusti Leder went live after 8 weeks, BlumeIdeal after 50 days, Sirocco after 12 weeks, Mintkind after 90 days and Hairshop Pro after 3 months. Groundies merged two legacy systems and took 6 months. We give a statement for your store after the inventory.

    Will rankings hold in every language after the move?

    Google evaluates the new store again, and positions move in the first weeks. Lasting losses come from missing redirects, thinner target pages and catch-all redirects to the homepage. We map every URL with visitors or backlinks in each language version, test the list before go-live and watch indexing afterwards. No platform change comes with a guarantee.

    Do we need Shopify Plus for an international setup?

    Not in every case. Shopify Plus fits when you run several markets or stores, want to extend the checkout, or need B2B with company catalogues and payment terms. The page on our Shopify Plus agency work lists the criteria. We check the question against your requirements during the inventory.

    Can the legacy system stay in place for part of the work?

    Yes. Hairshop Pro moved its storefront from Plentymarkets to Shopify Plus and kept Plentymarkets as its PIM. An interface synchronises product data, stock, prices and orders. At Kanela the live marketplace connections stayed in place until each replacement was verified.

    Talk to a Shopify migration agency

    Tell us which platform you are on, which systems are attached and which countries you sell to. We tell you which data, functions and URLs become critical in the move.

    NICCOS

    The page could not be loaded.

    Please reload the page. If an update has just gone live, this will load the latest version.