Start with a specific area, agree who owns the data and test the connections before moving more. Migration from Magento or other solutions is planned around your actual operations.
A practical view of the process. The exact setup depends on your business and the capabilities you use.
Review products, prices, customers, orders, stock, accounting and URLs. Choose the first area and agree which systems remain.
Import a focused dataset, map columns and validate rows. Agree stable identifiers, variants, units and update behavior before loading everything.
Test orders, prices, stock, payments and integrations against agreed results. Where parallel runs are used, compare data before the new connection takes over.
Agree timing, checkpoints, training and who follows up discrepancies. The plan must also define what happens if a critical flow fails its checks.
Configuration, rules and boundaries to review before rollout.
The import flow includes analysis, column mapping, validation and jobs. The import wizard covers products, prices, customers, persons, orders, stock adjustments, redirects, suppliers, purchase orders, BOMs and production orders, among others. This does not replace assessing your source format.
Decide who updates products, customers, prices and stock. Avoid two systems writing to the same area without a clear conflict rule.
Existing URLs and content are part of moving a shop. Redirects (301 or 302) can be imported from a file. Test that important pages and links lead to the correct destinations; unchanged visibility is not automatically guaranteed.
No. The starting point is determined by needs and dependencies. It can be products, warehouse or commerce itself, with PullPush connecting the systems you keep.
It depends on data quality, integrations, theme, order and stock flows. We provide a concrete plan after discovery rather than a generic timeline promise.
Tell us where it hurts — and we will show you how Kaduno solves it. A 30-minute demo, in Norwegian or English.