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.
Portland, OR
Replatforming & Migration to Shopify in Portland, OR
Migrations for Portland catalogues where the hard part is the spec data and the size-width matrix, not the theme.
Delivered remotely for brands across Portland and Oregon.
Build · Portland
Why Portland brands come to us for this
- Legacy spec attributes normalised into controlled metafield values, so filtering works on day one
- Size and width matrices consolidated out of the split-product workarounds the old platform forced
- Discontinued models mapped to successor products or retained spec archives, never to the homepage
- Subscription and club migration rehearsed separately, with card tokens and billing dates verified before cutover
- Historical order data reviewed by state during migration, so nexus exposure surfaces while the data is open
A Portland migration is rarely a design problem. It is a data problem wearing a design problem's clothes. Ten years of technical product data on Magento or WooCommerce arrives as free-text attributes, inconsistent width codes, three different ways of writing a fill weight, and material fields that were only ever meant for humans to read. Loaded straight into Shopify, all of that becomes unfilterable, and the store you paid for is worse at merchandising than the one you left.
So the mapping work comes first. Every attribute gets a decision: becomes a variant option, becomes a metafield with a controlled value list, gets normalised and merged, or gets dropped on purpose. Width codes get standardised. Sizes get one convention. Product families that were split across four legacy products because the old platform could not hold the matrix get consolidated so the reviews and links land on one page. Brands in this category routinely finish with a materially smaller SKU count and a better-merchandised catalogue.
Then URLs, which is where organic revenue actually goes missing. Legacy attribute and layered-navigation URLs, old blog paths, discontinued models that still rank for a spec query, warranty and manual PDFs that are linked from forums — all of it comes out of Search Console, Ahrefs and server logs and gets a target before cutover. Discontinued products are the Portland-specific trap: a 2016 boot that no longer sells still holds links and searches, and redirecting it to the homepage throws that away when it should go to the successor model or a retained spec archive.
Local context
The two things Oregon merchants get wrong at cutover
The first is tax. An Oregon business has never collected a state sales tax at home, so tax configuration tends to be treated as a checkbox during migration when it is actually the moment to look at where your buyers are. Economic nexus is triggered by sales into other states, thresholds differ, and a replatform is when the historical order data is already in front of everyone — so it is the cheapest possible time to see which states you have been crossing. We will configure Shopify Tax against the registrations you have; the registration and filing calls belong to your accountant. The second is the subscription base. Roasters, clubs and consumables brands carry the migration risk that matters most, because payment tokens do not always travel between processors and a botched move turns a healthy recurring base into a mass of failed charges. We plan that as its own workstream with its own rehearsal, and we do not cut over a subscription programme in the same window as the storefront if the calendar allows separating them.
Scope
What Migrate to Shopify includes
The same standard of work we run for every client — applied to a Portland 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 Portland store
We do not work off a rate card. Every Portland 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 Portland — your questions
Most do not, and blanket-redirecting them creates its own mess. We separate the ones with real evidence behind them — impressions in Search Console, referring links, log-file hits from crawlers or users — from the combinatorial noise that was never meant to be indexed. The evidenced ones get a target, usually a Shopify collection built deliberately for that attribute. The rest are allowed to 410 or fall out of the index, which is a cleaner outcome than pointing them all at a collection that does not match.
They get treated as assets rather than clutter. If there is a clear successor model, the old URL redirects to it and the successor page gets a line acknowledging the lineage, because that is what the searcher wanted. If there is no successor but the page still earns traffic or links, we keep it as an archive page with the specs and a route to the current range. Deleting them silently is how brands lose the long tail of spec searches they never realised they owned.
Sometimes, and it depends entirely on the processors involved and the gateway on each side. Where a token migration is supported we run it as its own rehearsal, verify billing dates and cadence on a sample, and watch the first two billing cycles closely. Where it is not supported, the honest plan is a communicated re-authorisation campaign with a clear reason and an incentive to act, run before the storefront cutover rather than after. Pretending it will be seamless when it will not be is how a subscription base gets damaged.
They are inventoried with everything else, because for hardgoods and tools brands those files often carry more links than the product pages do. PDFs get rehosted with redirects from the old paths, and where a manual is genuinely being searched for we usually recommend an HTML version alongside it so the content is indexable and can be cited by an AI answer. Warranty and repair pages get rebuilt as real templates rather than dumped into a single legacy page.
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 Portland 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.