Elogic Commerce migrates stores to Medusa.js from Magento 2, Adobe Commerce, Shopify, WooCommerce and custom platforms. Elogic Commerce has worked with Magento since 2009 and moved Manutan from a monolith to Medusa.js with a sequenced cutover. Products, customers, orders and URLs move, and search rankings stay protected.
A move to Medusa.js is a replatform, not a data copy. Elogic Commerce maps every extension, integration and URL before the build starts.
Migrations from
Adobe Commerce
Shopify Plus
WooCommerce
Medusa.js 1.x
Custom platforms
Since 2009 Elogic Commerce works with Magento
64% lower API response time for Manutan on Medusa.js
500+ commerce projects delivered
5.0 Clutch rating from 64 reviews
ISO 9001 and 27001-aligned processes for quality and security management.
Migration paths to Medusa.js
Elogic Commerce migrates six types of source platform to Medusa.js. Each path has its own reasons to move and its own effort drivers.
Migration paths to Medusa.js, as planned by Elogic Commerce
| Source platform | Typical reasons to move | Main effort drivers |
|---|---|---|
| Magento 2 and Adobe Commerce | License or hosting cost, slow releases, monolith limits | Custom extensions, EAV attributes, B2B features, URL rewrites |
| Shopify and Shopify Plus | Platform limits on custom logic, app costs, need for code ownership | Logic held in apps, checkout customizations, metafields |
| WooCommerce | Performance at scale, plugin conflicts, B2B limits | Plugin logic, inconsistent product data, WordPress content |
| Separate B2B and B2C stores | Duplicate catalogs, customers and integrations | Merging catalogs, mapping prices to price lists per sales channel |
| Custom or legacy platform | Tightly coupled logic, slow change, no API layer | Logic hidden in old code and direct ERP calls |
| Medusa.js 1.x | Access to version 2 modules, workflows and new features | Custom services and plugins need a new implementation |
Magento to Medusa.js migration: the data and feature map
Elogic Commerce has worked with Magento since 2009 and received the Magento Community Engineering Award in 2019. That knowledge matters because most Magento stores carry years of extensions and custom code.
Magento 2 and Adobe Commerce to Medusa.js map, as used by Elogic Commerce
| Magento 2 or Adobe Commerce | Medusa.js equivalent | Migration note |
|---|---|---|
| Simple and configurable products | Product Module: products, options and variants | Attribute sets become product options, fields or custom data models |
| EAV attributes | Product fields, metadata and custom data models | Elogic Commerce decides which attributes drive filters, prices or integrations |
| Bundle and kit products | Inventory kits on product variants | Each bundle type is checked in the migration audit |
| Categories | Product categories | Keep the URL structure or add redirects |
| Customer groups | Customer groups | Used for price lists and promotions |
| Tier prices and catalog price rules | Pricing Module: price lists and price rules | Contract prices can come from the ERP instead |
| Cart price rules and coupons | Promotion Module | Rules are rebuilt and tested against old orders |
| Multi-Source Inventory sources | Inventory Module: stock locations | Stock locations link to sales channels |
| Websites, stores and store views | Regions, sales channels and the Translation Module (beta) | One backend can serve several markets and storefronts |
| Adobe Commerce B2B: companies, shared catalogs, negotiable quotes, requisition lists, purchase orders | B2B Starter features and custom modules | Each B2B feature is planned in discovery |
| Orders and order history | Order Module | History is imported for customer accounts and reports |
| CMS pages and blocks | A headless CMS | Medusa.js does not manage editorial content |
| URL rewrites | Storefront routes and a 301 redirect map | Every changed URL gets a 301 redirect |
| Extensions | Modules, workflows or third-party services | Each extension gets a rebuild, replace or remove decision |
For Shopify, the same map starts from apps, metafields and Shopify Functions. For WooCommerce, it starts from plugins and product data quality.
How Elogic Commerce migrates a store to Medusa.js
Elogic Commerce runs every Medusa.js migration in seven steps. PMP-certified project managers lead each step on a PMI-aligned method.
How Elogic Commerce protects search rankings
Elogic Commerce treats search traffic as a migration deliverable. These checks run on every Medusa.js migration.
- A URL inventory from the crawl, analytics and Google Search Console.
- A 301 redirect for every URL that changes.
- Titles, meta descriptions, canonical tags and structured data carried over or improved.
- Internal links and XML sitemaps updated on launch day.
- A crawl comparison of the old and the new store before launch.
- Monitoring of rankings, 404 errors and organic traffic after launch.
Medusa.js 1.x to 2.x upgrade
Elogic Commerce upgrades Medusa.js 1.x projects to 2.x. Medusa.js 2.0 changed the architecture, so version 1 customizations need a new implementation.
Medusa.js 1.x to 2.x, as planned by Elogic Commerce
| Medusa.js 1.x | Medusa.js 2.x |
|---|---|
| Custom services | Modules with data models |
| Business logic inside services | Workflows with retries and rollback |
| Custom API endpoints | API routes |
| Event subscribers | Subscribers that run workflows |
| Plugins | Plugins and modules |
| Tightly linked core data | Decoupled modules joined by module links |
Migration risks and how Elogic Commerce controls them
Elogic Commerce plans each migration around six risks. Each risk has a named control.
Medusa.js migration risks and controls by Elogic Commerce
| Risk | Control |
|---|---|
| Lost search traffic | 301 redirect map, crawl comparison and monitoring after launch |
| Data errors | Test migrations with reconciliation reports |
| Missing features from extensions or apps | Feature inventory and mapping before the build |
| ERP sync failures | Integration tests under load before the cutover |
| Downtime during the cutover | A sequenced cutover by market, channel or function |
| Scope growth | A written scope after the audit and change control |
Cost and timeline of a Medusa.js migration
Elogic Commerce gives a written estimate after the migration audit. Rates are $50 to $99 per hour, on a fixed-price or time-and-materials basis.
- The number of extensions, apps or plugins to rebuild or replace.
- The number of integrations and the direction of each data flow.
- The volume and quality of product, customer and order data.
- The number of markets, storefronts and sales channels.
- Custom features such as B2B rules, marketplaces or subscriptions.
- The number of URLs and their search traffic.
For platform costs after the move, see Medusa.js pricing in 2026. For the proof, read the Manutan case study: a sequenced move from a monolith to Medusa.js with SAP S/4HANA.
Plan your Medusa.js migration with Elogic Commerce
Tell Elogic Commerce about your current platform, your integrations and your markets. A solution architect replies within one working day.
Ready to chat?
Send your requirements. We reply within one working day with a fit assessment and next steps.
Frequently asked questions
Yes. Elogic Commerce migrates Magento 2 and Adobe Commerce stores to Medusa.js. Products, customers, orders, CMS content and URLs move, and each extension maps to a module, a workflow or a third-party service.
Yes. Elogic Commerce migrates WooCommerce stores to Medusa.js. The team cleans and normalizes product data, replaces plugin logic and moves customers, orders and URLs.
Elogic Commerce sets the timeline after the migration audit. The main drivers are the number of extensions and integrations, the data volume and the number of markets. Manutan moved in a multi-phase implementation with a sequenced cutover.
Yes. Elogic Commerce merges separate B2B and B2C stores into one Medusa.js backend. Products move to one catalog, and sales channels and price lists keep the assortments and prices apart.
Yes. Elogic Commerce migrates Shopify and Shopify Plus stores to Medusa.js. The team lists each app and rebuilds, replaces or removes its function, then moves products, customers, orders and URLs.
Elogic Commerce protects rankings with a 301 redirect map, a crawl comparison before and after launch, and monitoring after launch. Some movement in rankings is normal in the first weeks after any replatform.
Elogic Commerce plans a sequenced cutover by market, channel or function, so sales continue during the move. Each cutover step starts only after the data reconciles and the ERP sync is stable under load.
Yes. Elogic Commerce upgrades Medusa.js 1.x projects to 2.x. The team re-implements custom services as version 2 modules and workflows, then migrates the data.
More from the Elogic Commerce Medusa.js series
Elogic Commerce publishes these Medusa.js services and guides as one series. Each page answers one question in depth.
Service
Service
Service
Medusa.js migration services