ps_install and the new Symfony tables in 8.x)?
Did your PrestaShop migration
break everything?
we fix it without starting over.
Audit and recovery of failed PrestaShop 1.6, 1.7, 8, 9 migrations
1.7 → 8 or 8 → 9 migration that blew up: modules throwing fatals, blank BO, payments down, SEO in free fall. We audit the current state, quote by order of criticality, recover piece by piece. Without starting from scratch, without breaking it all again.
The symptoms we find after a failed migration
Across 14 recoveries delivered in 2025-2026, here's the damage we consistently encounter, ranked by business criticality. The more this list rings a bell, the wider the recovery scope.
- • Stripe/PayPal payment not working
- • "Order" button doesn't respond
- • Carrier invisible at checkout
- • Stock displayed incorrectly (negative, empty)
- • Order emails not sent
- • VAT miscalculated
- • Blank BO after login
- • Modules listed as "disabled" en masse
- • Catalogue import / export crashing
- • Broken product search
- • Multi-store no longer working
- • Custom hook no longer displaying
- • Canonical URLs changed without 301 redirects
- • Sitemap.xml missing or wrong
- • Friendly URLs broken
- • Wrong hreflang (multilingual sites)
- • Performance degraded (LCP > 3s)
- • Robots.txt left as "Disallow: /" by default
- • "Best sellers" home block broken
- • Home slider disabled
- • Custom theme CSS not loaded
- • Google fonts missing
- • Favicons / OG images deleted
- • Customer reviews not displayed
Full audit in 45 min
Not a generic checklist. A real prioritised diagnostic that distinguishes what's losing you revenue today from what can wait.
error_log + php-fpm.log over the last 7 rolling days. PrestaShop debug mode temporarily enabled on 3 key pages (home, product, checkout). List of fatals, deprecated, warnings.
/override/: parent class signature comparison vs current version.
Pricing stated up-front
Audit free. For the recovery, you know exactly what it costs before we touch the code.
Post-migration audit
- Inventory of modules / overrides / theme
- Identification of business-critical errors
- Prioritised + quoted recovery plan
- You decide what we tackle
Progressive recovery
- Backup files + DB before each step
- Staging for risky fixes
- Fix by criticality (payment → checkout → SEO → cosmetic)
- Client validation at each step
- 30-day warranty on each fix
Performance maintenance
- 2 h/month cumulative for spread-out recovery
- Daily automated backups externalised
- Module compatibility watch ahead of next upgrade
- Systematic staging tests on the next upgrade
"Failed migration" is not...
If you're still on 1.7 and want to move up to 8.x without breaking anything, that's a new migration project: staging tests, upstream module audit, planning. It's not recovery, it's prevention. Request a quote.
If just one 500 error appeared after migration, that's a targeted troubleshoot, not a full recovery. Dedicated page, less expensive.
500 page → ❌ Not just a slower siteIf the migration went fine but the site is just slower than before, that's a performance topic, not a recovery. Dedicated page.
Performance page →Failed PrestaShop migration — frequently asked questions
Tools::displayPrice() methods removed in 8.x, renamed hooks. Number one cause on 1.7 → 8/9. (2) Overrides in /override/ inheriting from core classes whose signature changed. (3) Custom theme with Smarty variables or hooks removed. Bonus: 70% of post-migration incidents come from an auto-upgrader run without staging.robots.txt hasn't been reset to Disallow: / by default (badly cleaned staging case). (4) Core Web Vitals audit. Return to normal typically within 30-60 days after redirects.Other issues I handle
Failed migration in progress? Let's pick it up.
Free 45-min post-migration audit: we list the damage, we quote, we prioritise. Quote within 24 business hours.