How to migrate from SuiteCommerce without losing SEO

A storefront migration is one of the riskiest moments for organic traffic. The good news: almost all post-migration traffic loss comes from a short list of avoidable mistakes. This guide walks through the process we use when moving NetSuite merchants off SuiteCommerce or SuiteCommerce Advanced (SCA), step by step.

Why migrations lose traffic

Rankings belong to URLs. When a URL disappears without a permanent redirect, Google drops it and the links pointing to it stop helping you. The other common causes:

• Page titles, meta descriptions, and headings that are not carried over
• Category pages merged, split, or renamed without a plan
• Product structured data missing on the new site
• A staging site that gets indexed, or a live site that is accidentally blocked
• A slower new site, or one that renders content only in the browser
• Nobody watching Search Console in the weeks after launch

Step 1: Benchmark before you touch anything

Record where you stand so you can prove the migration worked:

• Organic sessions, conversions, and revenue for the last 3 to 12 months
• Top landing pages from organic search
• Top queries and average positions from Search Console
• Pages with the most backlinks, from your SEO tool
• Core Web Vitals for the home page, a category, and a product page

Step 2: Build a complete URL inventory

Crawl the current SuiteCommerce site with an SEO crawler and export every indexable URL. Add URLs from:

• Your current XML sitemap
• Search Console's indexed pages report
• Analytics landing pages with organic traffic
• Backlink reports

SuiteCommerce URLs usually follow a few patterns: product URLs built from the item URL component, category URLs from the commerce category path, and search or facet URLs with query parameters. Group your inventory by pattern; it makes redirect mapping much faster.

Step 3: Keep URLs where you can

The best redirect is one you do not need. If your new platform lets product URLs reuse the NetSuite URL component, many product URLs can stay the same or close to it. Keep category paths stable when the structure is not changing.

On AwaCommerce Next, the guided site migration maps your NetSuite URL component onto the new product URL field, so product URLs stay recognizable.

Step 4: Map every remaining URL with a 301

For every URL that changes, choose its best new match:

• Product to product. Never send a product to the home page.
• Category to category, or to the closest parent if a category is removed.
• Discontinued products to the most relevant category, or let them return 404 if nothing fits.
• Content pages to their new equivalents.

Use permanent 301 redirects. A 302 tells search engines the move is temporary and keeps the old URL in results. Avoid chains: an old URL should land on its final destination in one hop where possible.

AwaCommerce Next helps here in two ways. First, the storefront recognizes the classic SuiteCommerce URL style automatically: old product URLs go to the product, old category URLs go to the matching category, and old sort, page, keyword, and filter parameters carry over when they match a current filter. Second, any other redirect can be added in the Admin or imported by CSV, with hit counts so you can see which old links still get traffic.

Step 5: Carry over on-page SEO

For every category and key landing page, copy:

• The page title and meta description
• The H1 and introductory copy
• Any FAQ or buying-guide content that ranks

For products, make sure names and descriptions come across intact. On NetSuite, these usually live in web store fields; the AwaCommerce migration maps them onto the new item fields.

Step 6: Check technical SEO on staging

Before launch, on the staging site:

• Block indexing with a password or noindex so it does not compete with the live site
• Check product structured data (name, price, availability, reviews) with Google's Rich Results Test
• Check canonical tags point to the live domain
• Confirm pages render their main content on the server, not only in the browser
• Run Lighthouse on key templates and compare with your benchmark
• Test 50 of your highest-traffic old URLs against the redirect rules

Step 7: Launch day

1. Lower the DNS time to live a few days before.
2. Switch DNS and remove any staging noindex from the live site.
3. Test the home page, search, a product, the cart, and checkout on the live domain.
4. Spot-check the top old URLs again on the live domain.
5. Submit the new XML sitemap in Search Console and Bing Webmaster Tools.
6. Keep the old sitemap reachable for a few weeks so crawlers find and follow the redirects.

Step 8: Monitor for 30 days

• Daily for two weeks: Search Console coverage and 404 reports. Add redirects for any old URL that still gets hits.
• Weekly: rankings for your top queries, organic sessions, and conversions against the benchmark.
• Day 30: a full comparison report.

Small fluctuations in the first two weeks are normal while Google recrawls. Sustained drops usually point to a missed redirect pattern or missing content.

Common mistakes to avoid

• Redirecting everything to the home page
• Using 302 instead of 301
• Launching on a Friday
• Changing URLs, categories, design, and content all at once without a map
• Forgetting image URLs and PDF downloads that earned backlinks
• Turning off the old site before redirects are verified

Read how the full SuiteCommerce migration works on AwaCommerce Next, or request a migration assessment and we will review your URLs with you.