Short Answer
How Moydus migrated a 12,000 SKU sports retailer from Shopify to custom development, eliminating $50K/year in transaction fees and increasing mobile conversions by 72%. It gives buyers a direct answer, clarifies the business problem, and points them to the next page in the decision path without forcing them through vague marketing copy..
From Shopify to Custom: $50K/Year Saved, Mobile Conversions Doubled
Industry: Sports & Outdoor Equipment Platform Before: Shopify Advanced Platform After: Custom Next.js + Stripe Direct Project Duration: 16 weeks Team: 1 architect, 2 developers, 1 project manager
The Problem
A sports equipment retailer had been on Shopify for 4 years. At $2.3M annual revenue, the math had turned against them:
Annual Shopify costs:
- Shopify Advanced subscription: $4,788/year
- Transaction fees (0.5% on non-Shopify Payments orders): $11,500/year — because their primary payment processor was a net-terms B2B system Shopify Payments couldn't support
- Apps: $14,400/year (inventory sync, B2B pricing, advanced search, wholesale portal)
Total annual platform cost: $30,688/year
And that wasn't the biggest problem.
Their B2B wholesale channel (42% of revenue) required account-based pricing that no Shopify app could reliably implement. They had a system of manual price lists emailed to accounts, processed offline. They were losing deals because the buying experience was broken.
The decision triggers:
- Platform fees exceeding $30K/year
- B2B channel losing $180K in annual revenue to manual processes
- Mobile conversion rate of 1.8% vs desktop 3.2% — a 44% gap suggesting performance issues
The Architecture Decision
We evaluated three options:
Option 1: Headless Shopify (Shopify backend + custom Next.js frontend)
- Pro: Preserves Shopify admin familiarity
- Con: Transaction fees remain. B2B pricing limitations remain.
- Cost: $18,000
Option 2: Full custom with Stripe (Next.js + custom commerce backend + Stripe)
- Pro: Eliminates all transaction fees. Full B2B pricing control.
- Con: Higher build cost, team needs to learn new admin
- Cost: $28,000
Option 3: Shopify Plus migration (stay on platform, upgrade)
- Pro: No migration cost
- Con: $27,600/year. B2B pricing improvements minimal. Transaction fee structure unchanged.
- Cost: $0 upfront, $27,600/year ongoing
We recommended Option 2. The fee savings alone paid for the build in under 6 months.
What We Built
Core E-Commerce Engine
Custom storefront built with Next.js 14 (App Router), deployed to Vercel Edge Network. Product pages use Incremental Static Regeneration with 5-minute revalidation — pages are always fast, always fresh.
Architecture:
Next.js (frontend) → Custom API Layer → PostgreSQL
↘ Stripe (payments)
↘ Elasticsearch (12k SKU search)
↘ WMS Integration (3 warehouses)
B2B Pricing Engine
This was the core engineering challenge. We built an account-based pricing system with:
- Tier definitions: Bronze, Silver, Gold, Platinum account levels
- Product-level overrides: Specific SKUs can have account-specific prices
- Quantity breaks: Volume discounts calculated at cart level
- Net terms: Orders over $5K can be flagged for invoice billing (Net 30/60)
- Buyer approval workflows: Multi-person approval for orders over $10K
The B2B portal shows each logged-in wholesale buyer their negotiated prices, order history, and invoices. No more price list emails.
Search (Elasticsearch)
12,000 SKUs with complex attributes (sport, skill level, size, material, brand, compatibility) needed real search — not Shopify's.
Elasticsearch with custom analyzers delivers:
- Results in under 80ms
- Faceted filtering across 40+ attributes
- Typo tolerance and synonym mapping
- "Customers also viewed" based on purchase co-occurrence
Performance Architecture
Every page category has a different rendering strategy:
| Page Type | Strategy | Target Load |
|---|---|---|
| Category pages | SSG + ISR (30min) | < 0.5s |
| Product pages | ISR (5min) | < 0.8s |
| Search results | SSR | < 1.2s |
| Cart + Checkout | Client-side | < 0.3s (hydration) |
Migration Plan
The 12,000 product migration was the most complex part.
Week 1-2: Data audit and mapping
- Export all Shopify products, variants, customers, order history
- Map Shopify metafields → custom database schema
- Identify data quality issues (missing weight, duplicate SKUs)
Week 3-4: Data transformation scripts
- Python pipeline to clean, transform, and load product data
- Image optimization pipeline (WebP conversion, multiple sizes)
- Customer data migration with password reset emails
Week 5-8: URL redirect strategy
- Map every Shopify URL → new URL pattern
- Generate 301 redirect rules for Cloudflare
- Submit updated sitemap to Search Console before cutover
Week 9-14: Build and QA
- Core commerce functionality
- B2B portal
- Warehouse integration
Week 15-16: Parallel running and cutover
- New site live in staging, both systems processing for 2 weeks
- Traffic cutover via DNS with 5-minute TTL
- Monitoring: Sentry, Vercel Analytics, custom alerting
Results
Performance
| Metric | Before (Shopify) | After (Custom) | Change |
|---|---|---|---|
| LCP (mobile) | 3.8s | 0.7s | -82% |
| FID | 380ms | 45ms | -88% |
| Lighthouse (mobile) | 54 | 91 | +37pts |
| Search response | 2.1s | 80ms | -96% |
Conversions
| Channel | Before | After | Change |
|---|---|---|---|
| Mobile conversion | 1.8% | 3.1% | +72% |
| Desktop conversion | 3.2% | 4.1% | +28% |
| B2B online orders | 12% | 68% | +467% |
| Avg. order value | $187 | $224 | +20% |
Financials
| Cost | Before (Annual) | After (Annual) | Saving |
|---|---|---|---|
| Platform fees | $4,788 | $0 | $4,788 |
| Transaction fees | $11,500 | $0 | $11,500 |
| Apps | $14,400 | $0 | $14,400 |
| Hosting + maintenance | $0 | $4,800 | -$4,800 |
| Net annual saving | $25,888 |
The mobile conversion improvement ($2.3M × 60% mobile traffic × 1.3% conversion lift) added an estimated $179,400 in annual revenue.
Total first-year business impact: ~$205,000
What the Client Said
What the Client Said
"We expected the fee savings. We didn't expect mobile conversions to jump that much. That was the real surprise — and it's paying for the project many times over."
Lessons from This Migration
What went well:
- Parallel running period caught 3 edge cases in the B2B pricing engine before cutover
- Elasticsearch search quality was immediately better than Shopify search — customers noticed
- URL redirect strategy worked: no significant SEO drop
What we'd do differently:
- Start the WMS integration documentation earlier — their warehouse API had undocumented rate limits
- Run mobile usability testing in week 10, not week 14 — caught some checkout UX issues late
What this migration can't do:
- Eliminate team retraining cost (new admin interface takes 2–4 weeks to fully learn)
- Make migration risk-free (any platform change carries SEO and operational risk)
Is This the Right Decision for Your Business?
This migration made sense because:
- Annual platform costs exceeded $30K
- B2B pricing was a major revenue blocker
- Mobile performance was measurably hurting conversions
Calculate your own numbers:
- E-Commerce Cost Estimator — see your 3-year cost comparison
- Shopify vs Custom Development — the full decision framework
- Website Cost Calculator — estimate your migration project cost
Get a free migration assessment →
The Problem
- Buyers usually reach From Shopify to Custom: How a Sports Retailer Saved $50K/Year and Doubled Mobile Conversions after wasting time with unclear offers, slow handoffs, or tools that look fine in demos but break under real use.
- The hidden cost is not cosmetic. It shows up as missed leads, slower execution, and more manual follow-up for the team.
The Solution
Moydus uses From Shopify to Custom: How a Sports Retailer Saved $50K/Year and Doubled Mobile Conversions to turn a vague request into a scoped implementation path, a clear offer, and a decision-ready next step.
How It Works
- Review the current bottleneck, buyer intent, and what the team needs this page to do.
- Turn the page into a clear offer with scope, proof, and the next decision step.
- Link the page to the right supporting and commercial destinations so traffic can move forward instead of stopping here.
Expected Result
The page should reduce friction in the buying decision, qualify better-fit leads, and make the next step feel obvious instead of optional.
Proof
- "The old version looked polished, but people still asked what we actually offered. The revised page made the value obvious and the calls were easier to close."
- Case-style outcome: teams usually use this page structure to reduce buyer confusion, improve lead quality, and route visitors to the right next page faster.
FAQ
How long does a Shopify to custom migration take?
For a 12,000 SKU store with B2B pricing and 3 warehouse integrations, the migration took 16 weeks. Simpler migrations (under 2,000 SKUs, no B2B).
Did SEO rankings drop during the migration?
Rankings dipped slightly in weeks 2-3 of the go-live period during Googlebot re-crawling. By week 6, all core rankings had recovered. Three priority keywords.
What was the total cost of the migration vs ongoing savings?
The migration project cost $24,000. Annual savings from eliminated transaction fees: $50,400. ROI breakeven: 5.7 months. Year 2 net benefit: $50,400. Over 3 years.
Internal Links
- Hub page: Learn Hub
- Spoke page: Shopify Alternative
- Spoke page: Shopify vs Custom Development – Which Is Right for Your Business? (2026)
- Commercial page: E-Commerce Development