Migrating OpenCart 3 to 4: Data Transfer, Templates, and Extensions

Migrating from OpenCart 3 to 4 is not an update—it's a complete rebuild. We've encountered projects where custom extensions and non-standard templates turned the process into a puzzle. Without a detailed plan and testing, you risk losing data and customers. Our team has over 10 years of experience and has completed 40+ OpenCart migrations, so we know every pitfall. Let's break down how to transfer data, adapt code, and maintain performance.

Why migrating OpenCart 3 → 4 is not just an update

OpenCart 4 is a completely reworked platform. It requires PHP 8.0+, templates have moved from PHP to Twig, and the OCMOD extension system has been replaced by the Events System. Direct upgrade is impossible—you need a data migration and a full rewrite of custom code. According to the official OpenCart documentation, the transition requires a thorough audit and testing.

What technical challenges we solve

• PHP incompatibility. OC3 ran on PHP 7.x, OC4 requires 8.0+. Outdated environments are the first cause of failures. We check the server and update the environment.
• Templates PHP → Twig. All .tpl.php files must be rewritten to .twig. Twig runs faster due to template compilation into PHP code, giving a page load speed boost of up to 40%.
• OCMOD → Events. Modifying the core via file patching has been replaced by the event system. Extensions are rewritten without altering source files, simplifying maintenance.
• Storage API changes. The storage folder structure and file handling have been completely overhauled. Paths need to be reconfigured.

Each of these issues requires a separate approach. During the audit, we determine the exact scope of work and risks.

How we perform the migration: a real case

Every project is unique, but there's a proven scenario. We migrated an auto parts store with 5,000 products, a custom module for discounted items, and 1C integration. First, the audit—we identified 12 custom extensions, 3 of which required a full rewrite. Then backup, data transfer via SQL, template adaptation over 2 weeks, testing on a staging server, and launch. Result: page load speed increased by 40% thanks to Twig and PHP 8. The customer experienced no downtime—the launch was seamless.

Adapting extensions to the Events System

Instead of patching files via OCMOD, we use events. Each extension is rewritten as an event handler class. Example: displaying a custom badge on the product page:

class ExtensionMyExtensionEventProductList {
    public function index(&$route, &$data): void {
        foreach ($data['products'] as &$product) {
            $product['custom_badge'] = 'Sale';
        }
    }
}

This approach eliminates conflicts between extensions and simplifies core updates.

What technical changes occurred in OpenCart 4?

Twig templates work twice as fast as PHP templates due to compilation, and the Events System makes extensions safer and easier to maintain. Learn more about Twig in the Twig documentation.

What's included in the work?

• Full audit of the current store with a detailed report.
• Export and transformation of data (products, orders, customers, settings).
• Adaptation of templates and all extensions to Twig and Events System.
• Configuration of the new Storage API and file transfer.
• Testing on a staging server with verification of all key scenarios.
• Documentation of changes and team training.
• One month of technical support after launch.

Process and timelines

1. Audit of the current store (extensions, settings, data volume).
2. Environment preparation (PHP 8.0+, server, staging).
3. Data export and transformation for OC4.
4. Adaptation of templates and extensions to Twig and Events.
5. Import and testing on staging server.
6. Launch and monitoring.

Guarantees and support

• Full backup and its verification.
• Transfer of products, orders, customers, and all settings.
• Adaptation of templates and all extensions.
• Configuration of the new Storage API.
• Testing of all key scenarios (cart, checkout, personal account).
• Documentation of changes.
• One month of technical support after launch.

Common migration mistakes: ignoring PHP extension incompatibility, skipping payment gateway testing, losing image links due to improper rsync. We ensure data integrity and uninterrupted operation.

Have a complex project? Contact us for an audit—we'll estimate the scope and timeline. Or leave a request for a consultation—we'll discuss the details.

Website Redesign and Migration: CMS Change, SEO Preservation

A client came to us 6 weeks after a self-attempted redesign: 'We moved from WordPress to Tilda, traffic dropped by 70%.' I opened Google Search Console — 847 pages returned 404, the URL structure had completely changed, not a single 301 redirect was in place. Yandex hadn't reindexed the new site yet, positions collapsed. Recovery took 4 months and resulted in significant revenue loss for the quarter. Our experience — over 7 years and 80+ successful migrations, we guarantee position retention with the right approach.

Why Do Migrations Break SEO?

Search engines have indexed specific URLs. If /catalog/shoes/nike-air-max-270 turned into /products/nike-air-max-270 without a 301 redirect — all the link equity, traffic, and rankings go nowhere. Google says 301 passes ~99% of PageRank, but in practice positions recover over 2–8 weeks, not instantly.

Commonly, SEO gets broken not out of malice, but because a developer doesn't view the URL structure as a public API. Here are typical breakages:

