Magento Upgrade Service

Service scope

MageHex helps plan and perform Magento version upgrades with attention to platform requirements, extensions, custom code, integrations, and the store environment.

The process covers assessment, preparation, Magento core upgrade, compatibility review, testing, and deployment based on the agreed project scope.

What We Review

Magento Version

Review the current Magento version, target version, and required upgrade path.

Server Environment

Check relevant PHP, database, search, Composer, and platform requirements for the target Magento release.

Extensions & Integrations

Review installed extensions and relevant third-party integrations for potential compatibility issues.

Theme & Custom Code

Assess theme modifications, custom modules, and store-specific code that may be affected by the upgrade.

Upgrade Process

01 - Assessment

Review the current Magento installation, environment, extensions, customizations, and target version.

02 - Preparation

Prepare the upgrade environment and appropriate backups before platform-level changes are made.

03 - Upgrade

Upgrade Magento core and perform the required dependency and database update procedures.

04 - Compatibility

Review affected extensions, themes, custom code, and integrations for compatibility issues.

05 - QA Testing

Test relevant storefront, admin, customer, cart, checkout, and operational functionality affected by the upgrade.

06 - Deployment

Deploy the tested upgrade according to the agreed deployment plan and perform post-deployment checks.

What We Check

Testing is based on the functionality relevant to the store and may include:

• Storefront and key pages
• Magento Admin
• Products and categories
• Customer accounts
• Cart and checkout
• Applicable payment and shipping functionality
• Extensions
• Third-party integrations
• Indexing, cron, and caching processes affected by the upgrade

Customer Prerequisites

Before work begins, MageHex may require:

• Access to the agreed Magento environment
• Current Magento version and desired target version
• Hosting and server environment information
• Extension and integration details
• Theme and custom module information
• Relevant credentials and technical access
• Known issues or project requirements

A staging environment is recommended where appropriate before production deployment.

Project Considerations

Magento stores can differ significantly in extensions, themes, integrations, customizations, and infrastructure.

Compatibility fixes, custom development, extension replacement, infrastructure changes, or work outside the agreed upgrade scope may require separate review and scoping.

No fixed completion time, compatibility guarantee, or zero-downtime commitment is implied unless explicitly agreed for the project.

Why Choose MageHex

Structured Process

A clear workflow from assessment and preparation through testing and deployment.

Compatibility-Focused

Extensions, themes, custom code, and integrations are considered during upgrade planning.

Controlled Implementation

Upgrade work can be prepared and tested before production deployment where the project environment allows it.

Scope Based on Your Store

The project scope is defined around the actual Magento installation rather than assuming every store is the same.

FAQ

What is a Magento upgrade?

A Magento upgrade moves an existing store from its current Magento release to a newer target version and may involve dependency updates, database changes, compatibility work, and testing.

Why should Magento be kept up to date?

Keeping Magento current can help maintain platform security, technology compatibility, access to fixes, and long-term maintainability.

Can MageHex upgrade an older Magento 2 store?

The appropriate upgrade path depends on the current version, target version, server environment, extensions, integrations, and customizations. These factors are reviewed before the project scope is defined.

Will my existing extensions continue to work?

Compatibility depends on each extension and the target Magento version. Some extensions may require updates, replacement, or additional compatibility work.

What happens if my theme is incompatible?

Theme compatibility issues can be identified during assessment or testing. Any required changes depend on the theme, customizations, and target Magento version.

Is the store tested before deployment?

Yes. Relevant functionality is tested according to the agreed project scope before production deployment.

Can custom functionality be preserved?

Custom functionality is reviewed for compatibility. Whether changes are required depends on its implementation and changes in the target Magento version.

What information is needed to start?

Typically the current Magento version, target version, hosting environment, installed extensions, theme information, custom modules, integrations, and known technical requirements.