Migration from other platforms
Moves a shop from Webasyst: catalogue, warehouses, customers and orders.
Moving from Webasyst (Shop-Script) without retyping anything: the catalogue, customers and orders come across on their own, while the old shop is only read from and keeps trading. Before the move you see how much was found and match the old shop's attributes, product types, warehouses and order statuses to your own so no duplicates appear.
What it does
- Brings over categories, product types, attributes with their values and the products themselves — with variants, prices, selling units and minimum quantity.
- Brings over warehouses with the stock held in each and adds them to yours.
- Fetches product photos in the largest size the old shop serves; running it again does not re-download what already came across.
- Brings over customers with phones, e-mails, addresses and dates. Someone you already have is found by phone digits and e-mail and topped up rather than duplicated, so the purchase history stays whole.
- Brings over orders: line items, totals exactly as the old shop had them, discounts, coupon, addresses and the payment and shipping method names. Nothing is recalculated.
- Connects either way: with an access key to the old shop, or straight to its database — the second is faster and brings content translations too, if the old shop was multilingual.
What you need
- The old shop's address and an access key to it — the old shop issues the key itself through a link in the form, read-only.
- Or its database credentials: server, database name, user and password (in the old site's wa-config/db.php), plus the site address, which is where photos come from.
What's new
Once orders have been moved, the migration screen shows a new block: "Methods in moved orders". It lists payment and delivery method names exactly as the old store sent them, with the number of orders behind each name. You pick your own method next to each one and press "Link and apply" — the store applies it to every such order at once, leaving the amounts untouched.
After that these orders behave like any other: an unpaid one gets the pay button in the customer's account, the waybill sees cash on delivery, and filtering by method finds them in the order list. The old store does not share its methods at all — their settings are not transferred — so linking happens after the move, by the name kept in the order itself. The block is still there a week after the migration, and it disappears once nothing is left to link.
What to do after the update
The add-on needs store version 2.45.0 or newer. If you moved your orders earlier, open the "Migration" section and link the methods: until then moved orders do not know how they were paid for or shipped.
What we fixed
Numeric features now arrive as numbers. In the old shop volume, weight and length were often picked from a list of ready-made values, and the move created the same list-based feature for you — even though here a number is typed in as a number. The catalogue fell apart because of it: some products kept the value as a number, others as a list value, the field on the product page stood empty, and an accessory group with a volume condition showed up on no product at all. The add-on now reads the feature kind in the old shop and matches it to ours right away.
What to do after updating
If you have already moved and see an empty volume or weight on your product pages, open «Settings → Diagnostics»: the numeric features check will find such features and repair them with a button. There is no need to move the catalogue again.
You can see which languages the content moves in
If the old shop runs a multilingual app, translations of names, descriptions and SEO move together with products and categories. The connection check now shows exactly which languages are filled in there and how many translations each one has, and while the move runs those languages are shown right under the progress bar.
A language your shop does not have yet is marked separately: there is nowhere for its translations to land. You do not have to add it by hand — the same screen offers an «Add the missing languages» button. The languages are added switched off, so nothing changes on the storefront until you turn them on yourself.
Photos travel through the bridge file directly
The bridge file now serves a photo as it is, instead of packing it into a string inside the answer. Every photo used to grow by about a third on the way and to sit whole in the memory of both servers — on a catalogue with thousands of photos that is wasted time and extra load on a shop that keeps working.
You do not need to download a new bridge file for this: the one already placed on the old site keeps working, and a new move takes the file in its updated form right away.
Nothing extra is asked for
If the old shop is on this same server, or a bridge file lies next to it, the migration no longer asks for the site address or an access key. The add-on reads the names of your order statuses straight from the settings of the old shop, so the matching screen shows «Packing» instead of «na-upakovke».
Photos in these two cases move as originals: the files are taken from the disk of the old shop instead of being downloaded from the site as downscaled copies. All that is left to enter is the shop folder (or the address of the bridge file) and the language of the content being moved.
Moving without the database credentials of the old shop
To move a shop you previously had to dig up the database credentials of the old one, and hosting providers almost always close the database from outside — that is where the move used to stop. There are now four ways to connect, and two of them ask you for nothing.
If the old shop is on this same server, point to the folder it lives in: the add-on reads the database credentials from its own settings. If it is on another server, download a small bridge file, put it next to the old shop and give the address of that file. The file only reads the old shop and changes nothing in it, answers only requests carrying your key, and after a week it stops working and deletes itself. Finish the move earlier and you can remove it with a button on the migration screen.
The migration progress is visible
The migration screen shows the current step, a progress bar, how many records have been moved out of how many were found, how long the work has been running and how many records did not make it. Below are all the stages with counters: finished, current and waiting.
A transfer can be forgotten and started again
A transfer remembers what has already been moved and does not create the same records twice. If the moved data was later removed — the shop was reset or the catalogue cleaned — that memory got in the way: products counted as transferred and the report showed zero, while orders did not arrive because their lines referred to deleted products.
The transfer screen now has a «Forget the transfer» button. The shop stops remembering the previous mapping, and the next transfer starts from scratch. Products and orders already transferred stay where they are.
The migration wizard is back in the panel
Moving works in full again: connecting to the old shop with a link for the access token, linking the reference lists — with a search and one-click linking of matching names, picking the feature that used to be the brand, and the move itself in batches with live counters. The screen picks up an unfinished move on its own: close the tab, open it again and it continues from the same place.
Units of sale come across correctly
When migrating, units from the other platform are written as free text. They are now matched against your shop directory, so products arrive with the unit they were sold in — kilograms, metres, litres.
An icon of its own
In the «Plugins» section and in the list of installed items the add-on now shows its own icon instead of an identical box, so you find the one you need at a glance. The icon appears on shops running version 1.30.0 and newer.
A status from the old shop with no match in yours is now created instead of being replaced by the starting one: this used to drop thousands of orders into «New» and wipe out the history — «Awaiting payment», «Packing», «Frozen». The new status takes the name you gave it on the matching screen.
The connection check no longer confuses an unreachable database with a foreign one: with a closed port or a wrong password the shop used to answer «this is not a Webasyst database, check the name», and owners edited the database name for nothing. The connection is now checked separately, and the reason comes from the database server itself and stays on screen.
Fixed the transfer of attribute values: some values arrived without a name, leaving a row of empty fields in the attribute editor and empty filter entries in the shop. The name is now taken from whichever field the old shop keeps it in, and a value without a name is not created at all.
Свои статусы старого магазина показываются названиями, а не кодами: названия подтягиваются по ключу доступа либо задаются вручную на экране связывания.
Исправлен переезд напрямую из базы: справочники для экрана связывания больше не требуют ключ доступа к старому магазину.
A second way to connect has appeared — straight to the old shop database.
It is faster, does not trip over the quirks of the network exchange, and brings across what the network cannot give at all: content translations. Names, descriptions and SEO arrive in every language filled in at the old shop, together with feature names, their values and purchase option names. The old shop is still only read from.
The credentials come from the old shop settings file. If the new shop sits on the same server, localhost is enough.
The previous access-key method remains and has been fixed: orders no longer stop at the ten-thousandth one and feature values are no longer lost.
Order migration no longer stops at the ten-thousandth order.
For some numbers the old shop answers incorrectly: asked for “orders after 10000” it returns orders from the very beginning, and it invents the record count. The migration trusted that, could not move on, and declared itself finished — about 15% of orders actually arrived while the owner saw “done”. Orders are now walked by record count, every batch is verified, and on failure the migration stops with a reason instead of reporting success.
Feature values are no longer lost. Previously only colour and dimensions arrived, while material, manufacturer, purpose and other text stayed empty. On top of that, half the features lost their list of values, and multi-value ones kept only the first.
The reason a migration stopped is no longer crowded out of the report by notices about products that were not found.
Переадресация со старых адресов убрана из переноса — она настраивается отдельным плагином.
Перед запуском переноса объяснено, что происходит с покупателем, который в магазине уже есть: его находят по телефону или почте, карточку дополняют, а не переписывают, заказы привязывают к ней же.
Фотографии переносятся мелкими порциями и не замирают, ошибки описываются словами, артикулы считаются отдельно от товаров.
Переезд живёт в «Настройках плагинов». В связывании показываются названия ваших записей, а не номера; справочники разбиты на блоки; оплата и доставка убраны.
Переезд живёт в «Настройках плагинов» и работает без настройки сервера: порции идут сами, на экране видно текущий этап и счётчики. Справочники разбиты на блоки, оплата и доставка из связывания убраны.
Ключ доступа к старому магазину теперь выдаётся по кнопке: введите адрес магазина — и ссылка соберётся сама, вместе с возвратом в этот магазин.
Переносит склады старого магазина вместе с остатками на каждом из них. Склад можно связать с тем, который уже есть в магазине, — тогда остатки лягут на него, а его настройки не изменятся.
Добавлены фотографии, покупатели, заказы и переадресация со старых адресов.
Первый выпуск: перенос каталога с Webasyst (Shop-Script) — категории, типы товаров, характеристики, товары с артикулами.