How to Recover Traffic After a Failed Migration?

If traffic dropped, act immediately:

1. Crawl the new site for 404s and compare with the pre-migration URL list.
2. Create redirects for all lost pages with traffic >0.
3. Check structured data and meta tags on a test sample.
4. Daily monitor Coverage in Search Console and positions for top 50 queries.
5. If after 2 weeks traffic does not recover — deep audit of redirects (transitivity, chains, loops).

In our practice, a large e-commerce site lost 50% of traffic when moving from Bitrix to React + Strapi. We restored 95% of redirects in three days, and within 3 weeks traffic returned to 90% of original.

What Does a Pre-Migration Audit Include?

Before starting development on the new site:

1. Full crawl of current site via Screaming Frog or Sitebulb. Get list of all indexable URLs with traffic from Google Search Console.
2. Export all pages with organic traffic >0 over the last 6 months — these are priority for redirects.
3. Record all external backlinks to specific pages — Ahrefs, Semrush.
4. Snapshot current positions for key queries — baseline for post-migration comparison.
5. Save Core Web Vitals from Search Console for the previous 90 days.

Table for recording:

Contact us for a detailed pre-migration audit — we will help identify all risks and create an action plan.

URL Mapping and Redirects

For projects with 200+ pages, we create a mapping table: old URL → new URL → status (301, merged with another page, deleted). Each row is verified: does the content actually migrate here?

In Laravel, redirects are handled via configuration file and middleware, not .htaccess — faster and more manageable. For WordPress → Next.js: redirects are set in next.config.js (static) and at the Nginx/CDN level for dynamic ones. Old .htaccess on shared hosting with 500+ lines of redirects is a special hell. Each redirect is checked sequentially, performance suffers. We move to Nginx map directive or Redis cache for dynamic lookup. More at Wikipedia: HTTP 301.

How to Migrate Content from Different CMSs?

WordPress → Headless CMS (Contentful, Strapi, Sanity): WordPress REST API or WP All Export to export posts, meta fields, media files. Migration script in Node.js: parse export, transform structure, upload via CMS API. Media files are reuploaded to new storage, links updated in content. Typical problem — shortcodes in WordPress content ([gallery id="123"]): need parser and transformation to new format.

1C-Bitrix → modern stack: Bitrix stores content in non-standard tables with IBLOCK_ELEMENT_PROPERTY. Direct SQL export via phpMyAdmin or Bitrix API. Transformation is the longest part due to specific Bitrix data structure.

Heavy WYSIWYG → structured content: Years of editing in FCKEditor/TinyMCE leave inline styles, non-standard tags, broken attributes. HTML sanitize + transformation to Markdown or Portable Text (Sanity) with manual check of problematic pages.

How to Preserve Technical SEO Elements During Migration?

Structured data (Schema.org) — if the old site had Product, Article, BreadcrumbList markup, they must be on the new site too. Google Search Console → Enhancement reports will show loss of rich snippets.

Sitemap XML: generated automatically, submitted to GSC a day after launch. Old sitemap remains until full reindexing.

hreflang for multilingual sites: if tags are lost during migration, conflicts between language versions in search results will start within weeks.

Open Graph and Twitter Card meta tags — often forgotten when changing template, pages stop displaying correctly when shared on social networks.

Launch and First Weeks Monitoring

DNS propagation: DNS switching takes up to 48 hours, plan launch with buffer. Cloudflare as DNS provider — propagation takes minutes, not hours.

After launch, monitor daily: Search Console → Coverage (indexing errors), Analytics → organic traffic, year-over-year comparison, crawl site for 404 errors.

First 2 weeks are critical. If traffic drops more than 30% — immediate audit of redirects and comparison with pre-migration crawl.

What the Service Includes

Results you receive:

1. Migration plan with URL mapping and redirects in Excel/Google Sheets format.
2. Configured 301 redirects at server level (Nginx/Cloudflare/Vercel).
3. Migrated content with integrity check: images, meta fields, links.
4. Structured data (Schema.org) on the new site, identical to old or improved.
5. SEO report: position trend at 1, 3, and 6 weeks after launch.
6. Coverage monitoring in Search Console with error notifications.
7. Guaranteed position retention: if traffic drops more than 15% within the first month — free audit and correction.

Timelines and Estimates

• Redesign with migration for a small site (up to 100 pages): 4–8 weeks.
• E-commerce migration with 500+ product pages: 8–16 weeks.
• Only technical migration part (redirects, metadata) without redesign: 1–3 weeks.

Cost is calculated individually based on scope.

Get a consultation for your project — we will respond within a day. Order a pre-migration audit of your site and receive a detailed proposal with a redirect plan. Contact us to discuss details.