migration-guide

Name: migration-guide
Availability: InStock
Author: amo-tech-ai

Guide Mercur 1.x to 2.0 migration with analysis, mapping, and execution.

2|1|Updated May 20, 2026

Search Tags:#migration #configuration #project analysis #code porting #Mercur

Ready to run

npx skills add https://github.com/amo-tech-ai/mdeapp --skill migration-guide-amo-tech-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migration-guide
Source: https://github.com/amo-tech-ai/mdeapp/tree/main/commerce/mercur/.claude/skills/migration-guide
Command: npx skills add https://github.com/amo-tech-ai/mdeapp --skill migration-guide-amo-tech-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the migration process from Mercur 1.x to 2.0, providing a guide and tools to simplify the transition.

Core Features & Use Cases

Project Analysis: Analyze Mercur 1.x projects to determine the scope and effort of migration.
Package and Directory Mapping: Guide on mapping 1.x packages and directories to their 2.0 equivalents.
Config Migration: Assist with updating medusa-config.ts to align with 2.0 plugins and modules.
Workflow Execution: Execute the migration workflow step-by-step, including porting of custom code.
Verification: Verify the migration's success by checking server start, endpoints, and dashboard rendering.
Use Case: A developer is tasked with migrating a Mercur 1.x project to 2.0. This Skill helps them analyze the project, map dependencies, update configuration, and execute the migration.

Quick Start

Migrate your Mercur 1.x project to 2.0 by running the migration-guide skill with the path to your old project as an argument.

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 2.0?▼

To migrate a Mercur 1.x project to 2.0, you can use a structured workflow that analyzes your project, maps packages and directories, updates medusa-config.ts, and executes code porting step-by-step.

What is the process for mapping Mercur 1.x packages to 2.0?▼

Mapping Mercur 1.x packages to 2.0 involves analyzing your existing project structure and translating old packages and directories to their new 2.0 equivalents to ensure compatibility with the updated architecture.

How do I update medusa-config.ts for Mercur 2.0 plugins and modules?▼

Updating medusa-config.ts for Mercur 2.0 requires modifying your configuration file to align with the new 2.0 plugins and modules structure during the migration workflow execution.

Do I need to know the Mercur project structure to migrate to 2.0?▼

Yes, migrating to Mercur 2.0 requires existing knowledge of the Mercur project structure and configuration to effectively analyze dependencies and execute the transition accurately.

How do I verify a successful Mercur 1.x to 2.0 migration?▼

Verifying a successful Mercur 2.0 migration involves checking that the server starts correctly, API endpoints respond properly, and the dashboard renders without errors after porting your custom code.