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.
Copenhagen
Replatforming & Migration to Shopify in Copenhagen
Moving a Danish shop to Shopify without losing the organic revenue, the accounting integration or the customer accounts.
Delivered remotely for brands across Copenhagen and Denmark.
Build · Copenhagen
Why Copenhagen brands come to us for this
- URL inventory from Search Console, crawl and server logs, including the several ways æøå slugs were historically encoded
- One-to-one redirect map covering legacy /da/, /de/ and /en/ paths rather than folding orphans into the homepage
- Catalogue cleanup that moves dimensions, materials and lead times out of description text and into real metafields
- Accounting and carrier integrations mapped before build: e-conomic or Business Central, PostNord and GLS, parcel shop selection
- Dry-run migrations reconciled on order, customer, VAT and wholesale balances before cutover is scheduled
Denmark has a deep bench of legacy webshop platforms, and a lot of Copenhagen brands are still on one: a DanDomain or Smartweb shop from the mid-2010s, a Magento 1 install nobody has dared touch since support ended, or a WooCommerce site that has accumulated thirty plugins and two developers' worth of undocumented decisions. They all work well enough to postpone the decision, and they all fail in the same direction — the cost of every change keeps rising until small merchandising ideas stop being worth asking for.
The two things that actually go wrong in a migration are dirty data and dropped URLs. Danish catalogues carry a particular version of the data problem: product titles in Danish with inconsistent compound spellings, dimensions living in free-text descriptions instead of fields, EAN numbers present on some variants and not others, and a decade of images named after camera exports. Getting that into a clean Shopify structure with real metafields is most of the work and most of the value, because it is what everything downstream — feeds, filters, search, SEO — depends on.
The URL problem has a local twist. Danish slugs are full of æ, ø and å, historically encoded in several different ways depending on the platform, and legacy Danish shops often have parallel /da/ and /de/ or /en/ paths that were never consistently canonicalised. Every one of those indexed URLs needs a mapped destination before launch, taken from Search Console, a crawl and server logs rather than guessed from a sitemap. A homepage redirect for anything unmatched is not a plan, it is a way of losing rankings quietly.
Local context
The integrations are the part people forget until the week of launch
A Danish shop is rarely just a shop. It is usually connected to an accounting system — e-conomic, Dinero or Billy at the smaller end, Business Central further up — plus a carrier setup that has to keep working: PostNord and GLS labels, parcel shop pickers at checkout, and often a freight partner for anything that will not fit in a van. There may be a stock feed to a physical shop in Indre By or Vesterbro, and a wholesale price file the trade team relies on. We inventory all of it in the first fortnight and decide, per integration, whether it is replaced by a native Shopify app, rebuilt as a private app, or retired because it duplicates something else. Then we run dry-run migrations against real data until the reconciliation is boring: order counts, customer counts, tax totals and open wholesale balances matching before anyone touches DNS. Cutover gets scheduled outside your season, and because we are eight hours behind, launch night here is your late evening, which in practice works well — the site goes live with our full day still ahead of us.
Scope
What Migrate to Shopify includes
The same standard of work we run for every client — applied to a Copenhagen 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 Copenhagen store
We do not work off a rate card. Every Copenhagen 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 Copenhagen — your questions
The export usually gives you products, customers and orders in a workable form, and almost never gives you a clean structured catalogue. Expect specification data to arrive inside description HTML, variant naming to be inconsistent, and image filenames to be unusable. We treat the export as raw material for a mapping exercise rather than as something to import directly, which is the difference between a migration and a copy of your existing mess.
They get handled deliberately. We decide a single canonical slug convention on Shopify, then map every historical variant of the old URL to it — encoded, transliterated and mixed-case forms included, because Danish shops usually have all three in the index. Skipping that step is one of the most common causes of a rankings drop after a Danish replatform, and it is entirely avoidable.
In most cases yes, through an established connector, but the detail matters more than the connection. VAT handling on domestic versus EU cross-border orders, credit notes for returns, and how wholesale invoices are posted all need agreeing with your bookkeeper before launch rather than discovered in the first month-end. We schedule that conversation early and test it against real orders in the dry run.
Only if it is planned as a DTC project with wholesale attached at the end. We migrate company accounts, price lists and open balances as first-class data, brief your stockists ahead of the switch with new login instructions, and keep the old ordering route reachable for a defined overlap where the setup allows it. Dealers tolerate a new portal; they do not tolerate a lost order history.
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 Copenhagen 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.