---
title: "OpenCart to Laravel Migration: Why We Moved a Healthy Site and How We Checked Every Page"
description: "Why we moved an up-to-date OpenCart site to Laravel 13 before anything broke, how every page and address was kept, and when OpenCart should stay."
author: ["Yevhen Borovoi"]
date: 2026-11-19
updated: 2026-11-19
section: "Development"
language: en
canonical: https://peretz.agency/blog/opencart-to-laravel-migration
publisher: "Peretz Agency"
---

# OpenCart to Laravel Migration: Why We Moved a Healthy Site and How We Checked Every Page

> Why we moved an up-to-date OpenCart site to Laravel 13 before anything broke, how every page and address was kept, and when OpenCart should stay.

![Same house on a new foundation: a DeZZign house drawn as a construction section on the left and finished on the right, split by a red line](https://peretz.agency/photos/1/blog/opencart-to-laravel-migration.jpg)

## Nothing was broken on the DeZZign site. OpenCart had been updated a month earlier, the pages loaded, the leads came in. We moved it to Laravel 13 anyway, because the next stage of the project would have outgrown a shop engine. Here is why we moved early, how the move was built so that visitors noticed nothing, what took most of the effort, and when we tell clients to stay on OpenCart.

### The short answer

**Move from OpenCart to Laravel when the site has outgrown a shop engine, not when it starts to break. Move in stages: Laravel takes every request first, the old page code keeps running inside it, and pages move to native Laravel one by one. Before the switch and after every step, compare every page of the sitemap with the live site.**

OpenCart is a good platform for what it was made for: a catalogue, a cart and a checkout. Many businesses, though, run something else on it: a studio site, a portfolio, a blog, a lead form, a few landing pages. Over the years they bend the store to fit, with modules for articles, modules for projects, and a theme with the shop parts hidden. It works, but every new idea costs more than it should, and the admin keeps reminding the team that it was built for selling goods.

|  | Stay on OpenCart | Move to Laravel |
| --- | --- | --- |
| What the site does | Sells products: catalogue, cart, checkout, payments | Presents a company, collects leads, runs content, a portal or custom logic |
| Admin | The store admin fits the daily work | The team fights the admin to edit texts, projects or languages |
| Next stage | More products, more extensions | New sections, accounts, integrations, analytics, several languages done properly |
| Usual path | Update OpenCart and PHP, keep the design | Laravel in front, old code inside, pages moved one by one |

### Nothing was broken

DeZZign is an architecture and interior design studio with a site in three languages: projects, services with packages and stages, a journal, a glossary, careers. It had run on OpenCart for years. The store's catalogue engine held the pages, custom modules held the articles and projects, and the shop leftovers, product pages, the cart, the customer account, were simply hidden.

**The site was healthy when we moved it, and that was the point.** OpenCart had been brought to the latest release of its line a month before, the pages opened, search engines indexed them, forms sent leads. The reason to move was the plan, not a failure: DeZZign is preparing to grow, and the next stage needs things a store engine would only patch together. Every one of them would have meant another module on top of a platform made for something else.

> We moved while the site was healthy, not after it started to hurt.

A move made in a crisis is the expensive kind. The site is down or hacked, the team needs it back today, and every decision is taken under pressure. A move made in advance can be done step by step, with a closed copy, a rollback at every stage and time to compare the result with the original. That difference shows up in the bill and in the risk, which is why our [website modernization](https://peretz.agency/services/website-modernization) work starts with an audit and a plan, not with a rewrite.

![DeZZign website on Laravel 13: the same home page, project and service pages on desktop and phones](https://peretz.agency/photos/1/blog/opencart-to-laravel-migration/01-dezzign-site-after-laravel.jpg)
*DeZZign after the move: every page looks as it did, the base underneath is new.*

### Two stages, not one jump

The road was longer than the last step. Years ago the site ran on an old PHP version from the 5 or 7 era. The first stage was to bring it to PHP 8.2 on the last release of OpenCart 3, keeping the design, the modules and every address. That alone made the site safer and faster, and it gave a clean, current base to build the next stage on.

The second stage closed the technical debt for good. PHP 8.2 receives security fixes only until 31 December 2026, and OpenCart 3 is the end of its line: its successor, OpenCart 4, changed how extensions and themes are built, so a 3.x site with custom modules moves to 4 almost like to a new platform. Staying would have turned a healthy site into a legacy system within a year. Now the site runs on Laravel 13 and PHP 8.4, both current, with years of support ahead.

**Splitting the move into two stages kept each step small enough to check.** The first stage changed the language version and left the platform alone. The second changed the platform and left the design and content alone. We never changed two layers at once, so whenever something differed, we knew which layer to look at. We follow the same rule when we [upgrade old Laravel or PHP sites](https://peretz.agency/blog/upgrading-old-laravel-php-site-2026): one layer per step, a closed copy, a rollback plan.

### Laravel in front, OpenCart inside

The obvious way to leave OpenCart is to rebuild the site in Laravel and switch over. For a site with more than 640 pages in three languages, years of redirects, old addresses still linked from other sites and a journal search engines already know, that is the riskiest way. Every page rebuilt by hand is a page that can lose a heading, a link, an image or a line of structured data.

We did it the other way round. **Laravel 13 now takes every request, and the old OpenCart page code runs inside it as a module, with its templates and language files, until each page type moves to native Laravel.** A small set of files replaces the parts of OpenCart that no longer fit:

- the start of each request, so public pages carry no cookies and the language comes from the address;
- the template engine, moved to the current Twig 3;
- the database layer and the response, so a page is collected by Laravel and returned as a Laravel response;
- the redirect handling, so every old rule from the site's .htaccess still answers exactly as before.

Software engineers call this the strangler fig pattern: the new system grows around the old one and takes it over piece by piece, while the site keeps working the whole time. Its practical value is that the switch itself is small. On the day of the move, only the front file of the site changed. A check of key addresses ran right after it, with an automatic rollback if any status differed, and one command returns the OpenCart front if ever needed.

The pages now move to native Laravel controllers and Blade templates one type at a time, each with the same comparison against the live version. We used the same idea when we [moved The Structure from static pages to Laravel without changing a single byte](https://peretz.agency/blog/static-site-to-laravel-byte-for-byte).

### What took the time: the checks

Owners often ask how long such a move takes. **The honest answer is that it was a fairly long process, and most of it was checking, not writing code.** The code that runs OpenCart inside Laravel is not large. Proving that nothing changed for visitors, search engines and the team is the real work.

> Most of the effort went into proving that nothing had changed.

Before the switch every one of the 642 pages in the sitemap was rendered by the new base and compared with the live site, text and markup, whitespace ignored. The same comparison covered what a sitemap does not list: redirects, the 404 page, pagination, the site search, the old addresses with ?route= that OpenCart used to print, the "show more" lists loaded by script and the validation of empty forms. Only after all of them matched did the switch go ahead.

The database needed its own check. All 186 tables moved from MyISAM to InnoDB, the engine MySQL recommends, which writes changes as transactions and does not lose them on a crash. The data was compared before and after by a fingerprint and came out identical. One difference surfaced anyway: when two rows have the same sort number, MyISAM returns them in the order they were written, InnoDB in the order of their keys. **Without a fix, projects and articles would have changed places in lists with nobody touching them.** The link tables were renumbered in their old order and the page queries now sort explicitly.

The front end got the most detailed comparison. Old and new scripts were run side by side on 15 page types, on desktop and phone width, in two browser engines, in the dark and light themes. We compared screenshots after loading, after opening the menu, after switching the theme and after opening a popup. The forms had to produce the same requests byte for byte, and those requests were caught in the test browser, never sent, so no test ever reached the studio's inbox. The styles were checked element by element: the computed style of every element on 18 page types, old and new, with zero differences allowed.

The full list of what a migration has to keep is in our [website migration checklist](https://peretz.agency/blog/website-migration-checklist-agencies-skip). On this project every item on it was a test that had to pass, not a line to tick.

### What became faster

The move was not a redesign, so the site looks the same. What changed is the weight of everything a visitor downloads. The figures below were measured on the live site in November 2026.

| What | Before | After |
| --- | --- | --- |
| Scripts on the home page, compressed | 124 KB | 35 KB |
| Scripts on a service page, compressed | about 100 KB | 32 KB |
| Stylesheets, compressed | 35.8 KB | 28.3 KB |
| Photos used on the pages | 95 MB | 67 MB in WebP copies |

The scripts lost jQuery and the old bundles; every effect, menu, form and mask now runs on plain modern JavaScript, with the same timings as before. The stylesheets lost selectors no page uses and prefixes only old browsers read. **The photos were never recompressed: the originals stay untouched, and browsers that support WebP get a lighter copy only where it is visually identical.** Social previews and structured data still point to the original JPEG files.

Public pages no longer set cookies, which lets a CDN cache them later, and every article is also available as Markdown at its own address for AI assistants and crawlers. These details sound small, but together they make the site faster on a phone and cheaper to grow.

### An admin built for the team

**The biggest change for the people who run the site is the admin.** The OpenCart admin is a store template: products, categories, options, with the studio's articles and projects squeezed into modules. Editing a project in three languages meant jumping between tabs and forms that were never designed for it.

The new admin is built around how the studio works. Articles, projects, services with their packages and stages, careers, pages, blog sections and the home page sit in one menu, each language beside the others. Every save writes only what changed and keeps the old value in a history, so any change can be put back. A form opened on an older version of a record is refused instead of overwriting someone else's edit, and a form cut short by server limits is refused instead of saving half a page. Team members kept their logins: an old OpenCart password works once and is then stored in a modern format.

![DeZZign admin on Laravel: control panel, article editor in three languages and the files section](https://peretz.agency/photos/1/blog/opencart-to-laravel-migration/02-dezzign-laravel-admin.jpg)
*The new admin: one menu for the studio's content, three languages side by side, every change in a history.*

The admin also has an analytics page. Search Console, Google Analytics, Bing, visits of search and AI crawlers, the state of the hosting and of the code are on one screen. The manager sees leads and requests, the content manager sees which articles are found and read, the marketer sees channels and queries, and nobody has to collect it from five services.

![Analytics page of the DeZZign admin with Search Console, Google Analytics, Bing and crawler visits, figures blurred](https://peretz.agency/photos/1/blog/opencart-to-laravel-migration/03-dezzign-admin-analytics.jpg)
*The analytics page inside the admin. Figures are blurred on purpose.*

### The same road from other platforms

OpenCart is one starting point. The same approach, a new base under an unchanged site, has carried several of our projects in 2026:

- **IFHRS**, the international federation of hair research societies, moved from WordPress with Elementor to Laravel 13 with six languages and its own admin. The full story is in the case [IFHRS: back to Laravel, from WordPress 7 to Laravel 13](https://peretz.agency/blog/ifhrs-wordpress-to-laravel-13), and the technical part in [Elementor to Laravel Blade](https://peretz.agency/blog/elementor-to-laravel-blade).
- **The Alopecia School**, a patient organisation, had a landing built in 2017 and one large WordPress article. It moved to Laravel with the same pixels, a Ukrainian and an English version, and a page six times lighter; the old files also held a foreign script that sent visitors to spam sites, and the move removed it. See the [Alopecia School case](https://peretz.agency/portfolio/korporativnyye-sayty/alopecia-school).
- **EEAHRS**, the Eastern European hair research society, had 54 static pages edited by hand. They moved to Laravel with an admin, every page identical at the switch, and only then gained an English version, a Ukrainian version and a news section ([EEAHRS case](https://peretz.agency/portfolio/korporativnyye-sayty/eeahrs)).

**The Ukrainian Hair Research Society shows the other side: its site stayed on WordPress.** WordPress still fits what UHRS does, so we updated it from 5.2 to 6.9, kept its structure and rebuilt the look, as told in the [UHRS case](https://peretz.agency/portfolio/korporativnyye-sayty/uhrs). Moving a platform is a tool, not a goal.

### When OpenCart should stay

Not every OpenCart site should become a Laravel site. **If the business is a store and OpenCart does the selling well, the right move is usually to update it, not to leave it.** We did exactly that for the Trichocosmetics store of the Institute of Trichology: it stayed on OpenCart, moved to the latest 3.0 release and PHP 8.4, and kept its design. The modernization made it responsive and safe without a new platform.

Leaving OpenCart makes sense when several of these are true at once:

- the site mostly presents a company, its work and its articles, and the shop parts are hidden;
- the team spends more time fighting the admin than editing content;
- the next stage needs accounts, a portal, a CRM link or other logic of its own;
- languages, structured data and speed are held together by extensions that conflict with each other;
- the extensions the site depends on have no maintained version for current PHP.

If only one is true, an update is usually cheaper. If most are true, every year on OpenCart adds to the [technical debt](https://peretz.agency/blog/hidden-technical-debt-website-redesigns) the next move will have to pay off. For stores that are thinking of Shopify Plus or a custom build instead, we compared the options in [leaving Magento: upgrade, Shopify Plus or custom Laravel](https://peretz.agency/blog/leaving-magento-shopify-plus-or-laravel); the reasoning for OpenCart is close.

### Frequently asked questions

#### Can a site move from OpenCart to Laravel without changing its URLs?

Yes. Laravel can answer every old address, including the ?route= addresses OpenCart prints, and keep every redirect from the old .htaccess. On DeZZign every address stayed the same, and that was checked page by page before the switch.

#### How long does an OpenCart to Laravel migration take?

It depends on the number of pages, languages, extensions and integrations. Writing the new base is the smaller part; checking that every page, redirect and form behaves as before is the larger one. We give a timeline and a fixed price after the audit.

#### Will the site lose search rankings after the move?

Not if addresses, titles, descriptions, structured data and content stay the same, and that is what the page-by-page comparison is for. A move that keeps every page identical gives search engines nothing to re-evaluate except a faster site.

#### Do we have to rebuild the whole site at once?

No. Laravel can run the old page code inside it while the pages move to native Laravel one type at a time. The site keeps working the whole time, and each step can be checked and rolled back on its own.

#### Should we upgrade to OpenCart 4 instead?

If the site is a store and its extensions exist for OpenCart 4, that can be the right path. A 3.x site with custom modules, though, moves to 4 almost like to a new platform, and then it is worth comparing that work with a move to Laravel.

#### What happens to the data and the admin users?

The data stays in the same database. On DeZZign the tables moved to InnoDB with every row identical, the new admin reads the same records, and team members signed in with their old passwords.

#### How much does a migration cost?

It starts with an audit, from $300 for a small site and from $1,000 for a large one. The work itself is priced after the audit, as a fixed price with a timeline, because it depends on what the audit finds.

**Sources**

- [PHP supported versions](https://www.php.net/supported-versions.php)
- [Laravel release notes and support policy](https://laravel.com/docs/13.x/releases)
- [OpenCart releases on GitHub](https://github.com/opencart/opencart/releases)
- [Martin Fowler, Strangler Fig Application](https://martinfowler.com/bliki/StranglerFigApplication.html)
- [MySQL 8.4 Reference Manual: introduction to InnoDB](https://dev.mysql.com/doc/refman/8.4/en/innodb-introduction.html)

**Your site runs on OpenCart, and your plans have grown past a store? Let's look at what the move would take.**

[Book a Strategic Session](https://peretz.agency/services/strategic-session)

[Website Modernization](https://peretz.agency/services/website-modernization)

---

Source: Peretz Agency, https://peretz.agency/blog/opencart-to-laravel-migration
