MegaComp: moving from OpenCart to Medusa.js and Next.js

The computer and electronics shop moved from OpenCart to Medusa.js and Next.js on 15 October 2026. Its mobile audit score went from 28 to 100, the catalogue grew to more than 52,000 products, and old URLs lead to the new pages.

A product page in the new megacomp.bg shop on desktop

Results

28 → 100mobile score in the Maina Workspace audit, OpenCart vs Medusa
84 → 95overall score in the same audit before and after the move
52,000+products in the catalogue (was 7,315), now fed by distributors
99.7%of 36,116 old URLs redirect with a 301 to their new page
5.5 → 0.8 MBhome page weight on a phone (Lighthouse)
~45 minswitch-over window from OpenCart to Medusa

MegaComp sells computers, components and electronics. Its online shop ran on OpenCart 2.3 on PHP 5.6, versions that have had no security updates for years. We moved it from OpenCart to Medusa.js and Next.js: a new shop at the same address, automatic distributor feeds, a PC configurator and redirected old URLs so its Google rankings carried over.

The new shop has been live at megacomp.bg since 15 October 2026.

The result in short

  • Mobile score in the Maina Workspace site audit: from 28 to 100.
  • Overall score in the same audit: from 84 on the old platform to 95 after the fixes.
  • Catalogue: from 7,315 products in OpenCart to more than 52,000 in the sitemap, because products now arrive automatically from distributors.
  • Old URLs: 35,995 of 36,116 redirect with a 301 to their new page.
  • Switch-over: about 45 minutes, on the morning of 15 October.
  • Product page on a phone: 4 times lighter (2.6 MB → 0.6 MB), and the home page 7 times (5.5 MB → 0.8 MB).

Before and after

A product page in the old OpenCart shop, on a phone

The same product in the new Medusa and Next.js shop, on a phone

The same laptop, an ASUS Vivobook 15: first in the old shop, then in the new one, on a 412 px wide phone.

Why it had to happen

The old platform had become a risk. OpenCart 2.3 and PHP 5.6 get no security fixes, so we brought the move forward. The new shop runs on its own server, and every change goes through a test copy first.

A catalogue that keeps itself up to date

MegaComp doesn't type in thousands of products by hand. The shop is connected to five distributors: ASBIS, Solytron, MOST, Dekada and Apcom. Prices, stock, specifications and images arrive automatically twice a day. The first full cycle after launch updated 6,016 products from ASBIS, 18,839 from Solytron, 5,905 from MOST, 1,237 from Dekada and 1,198 from Apcom.

Stock is kept as real warehouse quantities. When the shop wants a product to stay at a set price, it locks the price and the sync leaves it alone. Where distributors send no images, the shop fills them in from Open Icecat: one bulk run added 48,712 images.

PC configurator

The MegaComp configurator on desktop: case view and component list

The configurator picks compatible components and shows estimated performance as you build. The eight core components are chosen around a view of the case, and separate tabs add peripherals and software. A finished build can be saved, shared and ordered.

Orders, delivery and payment

Delivery is by Speedy or Econt to an office, to a Speedy locker, or by pickup from the store. On a phone, the office is picked from a searchable list. Payment is cash on delivery or bank transfer. The admin has a Waybills module with live status, printing and cancelling, and every new order also lands in the shop's inbox.

The migration, without losing customers or rankings

A shop with years of history has thousands of URLs Google already knows. Before the switch we built a redirect map and ran it against the test copy: of 36,116 old URLs, 35,995 lead with a 301 to their new page and 20 answer that the page no longer exists. After the switch, 49 of the 50 most visited pages in Google Search Console opened with a single redirect.

We moved the registered customers and their order history. On launch day all 120 customer accounts received an email inviting them to set a new password.

The audit, before and after

The Maina Workspace site audit checked the old platform on 5 October and the new one after launch, with the same rules:

OpenCart, 5 OctoberMedusa, 16 October
Overall score8495
Mobile28100
Accessibility6688
Performance7589

On 15 November we also ran Lighthouse on the same pages of both shops, on a phone, as the median of three runs. The old shop ran from a copy on a local machine with no network delay, which favours it:

Lighthouse, phoneOpenCartMedusa
Home page weight5.5 MB0.8 MB
Product page weight2.6 MB0.6 MB
Home page main content shows after18.6 s3.7 s
Accessibility, home page8396
Best practices, home page58100
SEO, home page92100

The newer audit runs more checks (217 vs 150), so compare the direction rather than the exact points.

What happens from here

The shop runs on its own server, which we rent and maintain. The code belongs to MegaComp. Every change goes through a test copy first and reaches customers after approval.

MegaComp is a custom project, larger than our packages: five distributors, a configurator and more than 52,000 products. If you're considering the same move, see how we approach moving to Medusa or write to us.

Maina®

Want a similar outcome for your business?

Tell us what you are building and we will propose a clear technical direction.

Start a projectFirst conversation · No obligation