Moving to Skuvelo from another tool

Moving from another inventory or planning tool is a sequence of exports from the old system and uploads into Skuvelo, in an order that keeps every number explainable afterwards. Nothing is copied over automatically from another vendor's account, and nothing in the old system is changed by the move.

What to export from the tool you are leaving

Before you cancel anything, export these from the old system while you still have access. Most tools export CSV; XLSX works for the product list.

• Product list: SKU, title, cost, selling price, category or brand, and the supplier each item comes from with its lead time and minimum order quantity.
• Stock on hand by location, counted as close to the switch date as you can manage.
• Order history, one row per order line, with the date, quantity, unit price and whether the order shipped. Around twelve months gives the forecast a useful baseline, and seasonal methods wait for two full years of weekly history. The forecast reads the latest 78 weeks, so a year of history per item is what lets like items share a seasonal shape. Export all the old tool holds.
• Purchase history: supplier, PO number, SKU, quantity ordered and received, cost and dates, with the orders still on their way kept apart from the ones already received.
• Supplier price lists, if the old tool held them separately.

Reorder points, forecasts and planning settings do not export in a shape Skuvelo can read, and they do not need to: Skuvelo recomputes them from the history above (see Reorder points and safety stock). Keep a screenshot of the old tool's reorder points so you can compare.

The order to bring it in

Each of these is a separate upload on Settings → Import data. Load them in this order, because each one refers to the one before it:

1. Products first, including the supplier, lead time and MOQ columns, so every later row has a SKU to land on and every item can be planned.
2. Stock on hand, by location next, as a count. Skuvelo records each row as a dated opening balance (or, where the SKU already has stock movements at that location, an adjustment for the difference), so the starting figure stays visible later.
3. Order history, on the card labelled Sales history, with status: fulfilled on everything that already shipped. A blank status is rejected rather than guessed, because an open order would reserve stock and contribute nothing to demand.
4. Purchase history for the orders already received, so lead times come from what each supplier really delivered, then Open purchase orders, on its own card, for the orders still on their way, so they count as incoming supply.
5. Supplier price lists last, so landed cost and MOQ come from the current terms rather than an old PO.

Column names, accepted aliases and the Inventory Planner and Prediko presets are in Bringing your data in from a spreadsheet. Every upload leaves a receipt under Import history that counts what landed and lists rejected rows with the reason (the first 200 on a stock, sales, purchase or price-list file), and uploading the same file twice does not double-count.

If a store or marketplace is connected

When a sales channel is connected it syncs products, stock levels and orders itself. The stock levels and sales history uploads show as locked so a file cannot write a second copy of what the sync owns, and the products upload only updates SKUs that already exist, field by field, without creating new ones. Two ways to run the move:

• Connect the channel first and let it bring products and orders, then add only what the channel does not carry: the stock count (the channel is not the authority on your shelves), entered on Inventory → Cycle counts because the stock levels upload stays locked, then purchase history and price lists.
• Upload the files first, including the old tool's richer history, then connect the channel. The sync takes over from there.

Either way, the on-hand count comes from your own count or opening balances, never from the old tool's belief about stock. See What to expect after your first import for the first weeks after the switch.

What does not carry across

Logins, roles and permissions are set up fresh in Skuvelo: invite each colleague from Settings and give them the role that matches their job (see Inviting your team and choosing roles). Automations, alert rules and report layouts from the old tool are rebuilt here, mostly in Notifications and Reports. Attachments, notes and images on items do not import, except an image_url column on the product file.

Running both in parallel

A common pattern is to run the old tool and Skuvelo side by side for one reorder cycle. Load everything above, then compare Skuvelo's reorder recommendations against the old tool's on the same day. Where they differ, the item's reorder point in Skuvelo shows its inputs, so the difference can be traced to a lead time, a sales window or a count rather than argued about. Switch the purchasing team across once the numbers agree or the differences are understood.

Where a person steps in

Ask in Help with the name of the tool you are leaving ("migrating from SoStocked, where do we start") and Help brings this guide together with Ask a person, which sends your question to support with the guide and the page you were on already attached. Use it for an export the old tool will not produce, a file the importer rejects after the receipt has been read, or to have someone check the first uploads before the team moves over.