Medusa released a WooCommerce migration tool that uses an AI agent to transfer store data — products, variants, pricing, images, inventory, categories, and tags — from a WooCommerce installation into a Medusa project. The process runs through Medusa's MCP server and requires little more than a prompt to start. What previously required custom scripts, manual data mapping, and days of engineering work can now be handled in a single agent-driven workflow.
For WooCommerce merchants who have been considering the move but waiting for the migration story to mature, this is the release that removes the last significant technical barrier. But data migration is only part of the case. The platform architecture that WooCommerce runs on has structural limitations that no migration tool fixes — and the payment layer, which most WooCommerce merchants have never had real control over, is where the long-term value of the switch actually lives.
Why WooCommerce Merchants Are Looking for an Exit
WooCommerce was built as a commerce plugin on top of WordPress — a twenty-year-old CMS that was designed for publishing, not transaction processing. Product catalogs live in WordPress posts. Business logic is implemented through hooks and filters. Custom functionality requires plugins, and plugins require maintenance, compatibility testing, and the ongoing operational overhead of a stack that was never purpose-built for ecommerce.
For merchants who started on WooCommerce and grew into it, the friction is familiar: a payment plugin that conflicts with a shipping plugin, a theme update that breaks checkout, a security patch that requires four hours of testing. The platform works — until it doesn't, and when it doesn't, the root cause is almost always architectural.
The payment situation compounds it. Most WooCommerce merchants run on WooPayments — which is built on Stripe — or on the Stripe plugin directly. That means the same category restrictions, the same risk filters, the same automated account reviews, and the same approval logic that Stripe applies to every business regardless of industry, volume, or relationship. A merchant who has been processing successfully for three years is one algorithm update away from a hold.
What the Migration Tool Actually Transfers
Medusa's migration tool connects to WooCommerce through its REST API and transfers the full product catalog: products, variants, pricing, product options, images, inventory levels, and category and tag structures. Images are re-hosted to Medusa's storage rather than referencing the original WordPress CDN. Category trees are migrated in full, including WooCommerce's global attribute system mapped to Medusa's options format.
The tool supports two approaches. The custom API method is idempotent and resumable — the migration can be triggered via CLI, scheduled, or run from the admin, and it picks up where it left off if interrupted. This is the right path for merchants with large catalogs, complex variant structures, or inventory that needs to transfer accurately. The CSV method converts a WooCommerce product export into Medusa's import format without requiring API credentials — faster for straightforward migrations, but it does not include inventory quantities and keeps images as external URLs.
Orders and customers can be added to the migration scope through extended configuration. The AI agent asks which approach to use if it is not specified, builds the necessary flows, executes the import, and verifies the migrated data before reporting any gaps.
What Medusa Solves That WooCommerce Cannot
Medusa is a modern Node.js commerce backend built around modules, workflows, and a documented REST API. The architecture was designed for ecommerce from the ground up — not adapted from a publishing platform. Custom business logic lives in workflows, not WordPress hooks. Integrations connect through a headless API, not a plugin marketplace where compatibility is a constant variable. The platform is AI-native, with an MCP server, AI-friendly CLI, and the kind of structured extensibility that does not require workarounds.
Medusa Cloud adds managed hosting with preview environments, monitoring, and scaling — while keeping the code and data fully exportable. There are no GMV fees and no transaction taxes on top of whatever the merchant's payment processor charges. The platform cost is the platform cost, and it does not compound with revenue.
The Payment Layer Is Where the Real Change Happens
Migrating from WooCommerce to Medusa replaces the platform. It does not automatically replace the payment infrastructure. A Medusa store with the Stripe plugin installed is still routing transactions through Stripe's risk layer, still subject to Stripe's category restrictions, and still paying Stripe's pricing structure. The commerce architecture improved. The payment situation did not.
Medusa's payment system is built around modular provider plugins — any processor can be integrated without touching the storefront or the checkout flow. That architecture is specifically what makes a processor-direct integration possible, and it is why the Medusa migration creates an opportunity to upgrade the payment layer at the same time as the platform.
What Proficient Adds to a Medusa Migration
Proficient builds direct payment integrations for Medusa. A native provider plugin installs via npm and handles the full transaction lifecycle — authorization, capture, void, and refund — connected to Proficient's own processing infrastructure, with no Stripe layer in the middle and no platform taking a cut of the volume.
- Processor-direct routing — transactions go from Medusa straight to Proficient's acquiring relationships, with no consumer-gateway risk filter applied on top of card network rules
- In-house underwriting — approval decisions are made by underwriters who understand the merchant's business model, not by an automated matrix calibrated for low-risk averages. Categories that WooPayments and Stripe routinely flag — nutraceuticals, telehealth, subscriptions with trial structures, high-ticket services, adult, and others — are categories Proficient was built to approve
- No transaction markup on top of interchange — the merchant's processing cost is the merchant's processing cost, without a consumer-gateway margin sitting between interchange and the rate
- Configurable routing logic — optimized for approval rate, cost reduction, or category-specific performance depending on the transaction profile
- Capital access through the processing relationship — merchants processing through Proficient can access working capital, revenue-based financing, and equipment lending without starting a separate lender conversation from scratch
How to Approach the Migration
The practical sequence for a WooCommerce merchant moving to Medusa with Proficient handling payments: set up a Medusa Cloud organization and project, run the migration tool to transfer catalog and inventory, integrate the Proficient payment provider plugin, work through merchant account underwriting with Proficient, build or adapt the storefront, and go live.
The underwriting conversation — merchant account structure, gateway architecture, category-specific requirements — is the step with the most lead time, and it should start at the same time as the Medusa setup, not after the storefront is complete. A merchant who begins the Proficient conversation early can have payment infrastructure ready before the migration finishes.
For WooCommerce merchants who have been running on plugin debt and Stripe-imposed restrictions, the combination of Medusa's migration tool and Proficient's payment infrastructure removes both problems at once. The platform migration is now a matter of hours. The payment upgrade happens at the same time.
If you are evaluating a WooCommerce migration and want to understand what the payment side looks like on the other side, reach out at info@proficient.tech. We scope the merchant account structure, advise on the Medusa payment integration, and give a straight assessment of whether the switch makes sense for your specific business.