Features of Migration from Shop-Script to 1C-Bitrix

We often face the task of migrating from Shop-Script (Webasyst) to 1C-Bitrix. This solution is suitable for companies that have outgrown the capabilities of a lightweight eCommerce platform and need full-fledged integration with 1C, complex logistics, or extended functionality. In this article, we will explain how to transfer products, orders, and customers with minimal risks. Contact us to evaluate your project — turnkey migration takes from 2 weeks to 4 months depending on data volume. Our experience: over 10 years and 50+ successful migrations, we guarantee correct data transfer.

Why Migrate to 1C-Bitrix?

Shop-Script is an excellent solution for small stores, but when scaling a business, its capabilities often fall short. 1C-Bitrix offers built-in integration with 1C, trade offers, caching mechanisms, and a flexible permission system. According to our tests, on catalogs over 10,000 products, Bitrix with tagged caching is 3–5 times faster than Shop-Script. Additionally, the marketplace module and support for Federal Law 54-FZ make it the preferred choice for serious eCommerce.

Webasyst/Shop-Script Data Structure

Webasyst uses tables with the shop_ prefix (in MySQL database). The main ones:

• shop_product — products: id, name, url, summary (announcement), description, price, status
• shop_product_skus — SKUs: variations with price and stock
• shop_product_features — product characteristics (analog of infoblock properties)
• shop_product_features_values — characteristic values
• shop_category — categories
• shop_order — orders
• shop_order_items — order items
• shop_customer — customers (linked to the contact table of the Webasyst framework)
• shop_product_images — images

Webasyst also has a REST API through which data can be obtained without direct database access.

Retrieving Data via Shop-Script API

// Example request to Webasyst API $url = 'https://yourstore.ru/api.php'; $response = file_get_contents($url . '?method=shop.product.getList&access_token=' . $token); $products = json_decode($response, true)['response']; 

The API returns products with a full set of data, including SKUs and characteristics. This is the preferred method if direct database access is not available.

Product Characteristics Mapping

Shop-Script supports typed characteristics: string, number, color, select, date. The structure maps to Bitrix infoblock properties:

Characteristics with type "color" in Shop-Script have special rendering — in Bitrix, the analog is implemented via visual editing of an L-type property with HTML color code.

SKU and Variations

Shop-Script stores trade offers in shop_product_skus with fields: id, product_id, name, price, count, sku (article). Linking to characteristic-variants is through shop_product_skus_features.

In Bitrix, these are trade offers of the catalog module. Each SKU from Shop-Script → a separate trade offer with corresponding properties.

Customer Base and Orders

Buyers in Webasyst are stored in two tables: contact (common, for the entire framework) and shop_customer (extended for Shop-Script). In contact there are: name, email, address fields.

SELECT c.id, c.name, ce_email.value AS email, ce_phone.value AS phone FROM contact c LEFT JOIN contact_data ce_email ON c.id = ce_email.contact_id AND ce_email.field = 'email' LEFT JOIN contact_data ce_phone ON c.id = ce_phone.contact_id AND ce_phone.field = 'phone' WHERE c.id IN (SELECT contact_id FROM shop_customer); 

Buyers are created in Bitrix via CUser::Add(). Passwords are not transferred — only email and profile data. On first login, a password reset is offered.

Integration with Webasyst Applications

If the site uses other Webasyst applications (Blog, Photos, Helpdesk) — their data is migrated separately: blog → infoblock, photo galleries → Bitrix photo gallery or infoblock with images.

How We Perform Migration?

Our process consists of three stages: analysis and prototyping, development and testing, deployment and support. First, we prepare a technical specification, agree on the data schema, and set up the environment. Then we develop transfer scripts with verification on a test database. After successful testing, we deploy, configure integrations with 1C and payment systems. Finally, we conduct training and provide one month of warranty support.

What's Included?

• Audit of current database and data structure
• Development of a migration map (table and field mapping)
• Transfer of products, SKUs, characteristics, categories, orders, customers, images
• Setup of 301 redirects for SEO preservation
• Integration with 1C (exchange via CommerceML) and payment gateways
• Testing of data integrity and performance
• Training for administrators and delivery of documentation
• 1 month warranty support

Typical Timelines

The site template is developed from scratch on Bitrix — Webasyst themes are not compatible. Get a consultation — we will evaluate your project in 2 days and offer an optimal migration plan.