Migration Scanner checks extension code before Joomla migrations

Joomla sites face this problem because a CMS migration can expose old APIs, removed classes, outdated asset handling and extensions that have not declared a usable namespace. Joomla's update system handles installing updates and can use declared compatibility information in its pre-update checks, but it does not generally inspect every third-party PHP call and suggest a replacement at a specific line. A template override can avoid changing some presentation code, but it is not a practical answer for obsolete extension logic. This is where a code-scanning extension goes beyond Joomla core: according to the listing, Migration Scanner token-scans PHP, checks XML manifests, and reports findings with file paths, lines and proposed replacements. It also separates compatibility-layer cases from APIs that require code changes.

The likely audience is an agency, site owner or maintenance team preparing a staging copy for a Joomla 4.4, 5 or 6 migration, especially when several third-party extensions are involved or an agency needs a more concrete handoff than “incompatible”. A small site using only core features, or extensions already confirmed to support its target Joomla release, has little reason to install it. It is also not a replacement for updating or rewriting an extension.

The listing describes it as free, while paid rewriting support can be quoted by Infyways Solutions. The directory shows 118 other extensions from the developer, but this listing has no reviews. Before installing, check how often its 480-plus rules are maintained, how it handles false positives and custom code, and whether the proposed replacements are validated for the target site. The listing does not explain scan coverage beyond PHP tokens and XML manifests, rule update policy, or support pricing. It specifies Joomla 4.4, 5 and 6 and PHP 8.1+, and says the scan is read-only.

Listed on the Joomla Extensions Directory.