A Magento 1 to Magento 2 project is a platform migration, not an ordinary in-place upgrade. This preliminary check helps establish the visible starting point before committing to migration discovery, scope and budget.

Note: This is a preliminary external assessment. Extension compatibility, custom code and database migration complexity require access to the Magento installation.

What the preliminary assessment covers

  • the Magento 1 version and runtime signals visible from the public storefront;
  • publicly visible configuration and security concerns that affect the starting baseline;
  • storefront characteristics that should be raised during migration discovery;
  • whether the visible installation provides enough evidence to proceed to a detailed assessment.

What requires installation access

Magento 2 does not reuse a Magento 1 codebase as a conventional upgrade. Extensions, themes, custom business logic and integrations must be replaced, rewritten or deliberately retired. Catalog, customer, order, CMS and configuration data require a designed and tested migration process.

The detailed assessment therefore reviews the application and database, business-critical workflows, extension replacements, integration contracts, data volume, infrastructure requirements and cutover constraints. Its purpose is to determine whether Magento 2 is justified and to define a realistic migration path rather than treating it as the automatic successor to every Magento 1 store.