BigCommerce to Miva Merchant Migration

Our client is a US-based automotive parts retailer with a long-established business that began in 1969. With decades of experience in the industry, their business operates a large online catalog and earns a steady flow of online orders supporting day-to-day business.

As their B2B catalog grew in size and complexity, managing pricing tiers, customer-specific rules, and product visibility across two BigCommerce storefronts became increasingly difficult. Consolidating into a single store on the same structure would not eliminate the underlying limitations in handling high-SKU catalogs and advanced B2B logic.

They chose Miva Merchant not simply to unify their storefronts, but to gain stronger native control over complex product configurations and scalable pricing structures. This allowed them to centralize operations within a more flexible architecture designed for high-volume B2B environments.

With a large B2B dataset and complex product logic, our client needed a provider that could handle scale without compromising data accuracy. They chose LitExtension for our experience with large B2B migrations and a structured process that ensured critical data remained consistent after the move.

For this project, the client needed to merge data from two separate BigCommerce stores into a single Miva Merchant store while preserving clear category logic and consistency. Their key requirements included:

• Migrate all products from each source store under its own main category in Miva Merchant.
• Apply a clear naming rule for sub-categories, using the source store name as a prefix for category codes.
• Migrate all customers and orders from both BigCommerce stores into the new Miva Merchant store.

Working within a tight deadline was one of the main pressures of this project. The client had scheduled the launch of their unified Miva Merchant store around internal operational milestones. With limited time available, our team had to account for multiple data sources while keeping the overall timeline on track.

Another challenge came from the complexity of the product structure. Each store followed different category structures, naming conventions, and customer segmentation logic. In a B2B environment, this meant preserving tiered pricing, customer group permissions, tax rules, and historical order data without creating pricing conflicts or access inconsistencies in the new system.

Given the scale of the dataset and the structural differences between the two platforms, the project was executed under our All-in-One Migration Service. This approach covered detailed data auditing, mapping alignment, full migration, and post-migration QA validation.

The migration was divided into clearly defined stages to control risk. It began with a full data audit and structure mapping, followed by migrating the first source store and validating its hierarchy and logic before proceeding. Only after confirming structural accuracy was the second store migrated, ensuring clean separation and minimizing the chance of cross-store conflicts.

For product data, each store was handled independently to prevent overlap. Category codes were systematically generated using structured prefixes linked to each store’s original parent hierarchy. This prevented unintended category merging, maintained clear segmentation between datasets, and created a scalable, well-organized structure once consolidated within Miva Merchant.