mcpField
M
magento-upgrade-specialist

magento-upgrade-specialist

github.com/maxnormDevelopment31159 installsUpdated 40w ago
Repository

About magento-upgrade-specialist

magento-upgrade-specialist is a skill for teams upgrading Magento installations or migrating from Magento 1 to Magento 2. It covers compatibility reviews, migration planning, execution, testing and post-upgrade checks.

Key features

  1. 01Pre-upgrade system audit
  2. 02Extension compatibility checks
  3. 03Upgrade path planning
  4. 04Code and database migration
  5. 05Post-upgrade testing

Use cases

  1. 01Planning a Magento version upgrade
  2. 02Assessing custom code compatibility
  3. 03Migrating Magento 1 to Magento 2
  4. 04Validating an upgrade before release

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/maxnorm/magento2-agent-skills --skill magento-upgrade-specialist

After installing, type/magento-upgrade-specialistin Claude Code to confirm it loaded.

Details

From the project README

Magento 2 Upgrade Specialist

Expert specialist in ensuring smooth, risk-free transitions between Magento versions while maintaining business continuity and preserving custom functionality.

When to Use

  • Upgrading Magento 2 versions (minor or major)
  • Migrating from Magento 1.x to Magento 2.x
  • Planning upgrade strategies and timelines
  • Assessing extension compatibility
  • Handling breaking changes
  • Post-upgrade optimization

Upgrade Process Framework

1. Pre-Upgrade Assessment
  • Current System Audit: Comprehensive analysis of existing Magento installation
  • Custom Code Review: Evaluate all custom modules, themes, and modifications
  • Extension Compatibility: Check third-party extension compatibility with target version
  • Data Integrity Check: Verify database consistency and identify potential issues
  • Performance Baseline: Establish current performance metrics for comparison
2. Compatibility Analysis
  • Static Code Analysis: Use automated tools to identify compatibility issues
  • API Change Review: Analyze breaking changes in core APIs and interfaces
  • Deprecated Feature Assessment: Identify and plan replacement for deprecated functionality
  • Database Schema Changes: Review required database modifications
  • Configuration Changes: Identify system configuration updates needed
3. Migration Planning
  • Upgrade Path Strategy: Choose optimal upgrade path (direct vs. incremental)
  • Environment Setup: Plan development, staging, and production upgrade environments
  • Downtime Minimization: Develop strategies to reduce production downtime
  • Data Migration Strategy: Plan for large dataset migrations and optimizations
  • Contingency Planning: Prepare for various failure scenarios and recovery procedures
4. Implementation Execution
  • Code Migration: Update custom code to work with target Magento version
  • Database Upgrade: Execute database schema and data migrations
  • Configuration Migration: Transfer and update system configurations
  • Extension Updates: Upgrade or replace third-party extensions
  • Testing Validation: Comprehensive testing of all upgraded functionality

Upgrade Categories

Minor Version Upgrades (2.4.x to 2.4.y)
  • Security Patches: Apply critical security updates
  • Bug Fixes: Resolve known issues and stability improvements
  • Feature Enhancements: Leverage minor feature additions
  • Compatibility Updates: Maintain extension and custom code compatibility
  • Performance Improvements: Benefit from performance optimizations
Major Version Upgrades (2.3.x to 2.4.x)
  • PHP Version Updates: Handle PHP version compatibility requirements
  • Composer Dependencies: Update package dependencies and constraints
  • API Changes: Adapt to breaking changes in core APIs
  • New Architecture: Leverage new architectural improvements
  • Migration Tools: Utilize official migration utilities and scripts
Legacy Migrations (Magento 1.x to 2.x)
  • Data Migration: Comprehensive data structure transformation
  • Theme Migration: Complete frontend redesign and implementation
  • Extension Replacement: Find and implement Magento 2 equivalents
  • Custom Code Rewrite: Rebuild custom functionality for Magento 2
  • Training Requirements: Team training on Magento 2 architecture

Upgrade Commands

Pre-Upgrade
# Check current version
bin/magento --version

# Check database status
bin/magento setup:db:status

# Backup database
mysqldump -u user -p database > backup.sql

# Check extension compatibility
composer show | grep magento
During Upgrade
# Update composer dependencies
composer require magento/product-community-edition:2.4.x --no-update
composer update

# Run upgrade
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
bin/magento cache:flush
bin/magento indexer:reindex
Post-Upgrade
# Verify installation
bin/magento setup:db:status
bin/magento setup:upgrade

# Test functionality
# Run automated tests
# Manual testing checklist

Common Upgrade Challenges

Breaking Changes
  • API Changes: Update code using deprecated APIs
  • Class Changes: Update class references and namespaces
  • Configuration Changes: Update XML configuration files
  • Database Schema: Handle schema changes and migrations
  • Frontend Changes: Update templates and layouts
Extension Compatibility
  • Version Conflicts: Resolve composer dependency conflicts
  • API Compatibility: Update extensions using deprecated APIs
  • Replacement Extensions: Find Magento 2 equivalents for incompatible extensions
  • Custom Patches: Create patches for minor compatibility issues
Data Migration
  • Schema Changes: Handle database structure changes
  • Data Transformation: Transform data to new formats
  • Custom Attributes: Migrate custom EAV attributes
  • Media Files: Migrate images and media files

Best Practices

Planning
  • Timeline Planning: Create realistic upgrade schedules with proper testing phases
  • Risk Analysis: Identify potential breaking changes and their business impact
  • Resource Planning: Estimate effort, downtime, and team requirements
  • Rollback Strategy: Plan comprehensive rollback procedures
Execution
  • Environment Testing: Test thoroughly in development and staging
  • Incremental Approach: Consider incremental upgrades for major version changes
  • Documentation: Document all changes and customizations
  • Communication: Keep stakeholders informed throughout the process
Post-Upgrade
  • Performance Validation: Ensure performance meets or exceeds baseline
  • Functionality Testing: Comprehensive testing of all features
  • Security Review: Verify security improvements are properly implemented
  • Monitoring: Monitor system health and performance post-upgrade

Testing Strategy

  • Unit Tests: Run and update unit tests
  • Integration Tests: Test module integration with core
  • Functional Tests: End-to-end test scenarios
  • Performance Tests: Validate performance under load
  • Security Tests: Verify security compliance

References

Focus on smooth, risk-free upgrades that maintain business continuity while leveraging new Magento capabilities.

Comments

Markdown supported