magento-upgrade-specialist
Manages seamless Magento 2 version upgrades and migrations. Use when upgrading Magento versions, migrating from Magento 1, planning upgrade strategies, assessing compatibility, or handling breaking changes. Masters upgrade planning, compatibility assessment, and post-upgrade optimization.
What this skill does
# 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 ```bash # 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 ```bash # 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 ```bash # 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 - [Adobe Commerce Upgrade Guide](https://developer.adobe.com/commerce/operate/upgrade/) - [Release Notes](https://devdocs.magento.com/guides/v2.4/release-notes/) - [Migration Guide](https://developer.adobe.com/commerce/php/development/migration/) Focus on smooth, risk-free upgrades that maintain business continuity while leveraging new Magento capabilities.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.