analyze-m1-module-for-migration_skill

Overview

This skill systematically inspects a Magento 1 module to determine its purpose, production usage, and what is required to migrate it to Magento 2. It produces a clear recommendation: migrate, replace with an alternative, or skip. The outcome is a concise migration analysis report you can share with stakeholders or use to plan migration effort and testing.

How this skill works

The skill walks a reviewer through locating module files and metadata, scanning code structure (models, resources, blocks, controllers, observers), and detecting schema changes and media usage. It verifies production usage by counting records, sampling data, and listing up to 10 real products that rely on the feature. Finally it researches Magento 2 alternatives and applies a decision matrix to recommend a migration approach with estimated effort.

When to use it

• You encounter an M1 module during a migration assessment and need to decide next steps.
• You must verify whether a module contains active data that must be migrated.
• You want to find an off-the-shelf M2 replacement before committing to custom work.
• You need a report for stakeholders with sample products and effort estimates.

Best practices

• Start by reading app/etc/modules and module etc/config.xml to capture activation, version, and dependencies.
• Prioritize checking setup scripts for custom tables or core table modifications to scope data migration work.
• Limit sample products to 10 representative SKUs for clear, actionable testing cases in M2.
• Search Adobe Commerce Marketplace, vendor sites, and GitHub for M2 equivalents before deciding on custom migration.
• Document assumptions, risks, and estimated effort clearly in the recommendation section.

Example use cases

• Analyze a product-options extension to determine if default option values must be migrated and which products use them.
• Assess a catalog import/cron module to confirm scheduled jobs, data volume, and whether jobs should run in M2.
• Review a customer data extension that added fields to core tables to plan safe data migration and schema changes.
• Validate whether a frontend widget module is active and if a marketplace module matches its features.
• Determine if media/uploads used by a module require bulk transfer and filesystem mapping to pub/media in M2.