BigCommerce to BASE Migration

Supported standard data includes products and categories, customers, orders, manufacturers, coupons, reviews, and blogs where corresponding BASE fields are available. Taxes, CMS Pages, and Multiple Languages are not included as standard entities for this route.

Customer password transfer is not part of the standard BigCommerce export scope used for this migration. Customer profiles can be migrated, but customers may need to set or reset their login credentials on BASE after launch depending on the target account configuration.

No. BigCommerce themes, apps, scripts, and custom storefront logic are platform-specific and are not transferred as standard store data. Equivalent design and functionality should be recreated or configured for BASE separately.

For non-standard fields or transformations, our Migration Customization Service can be used to assess the required mapping.

Yes, supported BigCommerce variants and attributes can be migrated when their relationships can be mapped to the corresponding BASE product structure. Complex option sets or app-generated product data should be reviewed during the migration assessment.

Yes. The migration runs separately from your live BigCommerce storefront, so customers can continue browsing and placing orders while the main transfer is in progress.

Before launch, newly created records can be transferred with Recent Data Migration when applicable.

Preserve supported product and category metadata, then map important BigCommerce URLs to their new BASE destinations. When URL structures change, use 301 redirects to reduce broken links and preserve important search and backlink signals.

After migration, review redirects, metadata, canonical URLs, sitemap behavior, and crawl errors before launch.

Yes, supported review data such as created date, rating, author, and comment can be mapped to BASE. For blogs, the standard overlap includes title, description, URL, and thumbnail image. Fields that exist only on one platform are not included in the standard migration scope.

Yes. A Demo Migration lets you review a sample of migrated data before the Full Migration. Use it to verify products, customers, orders, reviews, blogs, images, and field mapping.

The timeline depends on your BigCommerce data volume, number of selected entities, app-dependent or custom data, data quality, and the amount of validation required. After reviewing the store, the migration team can provide a more specific project timeline.

Migration cost depends on the number of products, customers, orders, blog posts, and other selected entities, along with any custom migration requirements. Use the Cost Estimator on this page for an initial estimate.