What had to change
The store had to leave PrestaShop without losing the catalogue knowledge accumulated inside it. Product relations, customer data, custom fields, SEO metadata and legacy URLs all had to survive the move—and the new storefront still had to respond quickly under a large catalogue.
The decisive move
I treated migration as a data-integrity system, not a one-time export. Every source field and relationship was audited first, mapped to the WooCommerce model, then moved through repeatable batches with validation at each boundary. URL behavior and cache strategy were designed as part of the migration rather than patched in after launch.
What the build covered
The work covered batch import tooling, custom mappings, WooCommerce API registration, customer and SEO metadata, rewritten legacy routes and Redis object caching for frequently requested product data.
Why it matters
danielgerard.fr moved to its new platform with its catalogue structure, discoverability and operational data accounted for. The result shows how I handle high-consequence backend work where continuity matters more than a flashy rebuild.