skills.rest
amoai-tech
amoai-techCOMMUNITY
Explore all skills by this author →
GitHub

migration-guide

Analyzes Mercur 1.x projects and guides migration to Mercur 2.0.

1|Updated Sep 15, 2026
Search Tags:#migration#marketplace#upgrade#ecommerce#medusajs#code porting#mercur
One-click install
npx skills add https://github.com/amoai-tech/mdeai --skill migration-guide-amoai-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration-guide
Source: https://github.com/amoai-tech/mdeai/tree/main/commerce/mercur/.claude/skills/migration-guide
Command: npx skills add https://github.com/amoai-tech/mdeai --skill migration-guide-amoai-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migrating a Mercur 1.x marketplace project to 2.0 involves renamed packages, moved directories, changed imports, and new provider registration rules, making manual upgrades error-prone and slow. ## Core Features & Use Cases - Project Analysis: Scans package.json, medusa-config.ts, modules, workflows, API routes, subscribers, links, and admin pages to inventory custom code. - Complexity Classification: Categorizes projects as Starter, Light custom, or Heavy custom before migration begins. - Guided Porting: Maps packages, directories, and imports from 1.x to 2.0 and ports config, providers, modules, workflows, links, subscribers, API routes, middleware, and dashboard pages in a verified order. - Use Case: Point the skill at an existing Mercur 1.x marketplace repository to receive a full migration plan and step-by-step porting with build verification after each stage. ## Quick Start Analyze my Mercur 1.x project at ./my-marketplace and guide me through migrating it to Mercur 2.0.

Frequently Asked Questions about migration-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a Mercur 1.x project to Mercur 2.0?▼

Scan the old project's package.json, medusa-config.ts, and custom code directories, classify its complexity, then port config, providers, modules, workflows, links, subscribers, API routes, middleware, and dashboard pages in order. Verify the server starts after each group with bun medusa develop.

What replaces @mercurjs/b2c-core in Mercur 2.0?▼

@mercurjs/b2c-core is replaced by @mercurjs/core, which includes all core modules built in. The commission package is also built into core, while algolia becomes a registry block installed with mercurjs add algolia.

Does Mercur 2.0 support the 1.x Stripe Connect and Resend packages?▼

No, @mercurjs/payment-stripe-connect, @mercurjs/resend, and @mercurjs/stripe-tax-provider have no 2.0 equivalent and must be ported manually. The migration should stop and flag these integrations for manual handling.

Why does my custom provider fail with Cannot find module in Mercur 2.0?▼

Providers in medusa-config.ts must use the ./src/ prefix, such as ./src/providers/my-provider, and entry files must import from @medusajs/framework/utils instead of @medusajs/utils.

When should I not attempt an automatic Mercur migration?▼

Stop when a custom module depends on internal APIs not in core, a third-party integration has no clear migration path, database schema conflicts arise, or the old project modifies MedusaJS core. In-place upgrades of 1.x projects should never be attempted.

Related Skills

Explore More Software Engineering Skills→
nathangaleanathangalea

migration-guide

Analyzes Mercur 1.x projects to plan migration to Mercur 2.0.

Community
Advanced
OZVEOZVE

dashboard-form-ui

Create or modify dashboard forms with react-hook-form and zod validation.

Community
Intermediate
HillBombCreationsHillBombCreations

vivreal-site-deploy-pipeline

Automate customer website deployment with AWS Step Functions and Route53.

Official
Advanced
skaile-aiskaile-ai

skailup-prog-expert-integration-ai-agents

Integrate LLM agent sidecars into Nuxt 4 frontends via a Typed Action Protocol.

Official
Advanced