Migration Audit & Data Map
Field-by-field mapping of products, variants, customers, orders, blogs and metafields from source to Shopify, with a documented plan for everything that has no equivalent.
Paris
Replatforming & Migration to Shopify in Paris, France
PrestaShop, WooCommerce or Magento to Shopify, with every French URL you have ever ranked for accounted for before anyone touches DNS.
Delivered remotely for brands across Paris and France.
Build · Paris
Why Paris brands come to us for this
- Full URL inventory across accented paths, module-ID product URLs and years of layered-navigation filter pages, mapped one to one
- PrestaShop and WooCommerce module data translated into real Shopify metafields: appellation, ABV, allergens, shelf life, origin, materials
- Second-hand and consignment records carried across intact, so margin-scheme VAT history remains evidence rather than a lost price column
- Rehearsed dry-run migrations into staging with a delta report on counts, prices, stock and customer tags before anyone approves the real run
- Cutover scheduled into the summer lull and away from both soldes windows, on a runbook written for your working morning
France has a deeper installed base of PrestaShop and self-hosted WooCommerce than most markets, and the stores that grew on them share a profile: a decade of accumulated category pages, a module stack nobody dares update, and a developer relationship that ended badly. The move to Shopify is worth doing, and the thing that decides whether it goes well is not the theme. It is the URL inventory and the state of the catalogue.
French legacy sites carry specific redirect hazards. Accented and hyphenated category paths that were generated in three different conventions across three redesigns. Product URLs carrying a numeric module ID that has no equivalent on Shopify. Faceted navigation that spawned thousands of indexable filter combinations, half of which now hold real backlinks. Layered navigation URLs in one language and canonical tags pointing at another. The full list comes from Search Console, a crawl and your server logs, and is mapped one to one and get the exceptions decided rather than swept into a homepage redirect.
Then the data. Vintage and antiques dealers carry single-quantity records and second-hand margin-scheme VAT history that has to survive the move as evidence, not just as a price field. Perfumery and food catalogues carry ingredient, allergen, shelf-life and origin attributes that live in a module today and need to be real Shopify metafields tomorrow. Wine catalogues carry vintage, appellation and ABV. We map every field before a single import runs, and we rehearse the whole thing into staging until the delta report comes back boring.
Local context
Cutting over on a French calendar
There are two windows in a French year when a replatform cutover is a bad idea and one when it is close to ideal. The bad ones are obvious: the winter and summer sale periods, because a promotional window fixed nationally is not a period you can quietly repeat if a redirect map turns out to have a hole in it, and the run into December. The good one is the summer lull, when traffic drops as the country goes on holiday and a two-week stabilisation period costs you the least revenue it will cost you all year. We schedule the audit and data cleanup through spring, rehearse migrations across June, cut over in the quiet weeks, and use the remaining time before the rentrée to watch index coverage recover with real headroom. Add the eight-hour offset and the cutover runbook gets written for your morning rather than ours, with named owners on both sides and a rollback nobody has to improvise at midnight.
Scope
What Migrate to Shopify includes
The same standard of work we run for every client — applied to a Paris brand’s realities.
Full service detailFull URL Inventory & Redirect Map
Every indexed URL pulled from Search Console, Ahrefs and server logs, then mapped one-to-one. Anything without a target gets a decision, not a homepage redirect.
Catalogue Cleanup
Deduplication, variant restructuring, image renaming and metafield normalisation. Most brands cut 15-30% of their SKU count in this step and lose nothing.
Dry-Run Migrations
At least two full rehearsals into a staging store with an automated delta report on record counts, prices, inventory and customer tags before anyone approves the real one.
Integration Rebuild
ERP, 3PL, ESP, reviews, loyalty, subscriptions and tax reconnected and tested against real orders in staging. Nothing gets reconnected on launch night.
Post-Launch SEO Watch
Sixty days of daily crawl monitoring, index coverage tracking and 404 alerting, with a weekly report comparing organic sessions and revenue against the pre-migration baseline.
Scoped and quoted for your Paris store
We do not work off a rate card. Every Paris engagement starts with a fixed statement of work — named deliverables, named dates, one number — written after we have looked at your store, not before. If a smaller first step would serve you better, we will say so.
Get this scopedHow it runs
From kickoff to results
Audit & Feasibility
We inventory your data, integrations, custom logic and organic footprint, then quantify the risk in each. You get a fixed scope and a timeline before committing.
Data Mapping & Cleanup
Source-to-target mapping for every field, plus catalogue hygiene work. This is the least glamorous phase and the one that decides whether the project succeeds.
Build & Rehearse
Theme build runs in parallel with repeated dry-run migrations. Each rehearsal produces a delta report and a shorter list of exceptions than the last.
Cutover
A rehearsed runbook with named owners, timed steps, a freeze window and a documented rollback. Executed at your lowest-traffic hour, not on a Friday.
Stabilise & Monitor
Sixty days of crawl monitoring, redirect verification and revenue comparison. We stay until organic is at or above where it started.
Proof
Migrate to Shopify results
Anonymised under NDA. Figures pulled from the client’s own analytics.
Premium Skincare (DTC)
8-figure DTC brand, ~140 SKUs, US + CA · Shopify Plus (migrated from Magento 2)
Magento 2 cost $9k a month in hosting, extensions and emergency dev before a single feature shipped. Mobile LCP sat at 5.4 seconds and mobile converted at less than half the desktop rate across 68% of sessions. The named constraint: 11,412 indexed URLs and a top-3 organic position on their hero category, so a migration that lost rankings would cost more than the platform ever saved.
+41%mobile conversion rate1.62% to 2.28% over the first 90 days post-launch
5.4s → 1.8smobile LCP75th-percentile CrUX field data, not lab
+27%organic sessionssix months post-migration vs. pre-migration baseline, branded queries excluded
$108k/yrplatform cost removedhosting, extension licences and the standing emergency dev retainer
B2B Wholesale (Janitorial & Packaging Supply)
~$18M/yr wholesale, 6,400 SKUs, 900 trade accounts, US · Shopify Plus with B2B on Shopify (migrated from a custom .NET portal)
Ninety-one percent of orders arrived by phone, email or fax and were rekeyed into the ERP by four full-time staff. Order-entry errors ran at 3.8%, and every one of them meant a redelivery and a credit note. The named constraint: 900 accounts on 47 negotiated price lists with net-30 and net-60 terms. No account could ever see another's pricing, and nothing could break during the fiscal year-end freeze.
+4.1%average order valuemodest on purpose. Trade buyers order what they need, so AOV was never the target
9% → 63%of orders placed self-servewithin 10 months of launch
3.8% → 0.4%order-entry error rateroughly $240k/yr of redelivery and credit-note cost removed
+$620kannual gross profit impactfour order-entry roles redeployed into account management, which opened 71 new trade accounts
In their words
Clients on this work
Organic back to level in 5 weeks
“Magento to Shopify Plus with 14,000 SKUs and a subscription base we could not afford to break. We took the usual dip for about three weeks and organic was back level by week five — that was the entire ballgame for me. One honest gripe: discovery ran three weeks past the SOW and I had to push to get the revised timeline in writing. Once the build actually started they hit every single date.”
VP eCommerceSupplements DTC brand, ~$28M/yr · Miami, FL
Verified via Shopify Partner referralFAQ
Migrate to Shopify in Paris — your questions
Yes, but they have to be enumerated rather than pattern-matched, because the ID carries no information Shopify can rebuild a handle from. We export the full product and category table with its IDs, join it to the crawl and the Search Console export, and produce an explicit one-to-one map. Anything with no target gets a decision from you rather than a default. This is the least interesting part of a migration and the part that decides whether organic revenue survives it.
It complicates the data, not the storefront. Second-hand goods sold under a margin scheme need purchase-side records preserved alongside the sale, and those usually live in a bookkeeping module rather than the shop database. We map what exists into order metafields and historical records so the trail stays intact and exportable, and we tell you early where a source system holds something Shopify has no field for so your accountant can decide where it should actually live.
Only if the language routing is treated as an afterthought. French sites we take over routinely have canonical tags, hreflang and internal links disagreeing about which locale a page belongs to, and a migration either fixes that or entrenches it. We rebuild the locale structure deliberately in Shopify Markets, keep the French URLs that carry equity, and confirm recovery in Search Console coverage per language rather than looking at one national total.
Less than you fear and differently than you expect. A large share of PrestaShop and WooCommerce modules exist to patch things Shopify does natively, and those simply disappear at migration. What genuinely needs a plan is pickup-point carrier integration, instalment payment, age verification, accounting and stock sync, and anything holding structured product attributes. We inventory the stack in the audit and tell you which items are native, which need an app, and which need to be built.
Not if the redirect work is done properly. We map every indexed URL one-to-one before cutover and monitor index coverage daily for sixty days after. Expect a two to four week dip while Google recrawls, then recovery. Brands that skip the URL inventory are the ones that lose rankings permanently.
Ten to sixteen weeks for a mid-market catalogue. Magento 2 with heavy customisation, B2B pricing or an ERP dependency runs sixteen to twenty-four. The catalogue cleanup phase drives the timeline far more than the theme build does.
Order history, yes, imported as historical records with line items, fulfilment status and notes intact. Password hashes cannot transfer between platforms for security reasons, so customers set a new password on first login. We handle that with a pre-launch email sequence so it lands as expected.
Next step
Migrate to Shopify for your Paris brand.
Thirty minutes with the strategist who would actually run your account. We screen-share your store, read your data live, and tell you the three highest-value things we can see from the outside.
Shopify or Shopify Plus stores doing $150k/mo or moreFounder, CEO or eCommerce lead on the callNo deck and no pitch — we open your store instead
Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.