- Migration
- Moving a store onto Magento (Adobe Commerce) from another platform or from Magento 1, or moving it between Adobe Commerce editions or hosting. This site covers ten kinds; a version upgrade is the narrowest.
- Re-platform
- A migration that moves the whole application, database included. Distinct from a frontend migration, which keeps the database and replaces the theme.
- Version upgrade
- Moving a store from one Magento 2.4.x release to a later one, with PHP, the search engine, extensions, and custom code brought along. The database stays.
- Regular and extended support
- Adobe's two support windows per release. Regular support runs three years from release with quality and security fixes; extended support, offered for 2.4.6 and 2.4.7, adds a year of quality and security patches for the core application. Both dates are on the ranking page.
- Security-only period
- Adobe's one-time exception for Adobe Commerce 2.4.4, 2.4.5, and 2.4.6, giving isolated security fixes to 31 May 2027 or 31 May 2028 after extended support ends. Adobe states it will not be extended.
- Data Migration Tool
- Adobe's magento/data-migration-tool, the only official tool for moving a Magento 1 database into Magento 2. It runs settings, data, and delta modes and moves no media, admin users, or frontend.
- Delta mode
- The Data Migration Tool mode that replays changes made in Magento 1 during the data run, using triggers on the Magento 1 schema, so the old store keeps selling.
- url_rewrite
- The Magento 2 table that maps a request path to a target path for every product, category, and CMS page. Duplicate url_key values produce -1 suffixed rows that split a ranking URL in two.
- Redirect map
- The inventory of every old URL and its single-hop 301 target, built from Search Console, backlink exports, access logs, and a full crawl rather than sitemap.xml alone.
- Default Robots
- The Magento setting under Design and HTML Head that staging holds at NOINDEX,NOFOLLOW and production must read as INDEX,FOLLOW at go-live.
- hreflang
- The head tags that tell search engines which store view serves which language and country. They are regenerated against the new store-view routing on a multi-market move.
- Extension parity
- The per-module decision to rebuild, replace, or drop, made before design sign-off. Magento 1 modules, Shopify apps, and WooCommerce plugins do not run on Magento 2.
- Hyvä
- A Magento 2 frontend that replaces Luma's RequireJS, Knockout, and jQuery with Alpine.js and Tailwind CSS. Partner tiers are listed on hyva.io.
- Hyvä Checkout
- A separate Hyvä build running on Magewire, in which each payment and shipping method's rendering is reimplemented rather than ported from Luma.
- Configurable product
- A Magento parent product joined to simple child products through global attributes with fixed option lists. Shopify variants and WooCommerce variations map onto it, with conditions.
- Shared catalog
- The Adobe Commerce B2B object that carries company-specific pricing. Every shared catalog creates a customer group, and the price index holds a row per product, website, and group.
- Source of truth
- The one system that writes a given field, such as contract price or salable stock, during and after cutover. Wagento states the ERP should be that system; this site asks every agency to name one per field.
- Multi Source Inventory
- Magento's stock model, in which salable quantity derives from the sources assigned to a website. A website with no source assigned shows every product out of stock.
- ece-tools
- The deployment tooling on Adobe Commerce Cloud, which splits work into build, deploy, and post_deploy phases. Work parked in the deploy phase runs as downtime.
- Cutover window
- The period between freezing the old store and moving DNS, during which orders must land in the new store or be replayed. Who is staffed for it is a scoring criterion here.