Noah's Park & Playgrounds, based in Edmond, Oklahoma, supplies commercial playground and park equipment from more than 25 manufacturer brands to schools, city parks, churches and daycares across the US. Most of its customers are organizations, many sales start with a quote, and the company has more than 20 years in playground design, sales and installation behind it.
Its online store ran on BigCommerce, alongside a newer marketing site on a separate domain. This story covers what the move to Core dna's B2B eCommerce platform had to solve, how the two sites became one, and what B2B sellers can take from it when they look at BigCommerce alternatives.
The challenge
Noah's Park & Playgrounds sells to buyers who rarely check out like consumers. A school or parks department may buy a bench or a swing seat online, but a play structure, a shade or a load of safety surfacing usually needs a quote, and many of these buyers are tax-exempt.
On BigCommerce, quote requests ran through a third-party quote app. The store held the products, the blog and the installed project pages, while a newer marketing site on another domain carried a refreshed design, a map of installed playgrounds and some newer pages. Content lived in two places, and buyers moved between two domains.
The company wanted more leads and quote requests, more expert advice on its site, and a platform to build on, including a closer connection to Salesforce and further brand sites later.
What Noah's Park & Playgrounds needed
- One website in place of two, keeping the pages that already brought in traffic.
- Quotes built into the store, alongside normal purchases.
- A catalog of products from many brands, with options that change the price.
- Installed projects on a map, so buyers can find a playground near them.
- Orders, quotes and leads in Salesforce.
- A theme that further brand sites can reuse.
How the two websites became one
Discovery first. Nine discovery sessions with the Noah's Park & Playgrounds team covered the design, pages, blog, projects, accounts, products, checkout and quotes, Salesforce and the migration plan before the build started.
One domain. The merged site runs on the store's domain, and the marketing site's domain now points to it.
Pages chosen one by one. Where the newer marketing site had the better version of a page, such as the shipping and delivery guide, that version was used. Everything else came from the store.
Products imported from BigCommerce. The catalog came across from BigCommerce, and products with several combinations were set up as one product with options. The website is now the source of truth for products, and the team updates prices, descriptions and categories in bulk by exporting, editing and re-importing the catalog.
Blog and project pages imported. Blog posts moved to a simpler /blog/ address. Installed project pages kept their URLs and now sit behind a project finder with map and list views, built on the same structure as YMCA of Greater Toronto's location finder.
Category and brand pages kept. Category and brand landing pages were recreated as content pages on their existing URLs, so links and search listings that point to them still work.
Search set up for launch. The new site was kept out of search engines until launch. Analytics, tag management and search console were set up, the sitemap was submitted and crawl errors were checked.
Moving off BigCommerce?
Book a call with Core dna. We'll walk through your current store, the other sites you run, and what moving them onto one platform would involve.
Before and after the move
| On BigCommerce | On Core dna | |
|---|---|---|
| Websites | A BigCommerce store and a separate marketing site | One website on one domain |
| Quotes | A third-party quote app | Quote requests in the same cart and checkout as purchases |
| Installed projects | Project pages on the store, map on the marketing site | Project pages and the map in one place, with map and list views |
| Product updates | Edited in the BigCommerce store | Bulk export, edit and import, with the website as the source of truth |
| Blog | On the store | On the merged site at /blog/ |
Selling to organizations on the merged site
The B2B side of the site runs on the same platform as the content:
- One checkout for purchases and quotes. Products are marked purchasable or quote only, and the checkout becomes a quote request when the cart needs one or the buyer claims a tax exemption.
- Sales tax from the delivery address, calculated by a tax service at checkout.
- Salesforce. Orders, quote requests, accounts, newsletter sign-ups and form submissions are sent to Salesforce, so the sales team sees every lead.
- Many brands, one catalog. Products from more than 25 manufacturers sit in one catalog, with brand pages and search across products, blog posts and projects.
Questions to answer before leaving BigCommerce
- How many websites do you run? Count the store, marketing sites, landing page tools and brand sites. Each one you keep is another place to update content.
- Where do quotes live today? If quoting runs through an app, check whether the new platform handles quotes and purchases in one checkout, and what happens to tax-exempt buyers.
- Which URLs bring in traffic? List every page on every domain you're retiring, including deep links on old domains, and redirect each one to its new home. Pointing an old domain at the new home page isn't enough.
- How will products with many combinations move? Check how each variant, option and price maps to the new catalog before importing.
- Where will product data live? Decide whether the website, an ERP or a PIM is the source of truth, and how the team will update it in bulk.
- Which CRM or ERP needs orders, quotes and leads? Agree what is sent, when, and which system updates order status.
For the full list, use the 47-point eCommerce platform migration checklist. For a wider comparison, see BigCommerce alternatives and the 8 best B2B eCommerce platforms of 2026.
