Modernize without breaking a mature business
The legacy sites contained years of catalog data, commerce rules, SEO authority and operational dependencies that could not simply be discarded.
eCommerce migration case study · Legacy modernization · Retail replatforming
Legacy eCommerce Migration to Shopify
This eCommerce migration case study covers the modernization of two established retail platforms from custom Microsoft web applications to Shopify. Pulse Uniform moved from Classic ASP + SQL Server and JustLabcoats from ASP.NET + SQL Server, while preserving business-critical data, complex commerce rules, CRM operations, SEO equity and brand continuity.
2 production migrations250K+ SKUs at Pulse Uniform2,000+ pagesClassic ASP / ASP.NET + SQL Server → Shopify
01 · Executive overview
Legacy eCommerce migration meant moving years of commerce operations—not just two websites.
Both brands had long-running custom eCommerce platforms with business knowledge embedded in the code, database, product structure and day-to-day operating processes. Pulse Uniform—the larger and more business-critical property—had a particularly complex footprint: more than 250,000 SKUs, over 2,000 pages, extensive search-engine visibility, custom pricing and promotion logic, gift-card processes, product categorization, made-to-order products and product-personalization requirements.
The modernization program therefore treated Shopify as the new commerce foundation while carefully translating the existing business model into a maintainable platform architecture. My hands-on scope covered the full migration lifecycle: product and order data, product images, customer history, SEO architecture, redirects, canonical URLs, sitemaps, robots directives, structured data, analytics continuity, Google Search Console, Merchant Center, taxes, shipping, payments, notifications, custom attributes, storefront performance, QA, checkout validation, production cutover, rollback planning and post-launch monitoring.
Replatform selectively
Use Shopify for the commerce foundation, retain useful internal systems, and custom-build only where the businesses genuinely required differentiation.
Protect continuity
Preserve product discovery, search visibility, customer experience, operational workflows and business data throughout the transition.
The migration target was Shopify. The real engineering problem was preserving the commercial knowledge, search equity and operational continuity accumulated over years of running the businesses.
02 · Two implementations
One modernization strategy applied to two different generations of legacy eCommerce.
Pulse Uniform
- Legacy platform
- Classic ASP + SQL Server
- Target
- Shopify
- Catalog scale
- 250K+ SKUs
- Content footprint
- 2,000+ pages
- Primary complexity
- SEO, catalog scale, pricing/promotions, product customization, redirects, merchandising and operational continuity
JustLabcoats
- Legacy platform
- ASP.NET
- Target
- Shopify
- Source data
- SQL Server
- CRM continuity
- Shopify synchronization retained
- Primary complexity
- Legacy modernization, data migration, performance, rebranding and marketing enablement
03 · Business challenge
Pulse Uniform was a commerce operating system disguised as a website.
The Classic ASP storefront, backed by SQL Server, was only the visible layer. Behind it were product and SKU structures, vendor relationships, pricing updates, promotions, discounts, gift-card processes, categories, SEO landing pages and merchandising rules developed over years of operating in the medical-uniform market.
This was not a conventional retail website migration; it was the replatforming of a mature commerce operating system with years of embedded business logic. With more than 250,000 SKUs and over 2,000 pages, a simplistic “export and import” migration would have created significant risk. The URL structure was also fundamentally different from Shopify, making search visibility and redirect coverage a first-class engineering and business concern.
250K+ SKUs required careful mapping, classification and validation rather than one-off manual product setup.
Pricing, promotions, discounts, gift cards and product-specific purchasing behavior had to be translated into the Shopify operating model.
A large, established URL footprint meant migration mistakes could affect valuable organic search traffic.
Embroidery, logo personalization and made-to-order length/size options required product behavior beyond a basic catalog.
CRM, product setup, marketing, merchant feeds and internal workflows still had to function after the storefront changed.
Both Pulse Uniform and JustLabcoats were rebranded while the underlying commerce platforms were being modernized.
04 · My role
Hands-on ownership across architecture, migration, SEO, Shopify engineering and production release.
My responsibility extended across the complete replatforming lifecycle rather than stopping at storefront development. I analyzed the legacy businesses, recommended the Shopify direction and theme foundation, designed catalog and data mappings, implemented commerce functionality, managed SEO-sensitive migration work, configured the operational commerce stack, coordinated integrations, validated the customer journey and supported the production cutover and post-launch period.
Related consulting capabilities: legacy modernization, eCommerce systems and enterprise integration. You can also explore my enterprise software architecture approach.
Business & platform design
Translate legacy commerce rules, catalog structures, operational dependencies and executive requirements into the target Shopify operating model.
Data, catalog & history
Plan and execute migration of products, images, customers, historical orders, product attributes, categorization and related business data.
Search-safe replatforming
Handle 301 mappings, canonical URLs, sitemap transition, robots directives, metadata, structured data, Search Console and launch monitoring.
Shopify engineering
Configure taxes, shipping, payments, notifications, Shopify Markets where applicable, custom product options, metafields and storefront behavior.
Performance & end-to-end QA
Validate theme performance, responsive behavior, search/filtering, product journeys, checkout, feeds and critical operational workflows.
Cutover & production support
Run staging, coordinate domain transition, prepare cutover and rollback plans, validate launch readiness and monitor the platform after go-live.
05 · Modernization architecture
Replace the commerce layer while preserving the systems and business knowledge that still mattered.
Legacy estate
Pulse UniformClassic ASP + SQL Server
Large catalog · custom commerce rules · SEO footprint
JustLabcoatsASP.NET Storefront
Legacy commerce · SQL Server · operational history
→
Modernization program
Discovery & mappingCatalog · URLs · Rules · Data
Understand what must move, transform, redirect or remain integrated
StagingShopify implementation
Theme foundation · rebranding · configuration · custom commerce
ValidationSEO · Data · Operations
Redirects · feeds · CRM · product behavior · launch readiness
→
Target operating model
CommerceShopify Stores
Modern storefronts · merchandising · campaigns
Connected operationsCRM & Business Systems
Operational continuity through integration
Growth ecosystemSEO · Merchant · Marketing
Search visibility · product feeds · campaign operations
Replatform, don’t indiscriminately rewrite
Shopify became the commerce foundation while useful enterprise systems could continue doing the jobs they already handled well.
Migration is a data-and-rules problem
Products, URLs, pricing, promotions and operational behaviors were treated as business assets—not simply website content.
Cutover begins before launch day
Staging, validation and redirect preparation reduced the risk of discovering critical issues only after traffic had moved.
06 · Catalog engineering
250K+ SKUs meant the catalog had to be redesigned for operational reality—not merely imported.
Pulse Uniform’s catalog included vendor-supplied products alongside custom and made-to-order items. Product categorization, variant logic and SKU structure affected merchandising, search, inventory, CRM integration, reporting and the product-setup team’s daily work.
I worked closely with the product team to map the legacy structures into Shopify and to define workable SKU approaches for items that did not naturally fit the standard vendor-product model.
LegacyProducts & Vendor Data
→AnalysisClassification & Mapping
→DesignSKU & Variant Strategy
→ShopifyProducts · Variants · Collections
→OperationsCRM · Product Setup · Reporting
07 · Custom commerce requirements
Shopify provided the foundation. Business-specific purchasing behavior still needed engineering.
Some medical-uniform products could not be modeled as a simple product with size and color. The new storefront needed to support personalization and made-to-order scenarios while keeping the buying experience understandable.
Vendor-supplied products
Product → size/color variant → price → cart.
Embroidery & logo options
Product → variant → embroidery/logo configuration → personalization details → cart.
Custom length & size
Products requiring non-standard length, size or other made-to-order choices were modeled separately from routine vendor inventory.
A successful SaaS replatforming does not force every business rule into the platform’s default model. It identifies where configuration is enough and where the business genuinely requires custom behavior.
08 · SEO preservation
Protecting years of organic search equity was a migration requirement—not a post-launch task.
Pulse Uniform’s established search visibility was a major business asset. Because the Classic ASP URL structure differed substantially from Shopify’s routing model, URL migration received dedicated planning rather than being left to generic redirects after launch.
The work included cataloging important legacy URLs, mapping them to their new destinations, implementing redirect coverage and coordinating SEO requirements with the broader migration and rebranding work. The objective throughout was to minimize avoidable loss of search visibility during the platform transition.
01Legacy URL inventory
→Understand the existing page and product footprint.
02Destination mapping
→Define where high-value legacy routes should land in Shopify.
03301 redirect strategy
→Preserve user and search-engine continuity where URL structures changed.
04Launch validation
Check the transition alongside domain, storefront and SEO teams.
09 · Migration execution
Shopify migration execution across data, SEO, commerce and production cutover.
The migration was executed as a coordinated set of workstreams rather than a single storefront build. Each stream had its own failure modes: search traffic could be lost, catalog relationships could break, checkout configuration could fail, historical data could be missed, or a cutover could leave the business without a safe recovery path. I worked hands-on across all four areas.
01
SEO & discovery continuity
Protect organic visibility and measurement.
- 301 redirect mapping
- Canonical URL strategy
- XML sitemap transition
- robots directives
- Google Search Console monitoring
- Analytics continuity
- Meta titles & descriptions
- Structured data
02
Commerce & data migration
Move the business data and commercial configuration.
- Product image migration
- Customer migration
- Order-history migration
- Taxes
- Shipping rules
- Payment configuration
- Email notifications
- Shopify Markets where applicable
- Metafields & custom product attributes
03
Storefront engineering & QA
Validate the actual customer buying experience.
- Theme performance
- Mobile QA
- Checkout testing
- Search & filter behavior
- Feed validation
- Embroidery & logo options
- Made-to-order configurations
- SKU / catalog validation
04
Release engineering
Move production traffic with a controlled recovery path.
- Pre-launch staging
- Cutover plan
- Rollback planning
- Domain & DNS transition
- Launch validation
- Post-launch monitoring
- Search / feed health checks
- Operational continuity checks
A successful replatforming is not complete when the new storefront renders. It is complete when search engines, customers, payments, feeds, data, operations and internal teams continue working after production traffic moves.
10 · Staging, theme & rebranding
Start from a strong Shopify foundation, then invest custom effort where it creates business value.
Build before cutover
The new Shopify implementation was prepared and validated in a staging environment before the live domain was moved.
Buy vs. build deliberately
I evaluated professional Shopify themes, selected the foundation closest to business requirements and presented the recommendation to executive leadership.
Avoid unnecessary reinvention
Minor theme customization and business-specific functionality were layered onto a proven storefront foundation instead of rebuilding standard commerce capabilities from scratch.
Modernize the customer experience
Both Pulse Uniform and JustLabcoats were rebranded as part of their broader platform modernization.
Coordinate production cutover
Domain configuration was handled as part of the controlled move from the legacy storefront to Shopify.
11 · Data & operational continuity
The new storefront still had to connect to the history and systems the business depended on.
The modernization included migrating core commerce data and maintaining integration with the existing CRM rather than treating Shopify as an isolated replacement. The hands-on migration scope included products, product images, customer records, historical orders, categorization, custom attributes/metafields and the supporting data required by the new storefront. For JustLabcoats, Shopify order, risk and customer information was synchronized back into the CRM through GraphQL.
Operational continuity also required configuring the commercial environment around that data: taxes, shipping rules, payment methods, customer email notifications and Shopify Markets where applicable. The architecture principle remained consistent—replace the customer-facing commerce layer while preserving valuable operational systems and data flows wherever replacing them would add risk without business benefit.
ShopifyCommerce Data
APIGraphQL
IntegrationSynchronization
→Enterprise operationsExisting CRM
12 · Merchant & growth continuity
Migration also had to protect the channels that brought products to customers.
Google Merchant Center, product-feed validation, analytics continuity, domain configuration, product presentation and marketing requirements were treated as part of the launch program. The goal was to ensure that modernization did not create a disconnect between the new Shopify catalog and the acquisition channels already supporting the businesses.
Product-feed continuity
Merchant configuration and product-data readiness were handled alongside the platform transition.
Campaign enablement
The Shopify operating model gave marketing teams stronger control over campaigns and store activity than the aging custom platforms.
Production identity
Domain configuration and live storefront transition were coordinated as part of the cutover.
13 · Cross-functional delivery
Modernization required alignment across engineering, product, marketing, SEO and executive priorities.
The migration could not be designed from the codebase alone. Product teams understood catalog realities, marketers understood campaign requirements, SEO specialists understood search-sensitive pages, and executive leadership defined the brand and commercial direction. My role was to turn those perspectives into a coherent technical migration plan.
Product SetupMarketingSEOEngineeringOperations / CRMExecutive Leadership
14 · Second implementation
JustLabcoats proved the modernization approach was repeatable across another legacy stack.
JustLabcoats followed a similar modernization journey from a roughly 15-year-old ASP.NET and SQL Server commerce platform to Shopify. The migration addressed documented high-traffic performance limitations, moved products, customers and historical orders, preserved CRM synchronization through GraphQL, supported rebranding and enabled the marketing team to operate on the new platform.
The two migrations shared the same core philosophy while differing in scale and complexity: understand the legacy business first, map what must survive, use Shopify for the commodity commerce foundation, engineer the business-specific gaps, then cut over in a controlled way.
DiscoverBusiness rules & dependencies
→MapData · URLs · Catalog · Integrations
→BuildStaged Shopify implementation
→ValidateCommerce · SEO · Operations
→Cut overDomain · users · monitoring
15 · Engineering decisions
Where the project demonstrates senior-level modernization judgment.
Use Shopify as the commerce foundation
Move away from maintaining aging storefront frameworks while avoiding an unnecessary rewrite of unrelated enterprise systems.
Separate build from cutover
Prepare and validate the target environment before production traffic and domains move.
Make URL migration architectural
Treat redirect mapping and organic visibility as part of system migration—not a marketing cleanup task after launch.
Design for 250K+ SKUs
Product, variant and SKU structures were considered in the context of operations, reporting, merchandising and integrations.
Engineer differentiation, not commodity features
Use a professional theme and Shopify-native capability where appropriate, then add custom behavior for embroidery, logos and made-to-order products.
Keep the CRM valuable
The storefront could modernize without forcing internal teams to abandon established operational workflows at the same time.
Design for recovery, not optimism
Production cutover included staging, launch validation, rollback planning and post-launch monitoring so the migration had a controlled recovery path if critical issues appeared.
16 · Technology & platforms
A legacy-to-SaaS modernization spanning commerce, data, integration and growth systems.
| Legacy storefronts | Pulse Uniform: Classic ASP + SQL Server · JustLabcoats: ASP.NET + SQL Server |
|---|---|
| Legacy data | SQL Server and long-running commerce datasets |
| Target commerce | Shopify |
| Data migration | Products · images · customers · historical orders · categories · custom attributes / metafields |
| Commerce configuration | Taxes · shipping rules · payments · email notifications · Shopify Markets where applicable |
| Commerce customization | Theme customization · embroidery/logo options · made-to-order product configuration · SKU/catalog modelling |
| SEO migration | 301 mapping · canonical URLs · XML sitemap · robots directives · metadata · structured data · Search Console |
| Measurement & growth | Analytics continuity · Google Merchant Center · feed validation · marketing workflows |
| Integration | Shopify APIs · GraphQL · Existing CRM |
| Quality assurance | Theme performance · mobile QA · checkout testing · search/filter validation · feed validation |
| Release engineering | Staging · cutover planning · rollback planning · domain/DNS transition · post-launch monitoring |
17 · Business impact
Two mature commerce businesses moved to a modern platform without treating their legacy knowledge as disposable.
Legacy storefront risk reduced
Two custom Microsoft storefronts were replaced by a modern commerce platform while business-specific capabilities were carried forward.
Large catalog modernized
Pulse Uniform’s 250K+ SKU catalog and complex product structures were translated into a Shopify operating model.
SEO treated as business continuity
Redirects, canonicals, sitemaps, robots directives, metadata, structured data, Search Console and post-launch monitoring were incorporated into the migration rather than left as cleanup work.
Custom buying journeys preserved
Embroidery, logo personalization and made-to-order product options remained part of the customer experience after replatforming.
Enterprise workflows retained
CRM integration and operational data flows could continue while the commerce layer moved forward.
Teams gained a more usable platform
Product, marketing and business teams moved from heavily custom legacy storefronts to a platform better suited to ongoing merchandising and campaigns.
18 · Production evidence
Two legacy businesses, now operating on Shopify.
The original legacy storefront screenshots are no longer available, so this case study does not recreate or simulate them. Instead, the live production brands provide the clearest evidence of the modernization outcome: both businesses were replatformed from long-running Microsoft commerce applications to Shopify and continue operating on the modern commerce platform.
Lead implementation
Live Shopify storefront
Pulse Uniform
Classic ASP + SQL Server → Shopify
The larger modernization program combined catalog engineering, search-equity preservation, rebranding, custom product configuration, commerce setup, CRM continuity and controlled production cutover.
Visit Live Website ↗
Second implementation
Live Shopify storefront
JustLabcoats
ASP.NET + SQL Server → Shopify
A second legacy Microsoft storefront was replatformed using the same modernization principles, including commerce-data migration, CRM synchronization and a more maintainable Shopify operating model.
Visit Live Website ↗Live-site note: These links show the brands' current production storefronts. The sites may have continued to evolve after the original migration and replatforming work.