What moved, and what did not
Treat the table above as what moves by default. Confirm anything else against your migration scope rather than assuming it came across.
Reconcile by value, not by row count
Reconcile by value, not by row count. Counting rows tells you the migration ran and nothing more: a price that moved a decimal place, or an add-on that did not come across, leaves the row count identical and the catalog wrong. Check totals: total stock value and total catalog value against the same figures in 1.0. Where they differ, find the specific listing rather than accepting the gap.Reconciling by value is the check most often skipped, and the one that surfaces problems while they are still cheap to fix. A price error found now is a correction; found after go-live it is a refund.
Done when
- Stock item counts in 2.0 match 1.0, per location.
- Listings match on price, or you have confirmed the new pricing is deliberate.
- Rental periods, add-ons and buyback prices are correct.
- Collections contain the listings you expect.
- Total stock and catalog value reconcile against 1.0.
- Anything that did not reconcile is written down, reported, and has an owner.
Related articles
Stock item vs SKU
What TWICE counts as a unit, and what groups those units.
Import customers
Bringing a customer list across from another system.
Migrating from TWICE 1.0
The full sequence this step belongs to.