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.
San Antonio, TX
Replatforming & Migration to Shopify in San Antonio, TX
Move a long-established San Antonio business onto Shopify without losing the rankings, the wholesale accounts or twenty years of order history.
Delivered remotely for brands across San Antonio and Texas.
Build · San Antonio
Why San Antonio brands come to us for this
- Full URL inventory including Spanish-language pages, each mapped one-to-one rather than redirected to the homepage
- Wholesale accounts, negotiated price lists and login access rebuilt and tested before cutover, not after
- Order history preserved so loyalty tiers, reorders and the accountant's reporting survive the move
- Subscription migration for pantry and coffee ship programmes handled with the payment gateway, not by asking customers to re-enter cards
- Catalogue cleanup that collapses years of duplicate boot widths and bilingual double-entries into proper variants
San Antonio has an unusual concentration of stores that have outlived their platform. A WooCommerce site bolted onto a WordPress blog in 2014. A Magento 1 install that was expensive then and is now a security liability. A BigCommerce store nobody has been able to edit since the developer stopped returning calls. In every case the business is fine and the platform is the problem — which is the cleanest migration case there is, and also the one most likely to be botched by someone in a hurry.
The risk is never the products. It is everything attached to them. Two decades of order history that the accountant and the loyalty programme both depend on. Wholesale accounts with negotiated pricing that must survive the move. Subscriptions on a monthly salsa or coffee ship that will churn instantly if a token migration goes wrong. Spanish and English URL variants that each rank for something. Recipe and blog content that quietly pulls in more organic traffic than the homepage.
So we run it as a data project with a launch attached. Field-by-field mapping from source to Shopify, a full URL inventory pulled from Search Console and server logs with every indexed address given a real target instead of a lazy homepage redirect, catalogue cleanup that usually removes a meaningful share of duplicate SKUs accumulated over years of manual entry, and repeated dry runs on a staging store until the data lands identically twice in a row. Cutover happens on a low-traffic window with the old store still standing behind it.
Local context
Replatforming a business older than the platform it is on
Migrating a thirty-year-old San Antonio family business is a different exercise from migrating a four-year-old DTC brand, and the difference is institutional memory. Pricing rules exist because a grocery buyer asked for them in 2009. A product is listed twice because two generations named it differently in English and Spanish. Boot widths were entered as separate products rather than variants, so the catalogue has four times the SKUs it needs. Someone in the family knows why every one of those decisions was made, and none of it is written down. Our first pass is interviewing that person, not exporting a CSV. We also protect two things this city's stores are unusually exposed to: bilingual URL history, where a Spanish page has been ranking for years and gets casually dropped in a migration, and wholesale login access, because a grocery or boutique account that cannot log in the morning after cutover is the phone call that defines the whole project.
Scope
What Migrate to Shopify includes
The same standard of work we run for every client — applied to a San Antonio 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 San Antonio store
We do not work off a rate card. Every San Antonio 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 San Antonio — your questions
Only if nobody looks for them, which is the usual failure. We pull the full indexed URL set from Search Console and server logs, which surfaces Spanish-language pages that never appeared in the site's own navigation, then map each to its equivalent on Shopify with the right hreflang and canonical setup. Bilingual sites carry more orphaned ranking pages than monolingual ones, so this step is longer here — and skipping it is where traffic disappears.
Usually not all of it, but the decision should be deliberate. Recent years matter for customer service, returns, loyalty tiers and reorder behaviour; older history often matters more for accounting than for the storefront and can live in an archive export. We agree the cut-off with you and your accountant up front, then migrate to it, rather than dragging a decade of noise into a new system by default.
That is the goal, and it takes a rehearsal. We recreate company accounts, price lists and terms on staging, then have a handful of your actual buyers log in and place a test order before cutover. Reset-password communication goes out on a schedule you approve, in both languages, and your sales contact is briefed to handle the first week. Wholesale disruption is the most expensive migration failure and it is entirely preventable.
Anything in your own peak. For pantry and gift brands that is the fourth quarter; for outdoor cooking it is spring into Father's Day; for western wear it is the stock show and rodeo run in February and the Fiesta weeks in April. We work backwards from your calendar to find a genuinely quiet window with room to fix surprises, and we do not move DNS the week before your biggest selling event.
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 San Antonio 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.