Work / MyCustomPatches / Independent client
MyCustomPatches
A decade-old WordPress store, off it in about 22 days, with zero downtime recorded at cutover.
MyCustomPatches ran on WordPress for years before moving to a custom Next.js build -- URL mapping and redirects were planned before cutover. The project record reports no ranking losses in the 30-day post-launch monitoring window.
- Migration completed in
- about 22 days
- Distinct templates rebuilt
- 13
- Downtime at cutover
- zero
One storefront, one template, one process.
A store built on one template,
backed by a real process.
The storefront customers browse, the product template that runs every category page, and the order process behind each purchase.
01 / Storefront
Eight categories, one entry point.
The public storefront: patch types organized as category cards, each leading to its own product page.
Chenille, PVC, woven, leather, shoe charms and embroidery are among the categories on the homepage, each with a short description and a direct link into that category's product page.
The homepage also carries an instant-quote entry point and a live chat widget, visible in the corner of this screenshot.
Category grid
Each category card links straight into that product's own page -- the same shared template every category runs on.
02 / Product template
One template, every category.
Every product category page runs on the same shared template -- this one's Custom Chenille Patches, but the layout, fields and CTA are identical across all eight.
A photo gallery, a feature checklist, and the specifics that actually change a customer's decision: turnaround time (12 to 14 days standard, 4 to 7 days rush), minimum order quantity (as low as 50 units), and what's included (professional digitization, free revisions).
This is the same ProductPageTemplate component referenced in the migration record -- one template change applies to all eight category pages at once.
Custom Chenille Patches
12–14 day standard turnaround, 4–7 day rush, MOQ as low as 50 units -- the specifics a buyer actually needs, not filler copy.
03 / Order process
Design to finished patches, four steps.
The page that explains how an order actually moves: submit a design, approve a mockup, wait for production, receive finished patches.
Submit Your Design (professional digitization included) → Approve Your Mockup (free revisions until perfect) → Production Begins (US quality standards) → Receive Ready Patches (12 to 14 days standard turnaround).
Each of the four steps has its own “Get Quote Now” button, rather than routing every visitor to one generic contact form.
Design to production
Four steps, each with its own detail and its own path to a quote -- not one generic “how it works” paragraph.
Design submitted, mockup approved, patches produced -- the same four-step process and the same product template across all eight categories.
Also in scope.
Search rankings lost, per Google Search Console: none recorded in the 30 days after launch. Performance figures were withdrawn pending reconciliation of the original test records. The old hosting cost figure was retired because no invoice or reliable recollection exists to support it.
- Off a decade of WordPress, in about 22 days
- Moved the WordPress store to Next.js in roughly three weeks. The team inventoried search metadata and mapped redirects where URL paths changed.
- Forms with no server to maintain
- Quote and contact forms run on React Hook Form with Zod validation, delivered by Web3Forms -- no custom form backend to run. Design-file uploads go straight to Cloudinary.
- A single DNS cutover, not a slow migration
- The new build ran in parallel on staging while the WordPress site stayed live. After QA, a single DNS cutover with a pre-lowered TTL made the switch, and the project record shows zero downtime at cutover.
Questions about this project.
How did you handle URLs and search visibility during the WordPress move?
What made the rebuilt site faster than the WordPress original?
How does the hosting model differ from managed WordPress?
Was there any downtime during the migration?
What happens to the quote forms and file uploads after migration?
Stuck on an old platform you're afraid to touch?
Tell us what you're running and what you're afraid of losing, and we'll work out what a careful migration would take.