Magento 1 reached end of life on 30 June 2020. A store still running it in 2026 has gone more than six years without an official security patch, on a codebase whose PHP version, payment integrations and PCI posture all aged out together. Two of the eight agencies on this page describe that risk in their own copy. IWD Agency puts it most plainly, stating that Magento 1 is end of life with no security support, so moving to Adobe Commerce removes real risk. InteractOne says the same thing from the merchant's side in its Aladdin Temp-Rite case study, stating that Magento 1 had come to the end of its useful life since Magento had ended support for version 1. That is why a Magento 1 move is scoped as a rebuild rather than an upgrade: the data crosses over, almost nothing else does.
Here is the number that should change how the rest of this page reads. Of the eight agencies here other than scandiweb, exactly two publish a case study that names Magento 1 as the platform they took a store off: InteractOne, with V-Belt Global Supply, Aladdin Temp-Rite and Sam Villa, and Aureate Labs, with Lancer Skincare. That is the entire lane's verifiable Magento 1 proof. Three of the eight no longer keep a dedicated Magento 1 to Magento 2 page at all: Codilar folds migration into its general Adobe Commerce page, On Tap into a general migration page, and Magenest into a platform-agnostic Website Migration Services page. Everyone will tell you they can move you off Magento 1. Two of them have published a store they moved.
Two of the case studies most likely to be shown to you in a pitch are not Magento 1 migrations at all, and both agencies say so on their own pages if you read them. Codilar's flagship, ALDO, is a move from Oracle SuiteCommerce to Adobe Commerce; its only named Magento 1 reference, EGC Supply, appears in body copy with no case study page behind it. Magenest's flagship, Supervalue for SM Markets, is explicitly a refactor of an existing Magento 2 build. ScienceSoft anonymises most of its migration clients by industry, and the one case study that does name a source platform is a Shopify move. IWD Agency and WolfSellers publish twelve named case studies between them and not one of them states the source platform. None of this means the work was never done. It means you will have to ask for it, and the request is short: name two Magento 1 stores you took to Magento 2, and give me a contact at one of them.
What you are buying is a data move plus a rebuild, not a copy. Data is the part with published method behind it. InteractOne and WolfSellers both state they use Adobe's Data Migration Tool, WolfSellers adds ETL checkpoints, rollback and a post-migration reconciliation against comparative reports, IWD Agency states it reconciles the data after transfer so nothing is silently dropped, Aureate Labs states it takes a full backup during the process, and Magenest states its data move runs on its shopping cart migration partner LitExtension, which is a third-party tool rather than an in-house method. The rebuild is the part buyers underestimate. A Magento 1 theme cannot be carried across, so the front end is rebuilt whatever happens, which is when the Hyva question usually gets settled. Magento 1 extensions do not run on Magento 2, so every one of them is replaced with a Marketplace equivalent, rewritten as custom code, or dropped. Only WolfSellers publishes an explicit audit of that problem. Everyone else folds extensions into a generic phase, which is exactly where an underscoped quote goes wrong.
On the three questions a buyer asks first, the lane is uneven. Four of the eight publish a timeline and they do not agree: ScienceSoft says around 3 months, Codilar 4 to 13 weeks by complexity, Aureate Labs 12 weeks, and WolfSellers 3 to 5 months standard against 6 to 9 months for a store with 50 or more custom modules. InteractOne explicitly declines to publish one. On price, one of the eight publishes any figure at all, and it is narrower than it first reads: Aureate Labs states it costs $15,000 onwards for a quality Magento 1 to Magento 2 migration theme, which is the theme, not the project. Nobody in this set publishes a fixed-price migration package. And none of the eight publishes a support response time or a named SLA, so on the question of what happens when something breaks after go-live, eight of the nine entries here are asking you to take it on trust. scandiweb is the only one that publishes a number.
One result of this weighting is worth stating plainly, because it looks odd and it is not a mistake. Codilar ranks second at 61 while publishing a single line of Magento 1 body copy, and InteractOne ranks third at 54 while publishing three Magento 1 case studies. InteractOne takes the full 32 on the criterion weighted heaviest here and then scores nothing on three of the other five, because it publishes no team size, no certification count and no support terms. Codilar scores 11 on Magento 1 proof and picks up points on every other line. If the only thing you care about is whether an agency has demonstrably taken a store off Magento 1, read the first criterion rather than the order, and start with InteractOne. The scores are printed against every entry so that re-weighting is a two-minute job rather than an argument.
Finally, worth saying out loud: this is a shrinking question, and the page is written accordingly. Magento 1 has been unsupported for six years, search demand around it has collapsed rather than levelled off, and the agencies have widened their own pages in response. If you are moving from an old Magento 2 version, from Magento Open Source, or from another platform entirely, the same six criteria apply and most of the same agencies are relevant. IWD Agency states it moves stores from Magento 1, Magento Open Source and other eCommerce platforms. WolfSellers bands a Shopify or VTEX move at 4 to 6 months, Aureate Labs publishes 9 weeks from Shopify, BigCommerce, WooCommerce or PrestaShop, and ScienceSoft publishes a Shopify to Adobe Commerce case study. Only the first criterion changes: for a move that does not start on Magento 1, ask for a case study naming your source platform instead.