Big Sky Dynamics: From Custom React to Riven Portal in 14 Days

The Problem

Big Sky Dynamics (BSD) is an $8M industrial hydraulics distributor based in Montana. Before Riven, they ran a custom Next.js frontend, a separate Medusa backend, and a NetSuite connector maintained by a part-time contractor. Every pricing change required a deploy. Every new customer tier needed a code change. The contractor left. The stack rotted.

The Decision

BSD is a Cassilly Capital portfolio company. When Riven Commerce was built to unify the portfolio stack, BSD became the first production proof point. The mandate was simple: migrate without disrupting customer orders, and do it before the legacy SSL cert expired.

The Migration

Day 1–3: Catalog export and seed. 2,400 SKUs migrated from NetSuite to Riven Catalog via automated import script.

Day 4–7: Forge generation. BSD described their business in three sentences. Riven Forge generated a portal skin with navy-and-steel branding, hydraulic part categories, and a dealer login flow. One refinement cycle changed the hero image.

Day 8–10: Stripe checkout wiring. Live PaymentIntent tested end-to-end with real cards. Webhook handlers verified for `payment_intent.succeeded`.

Day 11–14: DNS cutover. Cloudflare apex A record repointed to Azure Front Door. 301 redirects preserved from old routes. Zero downtime.

The Result

BSD now runs on a single platform: Riven Commerce backend (Medusa v2), Riven Auth (Logto), Riven Catalog (PIM), and a Forge-generated portal skin. Their COO manages pricing tiers in the admin dashboard without opening a terminal. Their customers log in once and see real-time inventory, order history, and net pricing.

The custom React codebase is archived. The NetSuite connector is retired. The part-time contractor invoice is gone.

“We spent more time maintaining our storefront than selling hydraulics. Riven flipped that ratio.”

What’s Next

BSD is now the reference implementation for every Cassilly portfolio company migration. PES Supply is next. Portlandia Electric follows. Each migration refines the playbook — and makes the next one faster.