NetSuite SiteBuilder and legacy SCA lose support January 31, 2029. Plan your migration now.

NetSuite has confirmed that SiteBuilder will lose support on January 31, 2029. The same deadline applies to legacy SuiteCommerce Advanced (SCA) versions 18.1 and older. This is a confirmed date, not speculation. While there is no need to migrate tomorrow, a thoughtful migration plan should be in place well before that date.

Yes. Legacy SCA versions 18.1 and older follow the same January 31, 2029 end-of-support timeline as SiteBuilder. If you are running SCA 18.1 or earlier, you need to upgrade to a modern SCA version or migrate to another platform. This affects a significant number of NetSuite commerce customers who implemented SCA in its early years.

End of support means NetSuite will no longer update, patch, or maintain SiteBuilder and legacy SCA architectures after that date. Your site will not stop working overnight, but operating on an unsupported platform creates significant risk: no bug fixes, no security patches, and no compatibility guarantees with future NetSuite releases.

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.