Velicoo

migrating to velicoo

We've done this before. Not the most exciting part of our job. We do it well anyway.

Most wholesale migrations stall on one of three things: ERP-coupled SKUs, contract pricing that nobody documented, and URL redirects nobody wants to own. We've shipped past all three — including a ~115,000-customer Shopify cutover that is now live as nutri.se.

Shopify Plus B2B · BigCommerce B2B Edition · Adobe Commerce (Magento) B2B · PrestaShop · WooCommerce + B2B plugins · Spryker · Custom legacy

from

01from

Shopify Plus B2B

Volume tiers, contract pricing and net-30 work, but barely. Your buyer experience is still consumer-shaped.

we move
Products, variants, companies, buyers, contract prices, order history, discount codes, redirects.
tricky part
Multi-country VAT and reverse-charge are where Shopify gets uncomfortable. We handle this natively.
02from

BigCommerce B2B Edition

Decent on paper, but the B2B layer is grafted on and ERP integration usually comes from third parties.

we move
Companies + roles, price lists, quote requests, customer groups, order history, content pages, redirects.
tricky part
Quote-request data moves over so you don't lose negotiation history.
03from

Adobe Commerce (Magento) B2B

Powerful, costly, paying for capability you don't use. Time-to-change measured in quarters.

we move
Products, variants, company hierarchies, shared catalogs, negotiable quotes, invoices, redirects.
tricky part
Largest job we do; typical migration two to four weeks. We scope every Magento move individually.
04from

PrestaShop

Most cross-border distributors we meet are here, frustrated.

we move
Products, customers (B2C and B2B), order history, addresses, discount rules, URL redirects.
tricky part
Repeatable, low-risk. We've done several end-to-end.
05from

WooCommerce + B2B plugins

Patchwork drifts and breaks under cross-border tax. Plugin maintenance is a tax of its own.

we move
Products, variants, customers, orders, coupons, redirects. B2B-plugin data per-case.
tricky part
If you're using B2BKing / B2B for WooCommerce, expect a sandbox of it on our side first.
06from

Spryker

Mid-market enterprise B2B with high TCO. Customers move because the cost of change finally drops below the cost of staying.

we move
Catalog, companies, contract pricing, order book, content. Spryker schemas are unusual — we scope before promising.
tricky part
Bigger lift; typically a custom Growth+ scope with dedicated weeks.
07from

Custom legacy

It worked, until your ERP changed and your CFO asked for an audit trail.

we move
Whatever lives in your DB. We start with a read-only export and a working day of analysis.
tricky part
Honest answer here is always 'depends'. Small paid discovery phase up front.

how we run it

Five visible phases. No surprises.

1–3 days

01 · discovery

Read-only export from your platform, ERP and WMS. Written scope, including what we will and won't move.

1–2 weeks

02 · sandbox

Migrated catalog + accounts on a staging URL you can test as buyer, admin and finance role.

parallel

03 · integration

ERP, WMS, carriers and analytics wired while the sandbox stabilises.

one day

04 · cutover

DNS swap, redirects live, buyers can log in. We watch from your side for 24 hours.

2 weeks

05 · stabilisation

Bugs, edge cases and 'oh, we also do this' fixed on the same SLA your real customers get.

Send us a read-only export. We'll send back a real scope.