Magento Upgrades

Available exclusively for Magento stores hosted with LexiConn


1.  LexiConn will provide a report showing any core program files which have been modified in the LIVE account. In the unlikely event there were modifications:

  • First, determine if the changes need to be carried forward. i.e. Is the feature still used? Does the new version support it natively or in another useful way?
    • If the changes will not be carried forward, the affected files will be replaced with original versions just prior to the upgrade.
    • If the changes need to be replicated in the new version, the Merchant will incorporate the needed changes after the upgrade is processed in the development account (Step 2). LexiConn will in turn update the LIVE account with the modified files from the DEVELOPMENT account after the LIVE upgrade is processed.  You will need to provide us with a list of files and locations to be replaced.

2.  Merchant reviews 3rd party Extensions

  • 3rd party extensions not in use on the site should be deleted.
    Deleting unnecessary extensions decreases the risk of post-upgrade errors/conflicts. It also eliminates additional variables from consideration when troubleshooting post-upgrade issues.
  • For remaining 3rd party extensions:
    • Verify compatibility with the version being upgraded to. This can be done by visiting the support page for the extension developer.
    • Where possible, upgrade to the most current release for each extension.

3.  Merchant reviews 3rd party Theme

  • Check with theme vendor regarding version compatibility. Download and provide LexiConn with updated files (and installation documents if these are not publicly available).

4.  Merchant reviews 3rd party Integrations (if applicable)

  • Merchant should review any external programs, scripts and/or processes which interact with Magento to ensure version compatibility. This includes cron jobs, SOAP/REST API, critical exports, etc…


1.  LexiConn will copy the LIVE Magento store to a development account (isolated from the LIVE store) and apply the upgrade.

2.  LexiConn will perform a high-level (sanity test) test for obvious issues.

3.  If applicable, merchants applies any required core file modifications (Step 1).

4.  Merchant should test all features and functions in the development account.

  • Page layouts
  • Navigation menus
  • Category display
  • Product display
  • CMS blocks, widgets, etc…
  • Shopping cart (shipping, tax calcs, coupons, gift certificates, etc…)
  • Checkout
  • Email notifications
  • Customizations (extensions, scripts, etc…)
  • Integrations (to the extent possible)


Upon successful upgrade (and issue remediation) in the development account:

1.  LexiConn will backup the LIVE account.

2.  LexiConn will set the LIVE account in maintenance mode (site will not be available)

3.  The upgrade is applied to the LIVE account.

4.  All testing is repeated with additional verification of items which could not be tested in the DEVELOPMENT account.

Leave a Reply