Magento to Shopify migration
Move a Magento or Adobe Commerce store into Shopify with the catalog, pricing rules, and integrations reviewed before the destination is built. Norml maps the agreed records and rebuilds the storefront around verified Shopify behavior. The source edition and its custom modules matter, especially when several store views or business-customer workflows share one installation.
A few clients we’ve worked with
What we do
Plan a Magento or Adobe Commerce move to Shopify with attribute mapping, store-view review, order-data checks, and launch reconciliation.
What the migration covers
We record the source edition and version first. Magento Open Source and Adobe Commerce installations can have different features, extensions, and data that affect the migration.
- Solution
- Migrations
- Current platform
- Adobe Commerce / Magento
- Destination
- Shopify
- Attribute sets and product typesWe inspect attribute sets, configurable products, bundles, grouped items, and custom options. Product data is mapped into Shopify variants, metafields, or an agreed app-based representation. Samples include the products with conditional choices or price behavior that a flat catalog export might conceal.01
- Store views and selling rulesLanguages, currencies, domains, customer groups, catalog rules, and business pricing need a destination design. We establish which behavior Shopify must reproduce and test it against the selected plan and apps. A store-view label in an export does not recreate its storefront or permissions.02
- Customers, orders and connectionsWe agree the customer and order history to retain and reconcile source identifiers with imported records. Accounting, inventory, fulfillment, and other custom connections get their own field and ownership mapping. Historical imports must not generate new shipments or duplicate customer messages.03
- Storefront, URLs and final transferThe Shopify storefront is built around the approved catalog and buying flow. We map old product and category URLs, check content pages, and plan the final order and inventory updates. Pending orders and returns need an assigned operating home during the transition.04
Client reviews
“Norml Studio's professionalism and responsiveness were impressive.”
“They were proactive in suggesting improvements we hadn't considered.”
“They delivered what they said they would, on time.”
“They focused on how to make our daily operations easier, not just on building features for the sake of it.”
“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”
“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”
What we need before the move
- Edition, modules and examplesProvide authorized access, the Magento or Adobe Commerce version, module inventory, available exports, and domain details. Include examples of configurable products, custom pricing, business accounts, and integrations that affect checkout or fulfillment.01
- Features that need separate decisionsSubscriptions, payment tokens, credit balances, customer passwords, and custom B2B behavior are not assumed portable. We document supported replacements and required customer actions. Destination fees and plan requirements are identified for approval before implementation.02
How we prepare the move
- [Audit the source model]Step 01
Map product attributes, store views, customer groups, price rules, and custom module data. Define the retained record scope and the behavior each destination component must support.
- [Prove difficult cases]Step 02
Import representative records and demonstrate the required product choices, pricing, customer access, and order handling. Resolve differences before building the remaining storefront and transferring the full catalog.
- [Reconcile and cut over]Step 03
Test the agreed purchase and operational paths, compare final data changes, and prepare redirects and domain settings. Verify the public store and document where staff handle old orders, returns, and customer questions.
The people who do this work.
Meet the whole teamNo account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedRelated services.
From the Norml blog.
Questions about the migration
Can custom attributes and store views move?
Attribute values can be mapped when they are available in the source data. Their destination representation needs to be defined. Store views also control storefront behavior, language, or scope, so they require more than copying a field value.
Which checkout and pricing features need replacement?
We review custom modules, customer-specific pricing, catalog rules, payment behavior, and checkout fields. The supported Shopify approach depends on the required workflow and chosen plan. Material differences are demonstrated before launch.
Is this the same for Magento Open Source and Adobe Commerce?
The migration starts by identifying the edition, version, and installed extensions. The page covers both assessment routes, but it does not imply identical source features or a single importer that reproduces every setup.
Plan your Adobe Commerce / Magento migration
Share your current website, the features you rely on, and what needs to change. We will review the Shopify requirements and identify the content, rebuild work, and launch checks your move needs.