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.
Madrid
Replatforming & Migration to Shopify in Madrid
Moving a Spanish store to Shopify without losing the Spanish-language URLs that took years to rank.
Delivered remotely for brands across Madrid and Spain.
Build · Madrid
Why Madrid brands come to us for this
- Full URL inventory across Spanish-language category, attribute and product paths, mapped one-to-one before cutover
- Accented and ñ-bearing slugs handled at the encoding level so redirects resolve instead of quietly 404ing
- PrestaShop, Magento and WooCommerce exports normalised — duplicate SKUs and empty attributes cleaned, not carried over
- IVA rates, tax-inclusive display and OSS configuration reproduced and tested in staging against real order data
- Spanish carrier and fulfilment integrations rebuilt and proven in a dry run before DNS moves
Spain has a platform history that most of Europe does not. PrestaShop took deep root here, Magento 1 stores that were never upgraded are still trading, and a long tail of WooCommerce builds sits on top of hosting nobody has logged into since 2019. That history shows up in the migration in a specific way: the URL structure is Spanish, keyword-rich and deeply nested — category, subcategory, attribute, product — and every one of those paths may be carrying organic revenue. Losing them is how a replatform quietly costs a year of SEO.
So we treat this as a data and URL project that happens to finish with a new storefront. Every indexed path pulled from Search Console for the .es property, from your crawler and from server logs, then mapped one-to-one against the Shopify structure. Accented and ñ-bearing slugs get particular attention, because that is where a careless export produces mojibake, duplicate paths and redirects that resolve to a 404 with a 200 status. Anything without an obvious target gets a decision made by a human rather than a blanket redirect to the homepage.
The other half is the operational tail: invoicing that has to stay compliant and sequential across the cutover, IVA rates and tax-inclusive display reproduced correctly, an OSS position that must not break mid-quarter, carrier integrations for the Spanish couriers your fulfilment depends on, and a customer base whose accounts and order history they expect to still be there. None of that gets reconnected on launch night. It gets rehearsed in staging against real orders until the delta report comes back clean.
Local context
Cut over in the dead weeks, not into the sales
The Spanish trading calendar makes the cutover date a genuine commercial decision rather than a scheduling preference. January is the worst month you could pick: Reyes gifting runs to 6 January and the rebajas begin immediately after, so a fortnight of full-volume trading sits exactly where a replatform is most fragile. The summer rebajas take out a second window. What Madrid gives you in exchange is August — a stretch when the city genuinely slows, order volume drops, and the blast radius of a bad hour is at its smallest. We plan dry runs through July, cut over in the quiet part of August or in a low-traffic week in autumn, and then run the post-launch crawl watch straight through into the pre-Christmas ramp so anything that broke is found while there is still time to fix it before the gifting peak arrives.
Scope
What Migrate to Shopify includes
The same standard of work we run for every client — applied to a Madrid 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 Madrid store
We do not work off a rate card. Every Madrid 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 Madrid — your questions
Different rather than harder. PrestaShop stores tend to carry a lot of custom module logic and attribute combinations that have no clean Shopify equivalent, so the mapping work is about deciding what becomes a variant, what becomes a metafield and what quietly gets dropped. Magento stores usually have cleaner data but more integrations. Either way the risky part is the same: the URL inventory and the redirect map, not the product export.
It has to stay continuous, and that is a planning item rather than a technical accident. We agree the sequence handover with your gestoría before cutover, configure the invoicing app or integration to pick up from the correct number, and make sure the tax fields Shopify passes into it are complete for both domestic and OSS orders. We also keep the legacy system readable for the statutory retention period rather than switching it off the week after launch.
Some of them, not all. Shopify's URL structure is fixed in places — products and collections live under prefixes you cannot rename — so a deeply nested PrestaShop path cannot be reproduced verbatim. What we can do is preserve the slug itself where it carries the ranking, keep the Spanish keywords in it, and redirect every legacy path one-to-one so the equity transfers. In practice a clean redirect map protects rankings far better than a contorted attempt to fake the old structure.
Market by market, with the tax position checked first. We map the existing country setup onto Shopify Markets, confirm which countries are OSS-declared and which carry local registrations, rebuild per-country pricing and language variants, and get hreflang correct across every locale before the switch rather than after. Multi-country migrations fail most often on hreflang and duplicated language paths, so that is where the pre-launch crawl focuses hardest.
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 Madrid 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.