OXID to Shopify migration

    We move OXID eShop stores to Shopify and Shopify Plus: articles with variants, customer groups, scale prices, SEO URLs and the ERP connection. It is for international teams that inherited an OXID store for the German-speaking market, and for DACH merchants expanding abroad. You end up with a store your team maintains, in which every old address reaches its target.
    Motocross rider in white O'Neal gear whipping the bike mid-air and riding through red dustGlass teapot, a carafe of ice cubes and two glasses of iced tea with mint on a wooden trayBrown leather Groundies Chelsea boots stepping into frame on a concrete floorPregnant woman holding a Mintkind “week 30” card to her bellyHands opening a brown leather Gusti messenger bag and showing the inner compartmentsLinen-bound baby album with an embossed animal wreath and the title Mein erstes Jahr on a wooden tableLight-coloured Labrador with a braided collar in profile looking across a sunny meadowWoman in profile with voluminous blonde curls, a hand spraying hair spray from above.Road cyclist backlit on a mountain roadSilver tube of Liquid Glass Skin Mask and a silicone brush lying in clear gel on a pink surfaceMountain biker in a red long-sleeve jersey and white helmet riding through the forest with the front wheel liftedBlack maleup products with a concealer palette, dispensers and a towel against a dark backgroundHands bending and rolling a blue Freiluftkind insole against a mint-green backgroundTwo young women in white lying on a bed holding perfume bottles.

    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

    What does an OXID to Shopify migration involve?

    OXID eShop is a German shop system, and most OXID stores were built for the German-speaking market by German agencies. Teams outside that market often find a store whose behaviour is defined by modules nobody on the team wrote. An OXID to Shopify migration therefore starts with reading code. Modules overload the classes of the core and change cart, pricing and order flow wherever they need to.

    That review produces a list of functions. Some are dropped because nobody uses them any more. Some are standard in Shopify, such as discount codes, quantity discounts or managing several languages. Some are covered by an app. The rest is built as a custom extension. The page on our work as a Shopify migration agency describes the method for every source system. If you want to know before the project which modules 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. Among our 13 published case studies, one is a move off OXID: Groundies, whose US store ran on OXID.

    How did Groundies move its US store off OXID?

    Groundies sells barefoot shoes and ran two separate systems: OXID for the US market and Shopware for its international markets. The result was duplicated operations, rising maintenance cost and long lead times for new storefronts and campaigns. In 6 months we merged both systems onto one shared Shopify Plus codebase. The theme was rebuilt, and Zendesk, Workato for warehouse and fulfilment, 8Returns for returns and Pathway Solutions for accounting were connected, along with Reviews.io for reviews and Klar for analytics.

    The US store, which had run on OXID, went live first. 100+ orders came in within 3 days of the US launch, and the international launch followed 60 days later. The consolidation cut cost by 50%, and the time from briefing to live is about three times shorter than before. Caro Kampnick, E-Commerce Manager at Groundies, put it this way: “That was the calmest launch we’ve ever had.”

    A staged launch is one of several routes. Starting with one market keeps the first cutover small and lets the team check order flow, returns and accounting with real orders before the other countries follow. The page on Shopify internationalisation covers what selling into several countries involves.

    How do OXID articles, variants and prices translate to Shopify?

    OXID holds variants as separate articles under a parent article and also has selection lists, which represent a choice without its own stock. Shopify has products with variants and options. Before the export we decide per article what becomes a variant with its own stock and what travels as a property of the order line. Attributes become metafields and filters, and categories become collections.

    Prices are the second area where OXID projects need time. A, B and C prices, scale prices and discounts per customer group overlap. Before the import we record which price applies to which customer, and map the result to company profiles and catalogues on Shopify Plus. The page on Shopify B2B describes what that includes.

    German law adds requirements that an international team may not expect. On price reductions, the lowest prior price has to be shown under the Price Indication Ordinance (PAngV). Our own app, Best Price Indicator (PAngV), in the Shopify App Store covers that. Unit prices, delivery information and legal texts move to the places where they have to appear in the purchase flow.

    How do OXID SEO URLs redirect in every language?

    OXID builds SEO URLs from the category path and the article name, per language and usually with the .html suffix. The addresses sit in the database together with older entries that stay reachable after renaming. Shopify sets fixed paths for products, collections and pages. Almost every address changes in the move.

    We extract the stored SEO URLs from the database and add addresses from Search Console, analytics and our own crawl. That surfaces addresses with parameters which come from older versions and are still linked. Articles assigned to several categories in OXID often have several addresses, and all of them point to the same product afterwards. Every address gets exactly one target through a 301, with the same content in the same language.

    We test the list against staging before go-live. After launch we watch indexing and fix 404 errors. Nobody can seriously promise unchanged rankings in a platform change. The page on Shopify SEO describes the work on visibility afterwards.

    How do customers, orders and the ERP connection move?

    Customer accounts, addresses and orders move with the original order number, so that customer service and accounting can find old transactions. Passwords cannot be transferred. Customers receive an invitation to activate their account, and newsletter consent moves as its own attribute. Many OXID stores exchange data with the ERP through files or custom modules. In Shopify that connection is rebuilt through a connector, middleware or a custom app, and it is signed off when test orders, cancellations and returns arrive in the ERP. The page on system integration explains the structure.

    If your business depends on changes that can only be made in open code, we advise against the move. The comparison Shopify vs. OXID sets the two platforms side by side.

    Why does an OXID store need so much maintenance?

    OXID eShop is used mainly in German-speaking countries and can be customised deeply through modules. That freedom has consequences for operations. We hear four of them in almost every first conversation.

    • Updates turn into projects

      Modules overload classes of the core. After every update someone has to check whether they still run together.

    • The knowledge sits with a few people

      Changes require knowledge of the OXID core and of your own modules. If one developer is unavailable, development stops.

    • Hosting is your responsibility

      Servers, security and traffic peaks sit with you or your service provider.

    • New functions need development

      Whatever does not exist as a module is built. Campaign pages and new countries wait for an open slot.

    When is moving off OXID worth it?

    • OXID developers are hard to find or fully booked

    • Updates are postponed because modules stop working afterwards

    • Custom modules are to be replaced by standard functions and apps

    • The OXID store serves one market while other markets run on a different system

    • New countries, currencies or languages are planned

    • Your team wants to maintain content and promotions without a developer

    What is specific to an OXID migration?

    • Modules

      OXID modules reach into the core. Each module is traced back to its function and then replaced, rebuilt or dropped.

    • Articles and variants

      Variants, selection lists and attributes follow their own logic in OXID. Before the export it is settled what becomes a variant, a metafield or a filter in Shopify.

    • Customer groups and prices

      Customer groups, scale prices and net price display are mapped to company profiles and catalogues on Shopify Plus and checked with their own test orders.

    What do we check on OXID URLs and redirects?

    OXID generates SEO URLs per language and stores them in the database. Older addresses with parameters are often still linked as well. We sign off these four points before and after go-live. That limits fluctuation in the first weeks. Nobody can rule it out.

    • SEO table

      An extract of all stored SEO URLs from OXID, per language and including the entries from the URL history

    • Parameter URLs

      Addresses with parameters from older versions are recorded when they have visitors or backlinks

    • 301 redirects

      Every old address points to exactly one target with matching content in Shopify, with no catch-all redirect to the homepage

    • Indexing

      Indexing report and crawl statistics in Google Search Console after go-live

    How do we protect data and rankings when you leave OXID?

    1. Inventory the modules

      First we record which modules hang on the OXID core and which of them are still used. For every module in use, the function it performs is then on record.

    2. Classify the custom logic

      We separate price rules, approvals and custom fields in the order flow into business-critical and historically grown. That includes the question of whether the ERP offers a dependable interface.

    3. Record the indexed addresses

      The list is built from the OXID SEO table, Search Console, analytics and our own crawl. The sitemap alone is not enough because addresses with parameters are missing from it.

    4. Map every address to a target

      Every indexed address gets exactly one matching target in the new structure, in the same language. We set no catch-all redirects to the homepage.

    5. Review after the cutover

      After go-live we watch indexing reports and positions in Google Search Console and trace outliers back to missing targets.

    • Motocross rider in an O'Neal goggle and helmet, then airborne over a crestO'Neal
    • Woman sitting against a terracotta wall on gravel, wearing Groundies shoesGroundies
    • Three Vitabay jars on a stone table in front of a green sofa.Vitabay
    cost at Groundies from consolidating OXID and Shopware
    -50%
    faster from briefing to live at Groundies
    ~3×
    orders at Groundies within 3 days of the US launch
    100+
    project duration at Groundies, merging OXID and Shopware
    6 months

    Is moving off OXID your next step right now?

    Then you are starting in the right place

    • OXID developers are hard to get

      Changes require knowledge of the core and of your modules. The people who have it are booked, and your store waits.

    • Updates are postponed

      Every update requires a check of all modules. So it is put off until the backlog becomes a risk.

    • Custom modules should go

      Modules built over years reach deep into the system. Shopify covers much of it in the standard or through apps.

    • Your team should run the store itself

      You want to change products, content and promotions without a developer and hand over server operation.

    Then something else will do more for you

    • The platform decision is still open

      As long as it is not settled whether Shopify is the right target platform, a migration project is premature. The platform decision comes first.

      To the platform comparison
    • The project risks are unclear

      You want to move but do not know which modules, customer groups and URLs become critical in the process. Then the review comes before the project.

      To the migration audit
    • You are already on Shopify

      If the theme, structure or design no longer holds up, you do not need a platform move. The work is a rebuild on the platform you are already on.

      To Shopify development

    How can we work together on the OXID migration?

    You want modules and data clarified first, have the move carried out, or keep optimising afterwards. 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 thirteen projects we have published with starting point, delivery and result.

    Frequently asked questions about OXID to Shopify migration

    We took over an OXID store without documentation. Where do we start?

    With the modules. We read which modules overload the OXID core, which of them are still used and which function each one performs. That gives you a list of what moves, what is replaced and what is dropped before any budget is committed to the build.

    Can an OXID store for one country be merged with other stores?

    Yes. Groundies ran OXID for the US and Shopware for its international markets. Both were merged onto one shared Shopify Plus codebase and launched in stages, the US first and international 60 days later. The consolidation cut cost by 50%.

    Which German-market requirements have to survive the move?

    Price display under the German Price Indication Ordinance (PAngV), unit prices, legal texts in the purchase flow, the payment methods your buyers use, and the ERP connection. For PAngV we publish our own app, Best Price Indicator (PAngV), in the Shopify App Store.

    How are OXID customer groups and scale prices handled?

    On Shopify Plus, through company profiles, catalogues with their own price lists, quantity breaks and payment terms. B2B test orders run before go-live. If quotes and multi-step approvals are the regular route to an order, we clarify that before the project.

    How do OXID URLs redirect?

    OXID stores SEO URLs per language in the database, usually with the category path and the .html suffix. We extract those entries, add addresses from Search Console, analytics and our own crawl, and map each one to a target in Shopify in the same language. The list is tested against staging before go-live.

    Will we lose rankings when we leave OXID?

    A platform change alters the address scheme, and positions move for a while afterwards. Lasting losses come from missing redirects, thinner target pages and catch-all redirects to the homepage. We are responsible for every indexed address getting exactly one matching target. There is no guarantee of unchanged rankings.

    What happens to subshops in OXID Enterprise Edition?

    Depending on assortment and pricing logic, subshops become markets within one store or separate stores on Shopify Plus. Rights and roles from OXID are transferred to staff accounts in Shopify. The decision is made during the inventory because it defines the URL mapping.

    Discuss your OXID to Shopify migration

    We look at your OXID store and tell you which modules, customer groups and URLs become critical in the move. The first assessment is free and gives you an initial evaluation, not a full audit or a worked-out concept.

    NICCOS

    The page could not be loaded.

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