Planning your migration: Options, Timelines, and What to Do Next
NetSuite has confirmed that SiteBuilder will be retired on January 31, 2029. The same timeline applies to legacy SuiteCommerce Advanced (SCA) versions 18.1 and older.
If your storefront runs on one of these versions, this is not an emergency. But it does mean the current architecture has a defined end, and that a thoughtful migration plan should exist well before that date.
This page is intended to answer the most common questions teams search for when learning about the SiteBuilder retirement, legacy SCA upgrades, and how to migrate to a modern NetSuite ecommerce architecture.
At Awalabs, we work with teams navigating these migrations regularly. Our role is not to push a project, but to help teams understand their options, timelines, and the practical impact on their business.
What the NetSuite SiteBuilder & legacy SCA retirement means
SiteBuilder and legacy SuiteCommerce Advanced represent older ecommerce architectures. The retirement date clarifies NetSuite’s long-term direction for ecommerce.
In practical terms:
- SiteBuilder is no longer where NetSuite is investing
- modern NetSuite ecommerce architectures are the supported path forward
- legacy SCA versions will reach end of support
This gives teams time to plan a SiteBuilder migration or SCA upgrade without rushing.
How long does a SiteBuilder or legacy SCA migration take?
One of the most common questions we see in search is how long a SiteBuilder or legacy SCA migration takes.
In practice:
- migrations are measured in months, not years
- most teams approach them in phases
- a full data migration is not required, since data already lives in NetSuite
Products, customers, pricing, orders, and operational data already exist in NetSuite. The migration focuses on rebuilding the storefront and making minor adjustments if needed so data is consumed correctly by the new architecture.
SEO, performance, and discoverability improvements
Migrating off SiteBuilder or legacy SCA almost always results in meaningful SEO and performance improvements.
We consistently see:
- cleaner URL structures that search engines understand better
- improved page speed and Core Web Vitals
- stronger mobile indexing and responsiveness
- better content structure for both users and search engines
These improvements also matter for AI-driven discovery, where structured content, performance, and clarity influence visibility in modern search and recommendation systems.
How teams approach SiteBuilder and SCA migrations
Even when teams aim for a minimal or fast transition, the age of SiteBuilder and legacy SCA means the outcome is typically a substantial upgrade.
Re-implementations lead to:
- modern, responsive storefronts
- significantly improved UX
- stronger SEO foundations
- better long-term maintainability
Some teams treat the migration as a redesign. Others simply modernize by necessity. Either way, the result is almost always a better ecommerce experience.
Technical decisions that reduce long-term risk
Legacy storefronts often contain years of accumulated customizations.
As part of a SiteBuilder or legacy SCA migration, we:
- identify which customizations should be rewritten
- replace custom logic with native platform features where possible
- remove workarounds that are no longer needed
- simplify architecture to reduce future maintenance cost
This approach lowers technical debt and makes future upgrades easier.
You do not need to migrate immediately, but planning matters
There is no need to migrate today. However, teams that plan earlier have more flexibility around timing, scope, and budget.
Early planning allows teams to:
- align migration timing with business cycles
- preserve SEO equity during the transition
- choose the right architecture for long-term growth
Why work with NetSuite ecommerce specialists
As ecommerce requirements mature, storefront architecture decisions become more specialized.
Awalabs focuses specifically on NetSuite ecommerce implementations, including SuiteCommerce Advanced and modern architectures such as AwaCommerce. This specialization helps teams avoid common migration pitfalls and build storefronts that scale.
A consultative approach to SiteBuilder retirement
Announcements like the SiteBuilder retirement often create uncertainty.
Our role is to help teams understand what the retirement means for their specific storefront, how long a migration would realistically take, and what options exist without pressure.
Discuss your specific setup
We offer consultative reviews for teams evaluating a SiteBuilder migration or legacy SCA upgrade. These conversations are focused on clarity, not selling.
There is no requirement to start a project or commit to a timeline. The goal is to understand your options and remove unnecessary anxiety.
