- Version upgrade
- Moving a store from one Magento 2.4.x release to a later one, with the core, PHP, extensions and custom code brought along. Distinct from a patch and from a migration.
- Security patch
- A fix Adobe publishes for a supported release, applied without changing the minor version. A patch cycle is the work of applying one and testing the result.
- Migration
- Moving a store from another platform, or from Magento 1, onto Magento 2. Counts for half of a version upgrade on this site's evidence criterion.
- Regular support
- The period in which Adobe publishes security patches and quality fixes for a release. Dates are on Adobe's lifecycle policy page.
- Extended support
- A further period after regular support in which Adobe Commerce customers keep receiving patches, at no additional cost on 2.4.6 and 2.4.7 according to Adobe's lifecycle page, which lists it for Adobe Commerce and makes no mention of Magento Open Source.
- Security-only period
- A one-time transitional period Adobe's lifecycle page lists for 2.4.4, 2.4.5 and 2.4.6 after extended support, with isolated security fixes and no quality fixes, ending 31 May 2027 for 2.4.4 and 2.4.5 and 31 May 2028 for 2.4.6. The page states it will not be extended.
- Magento Open Source
- The free edition of Magento, without the B2B suite, returns management, reward points, store credits and gift cards that Adobe Commerce adds.
- Adobe Commerce
- The licensed edition, on-premise or on Adobe's cloud, with the features above, access to the Upgrade Compatibility Tool and extended support on the release lines Adobe's lifecycle page lists.
- Mage-OS
- A community-maintained distribution of Magento Open Source. Three agencies here state Mage-OS work or partnership; none publishes a Mage-OS upgrade case.
- Upgrade Compatibility Tool
- Adobe's tool for checking a customized instance against a target version. Adobe's documentation states it is available for Adobe Commerce instances only.
- Compatibility audit
- The review of every extension, custom module and the PHP level against the target release that produces the estimate. integer_net and Inchoo publish a price for it; scandiweb publishes it as the first step of its process.
- Composer constraint
- The version range an extension declares for the packages it depends on. A constraint that excludes the target release stops the upgrade until the extension is updated, patched, rewritten or removed.
- Template override
- A copy of a core .phtml file placed in a theme. It keeps serving the copied markup after an upgrade, so core fixes never reach it.
- Plugin and preference
- Magento's two ways of changing core behavior through di.xml. Both break when the core method they attach to changes its signature.
- Staging copy
- A full copy of the production store, code and data, on which the upgrade is built and tested before cutover.
- Rollback path
- The written steps for returning the live store to its pre-upgrade state if the cutover fails, prepared before the freeze window starts.
- Freeze window
- The period during cutover in which no orders, catalog changes or admin edits are accepted. Its length is set by the reindex time on the production catalog.
- Hyvä
- A Magento frontend that replaces the stock Luma theme. hyva.io lists partner tiers; four agencies here are Platinum.
- Takeover
- An agency assuming maintenance of a store built by another agency, usually starting with a code review. Vendic publishes a takeover process with an average time to stable.