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.
Amsterdam
Replatforming & Migration to Shopify in Amsterdam
Magento, Lightspeed, CCV Shop or WooCommerce to Shopify, with your Dutch URLs, your VAT setup and your marketplace feeds intact.
Delivered remotely for brands across Amsterdam and Netherlands.
Build · Amsterdam
Why Amsterdam brands come to us for this
- Dutch and English URL trees inventoried and redirected separately, with hreflang pairs verified after cutover as their own check
- Magento attribute sets, configurable products and multi-store views mapped to Shopify variants and metafields field by field
- iDEAL and the rest of the Dutch payment mix live and tested in staging before the store takes its first real order
- Per-market VAT rates and OSS thresholds configured during migration, so the first quarter after launch files cleanly
- bol.com and comparison feeds rebuilt against the new URL structure so marketplace listings do not go dark on launch day
The Netherlands has one of the deepest Magento installed bases in Europe, and it shows in the inbox. A large share of the replatform conversations we have with Amsterdam brands start the same way: a heavily customised Magento 2 store, a hosting bill that grew faster than revenue, a developer relationship that ended, and a catalogue nobody has been able to safely restructure in four years. The rest come off Lightspeed or CCV Shop, where the store works but the roadmap has run out, or off WooCommerce that outgrew its hosting.
Whichever the origin, the two things that sink a Dutch migration are the same. Dirty catalogue data, because a Magento store with a decade of history carries duplicate SKUs, orphaned attribute sets and product copy that exists in Dutch but not English or the reverse. And dropped URLs, which here means two language trees rather than one: every /nl/ path and every English equivalent, plus the category filter URLs that a previous SEO deliberately got indexed. We pull the full inventory from Search Console, a crawl and your server logs, and map it one to one before anyone books a cutover date.
The third workstream is the one that is specific to selling from here, and it is not a theme problem. VAT configuration per market so OSS filing does not break in the first quarter after launch. iDEAL live and positioned first from hour one, because a Dutch store without it on day one loses domestic conversion immediately. Marketplace and comparison feeds rebuilt and revalidated, since a bol.com listing pointing at a dead product URL is a channel outage nobody gets an alert about. Carrier integrations and pickup-point selection re-tested against real orders in staging, not on launch night.
Local context
Two language trees, one redirect map, and a cutover that is not in November
A single-language migration has one URL inventory. A Dutch brand selling in Dutch and English has two, plus whatever hreflang pairing existed before, and the failure mode is subtle: the Dutch pages redirect cleanly, the English ones land on Dutch equivalents, and six weeks later the cross-border organic that was quietly funding Germany has evaporated. We inventory and map each language tree separately, then verify the hreflang pairs post-cutover as a distinct check rather than assuming redirects covered it. Timing matters just as much. The Dutch retail year has an early peak because Sinterklaas falls on 5 December, so the freeze window here starts earlier than a US or UK brand would plan for. We aim cutover at January through March or the back half of spring after King's Day, and if a client insists on autumn we will say plainly which weeks we are not willing to touch DNS in.
Scope
What Migrate to Shopify includes
The same standard of work we run for every client — applied to a Amsterdam 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 Amsterdam store
We do not work off a rate card. Every Amsterdam 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 Amsterdam — your questions
Data carries over; custom modules do not. Products, variants, customers, order history, blog content and media all migrate. Every custom module gets a decision instead of a translation: replaced by a native Shopify feature, rebuilt as a Function or app extension, or retired because it was solving a Magento problem you no longer have. In practice a good share of Dutch Magento customisation turns out to be catalogue and pricing logic that Shopify handles natively, which is the cheapest outcome available.
They need treating as a live sales channel with its own cutover plan, not as an afterthought. The feed connector changes, the product identifiers have to line up, and the URLs behind the listings move. We rebuild and validate the feed against the staging store, then switch it in a controlled window with stock and pricing reconciled on both sides. The risk you are managing is not a broken listing, it is a listing that keeps selling stock the new store does not think it has.
Yes, and the discipline is exporting cleanly on both sides of the line. Your old platform holds the transaction record up to cutover and Shopify holds it after, so the return for that period is assembled from two sources. We make sure the new store applies the correct destination VAT rate per market from the first order, and that order exports carry the country and rate fields your accountant needs. Coordinate the date with whoever files for you; it is a fifteen-minute conversation that avoids a very long one.
Usually yes on the data side and no on the expectations side. The catalogue is generally cleaner and there is far less custom logic to unpick, so the technical lift is smaller. What catches brands out is that some conveniences they took for granted are configured differently on Shopify, and the Dutch-market apps they relied on for shipping, invoicing or returns have different equivalents. We map that app-for-app during the audit so nobody discovers a missing workflow in launch week.
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 Amsterdam 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.