Oracle's help center calls Site Builder “the legacy commerce solution delivered by NetSuite.” There is no published end-of-support date, so you can plan the move instead of rushing it. Your data already lives in NetSuite. The migration is a storefront rebuild, not a replatforming.
SuiteCommerce specialists since 2017 · 100+ companies served · Migrations in months, not years
See migration pathsStatus
Oracle has not published an end-of-support date for Site Builder or older SCA releases.
Treat any date you see online as unconfirmed, and plan the move on your own schedule.
The Migration Difference
SiteBuilder and legacy SCA represent older eCommerce architectures. Here is what changes when you move to a modern, supported platform.
Free tools
Three tools you can use right now — no signup, no sales call. Understand where you stand before making any decisions.
Run your current SiteBuilder or SCA site through our performance analyzer. Core Web Vitals, load times, and a list of what to fix — before you even start the migration conversation.
Answer a few questions about your business model, volume, and requirements. Get a platform recommendation with cost estimates in under 3 minutes.
Your new storefront needs an integration layer to sync with NetSuite. Compare iPaaS platforms side by side and find the one that fits your migration architecture.
Track record
NetSuite-only since
Companies served
Of clients hire us again the next year
Rating on Clutch
Why BrokenRubik for Your Migration
We migrate to SuiteCommerce, Shopify Plus, BigCommerce, or headless architectures. We recommend what fits your business model, not what pays us the highest margin.
This is not a full-stack replatforming. Products, customers, orders, and pricing already live in your ERP. The migration focuses on rebuilding the storefront layer and connecting it properly.
Migrating off SiteBuilder or legacy SCA almost always results in cleaner URLs, faster page speeds, improved Core Web Vitals, and better mobile indexing. Your organic traffic improves, not just survives.
Celigo, Boomi, or custom integrations. We configure real-time data sync between NetSuite and your new storefront so orders, inventory, and customers flow without manual intervention.
We identify customizations worth rewriting, replace custom logic with native features, and remove outdated workarounds. You end up with a cleaner, more maintainable system that costs less to operate.
Most migrations complete in phases over weeks to months. Starting before something forces the move lets you pick the timing and leave room for discovery and testing.
Migration paths
No one-size-fits-all. Your business model, budget, and technical requirements determine the platform. These are the options we implement and support.
Stay native to NetSuite with the latest SCA architecture. Customer-specific pricing, complex order workflows, no third-party middleware.
World-class storefront for consumer brands. NetSuite handles operations, Shopify handles the experience. Connected via Celigo or custom integration.
Multi-storefront, headless-ready, native B2B features, and NetSuite connectors without SuiteCommerce licensing.
NetSuite's streamlined commerce option. Functional online catalog with ERP sync, not a full custom storefront.
Next.js, Hydrogen, or custom frontends. NetSuite as the commerce engine via API. For brands that need unique digital experiences.
Our product. Self-service B2B ordering, customer-specific pricing, invoice payments, real-time inventory. Live in 2-4 weeks.
Our B2B Product
BrokenRubik B2B Portal connects directly to NetSuite. Customer-specific pricing, self-service ordering, invoice payments, and real-time inventory. No SuiteCommerce license required. Live in 2-4 weeks — the fastest migration path for B2B companies.
Your data stays in NetSuite. We rebuild the customer-facing layer.
Cleaner URLs, faster speeds, better Core Web Vitals, improved mobile indexing.
Celigo, Boomi, or custom middleware for real-time NetSuite sync.
Replace custom workarounds with native features. Lower maintenance costs.
Your team is confident on the new platform. Post-launch support included.
How It Works
A structured, phased approach refined over years of eCommerce migrations. Most teams complete the migration in months, not years.
We audit your current SiteBuilder or legacy SCA setup: pages, catalog, customizations, integrations, and SEO footprint. You receive a migration report with platform recommendations, timeline, and investment range.
Based on the assessment, we recommend the best platform for your business and design the integration architecture. We identify technical debt to eliminate and native features that can replace custom code.
Your data already lives in NetSuite — we rebuild the storefront layer on the new platform and configure iPaaS middleware (Celigo, Boomi, or custom) for real-time sync. No full data migration needed.
301 redirects for every URL. Metadata and structured data migration. Sitemap regeneration. The new storefront launches with cleaner URLs, faster load times, and improved Core Web Vitals.
Full regression testing of orders, payments, and data sync. Team training on the new platform. Cutover with zero downtime. 30-day hypercare support included to catch and resolve any post-launch issues.
Contact
Tell us about your current SiteBuilder or legacy SCA setup. We will review your configuration, recommend the best migration path, and give you a timeline and investment estimate. No commitment.
The people who answer: NetSuite consultants and developers, not a sales team.
5.0 on ClutchFAQ
Oracle has not published an end-of-support date for Site Builder. Its help center describes Site Builder as "the legacy commerce solution delivered by NetSuite" and SuiteCommerce as the modern web store. You may see a specific date quoted on other sites; we could not find it in any Oracle documentation, so we do not plan around it. If your NetSuite account team gives you a date in writing, use that one.
SCA is a bundle you install and customize, so a site stays on the release it was built on until someone migrates it to a newer one. Oracle has not published an end-of-support date for older releases such as 18.1 either. The practical cost is that a store several releases behind misses the newer SCA features, and its customizations get harder to change safely. Moving to a current SCA release or another platform fixes both.
Not on any date Oracle has announced: there is no published shutdown. The risk is slower. A legacy platform gets left behind as commerce moves on, fewer developers know it, and old customizations get harder to change. That is why most teams plan the move on their own schedule instead of waiting for a deadline.
No. This is a key advantage. Your product, customer, order, and pricing data already lives in NetSuite. The migration focuses on rebuilding the storefront layer — the customer-facing website — and connecting it to your existing NetSuite data. This makes the migration scope significantly smaller than a full replatforming.
It depends on your business model. For B2B companies with complex pricing and deep NetSuite workflows, modern SuiteCommerce Advanced or our B2B Portal are strong choices. For D2C and B2C brands focused on conversion and marketing, Shopify Plus with a NetSuite integration is often best. For mid-market companies wanting B2B features without SuiteCommerce licensing, BigCommerce is worth evaluating. We provide a free assessment to recommend the best fit.
No — in fact, you should gain rankings. Migrating off SiteBuilder or legacy SCA almost always results in cleaner URLs, faster page speeds, improved Core Web Vitals, and better mobile indexing. We implement 301 redirects for every URL, migrate metadata and structured data, regenerate sitemaps, and monitor rankings for 90 days post-migration.
Migrations are measured in months, not years. Most teams approach them in phases. A straightforward migration (standard catalog, limited customizations) typically takes 8-12 weeks. Complex projects with multiple integrations, B2B portals, or multi-region setups may take 16-20 weeks. We provide a fixed timeline during the assessment phase.
Absolutely. Migration is the ideal moment to identify customizations worth rewriting, replace custom logic with native platform features, and remove outdated workarounds. Teams that treat migration as a clean-up opportunity end up with a more maintainable, lower-cost system on the other side.
Yes. Integration is a core part of every migration we do. We implement iPaaS solutions (Celigo, Boomi) or build custom middleware for real-time sync between NetSuite and your new storefront. This covers order flow, inventory updates, customer data, pricing rules, and fulfillment status.
We review your current SiteBuilder or legacy SCA configuration, catalog size, integrations, customizations, SEO footprint, and business requirements. You receive a written report with: platform recommendations (with pros and cons for each), estimated timeline, integration architecture overview, technical debt assessment, and a ballpark investment range. No obligation.
Yes. Our B2B Customer Portal connects directly to NetSuite without requiring a SuiteCommerce license. It supports customer-specific pricing, self-service ordering, invoice payments, and real-time inventory. It can go live in 2-4 weeks — making it the fastest migration path available for B2B companies that need a functional portal quickly.
About SiteBuilder migration
Oracle's help center calls Site Builder “the legacy commerce solution delivered by NetSuite”; SuiteCommerce is the current one. No end-of-support date has been published, so the question is when a move to SuiteCommerce, Shopify, BigCommerce, or another platform makes sense for your business. We've worked only in NetSuite since 2017, for 100+ companies. Done well, a migration takes 8-16 weeks and preserves SEO, conversion paths, and customer data.
Oracle documents Site Builder as legacy and positions SuiteCommerce as its modern web store. With no shutdown date announced, the choice is about timing: migrate on your schedule, or later under pressure with less control over when.
A planned migration leaves time for proper discovery and testing, which is where most of the risk in a storefront move gets removed.
SuiteCommerce Standard or Advanced: stays in NetSuite, no new integration. Recommended for B2B-heavy use cases. Shopify Plus: best B2C UX, requires a NetSuite integration (Celigo or custom). BigCommerce: middle ground, B2B Edition for B2B-heavy. Custom platform: rare, only for very specific needs.
Target choice drives everything else: timeline, cost, SEO impact, integration architecture. We help pick the right target before quoting.
SEO is the single biggest risk in ecommerce migration. URL changes, missing redirects, content rewrites, schema gaps — any of these can tank organic traffic for 6-12 months.
Every SiteBuilder migration we run includes a structured SEO plan: URL mapping, 301 redirects at scale, schema markup preservation, Core Web Vitals optimization on the new platform. Done well, organic traffic stays flat through migration; done badly, it can take months to recover.
Beyond URLs, migration covers product catalog, customer accounts (with password reset flow), historical orders, custom fields, and any SiteBuilder-specific data structures.
We run staged data migrations with reconciliation against source data, multiple test runs, and a structured cutover process. Customer-facing email about account changes is part of every project.
Related
