Two rules that hold throughout
Break either of these and you get double-sold stock or money you cannot reconcile.The nine steps
Check what was migrated
Done when: your counts and prices reconcile against 1.0, and anything that did not has an owner.
Configure settings
Done when: every settings view has been opened and either configured or confirmed as not needed.
Connect payments
Done when: a live-mode payment has been taken and refunded.
Move your subscription
Done when: your trial has started and your 1.0 subscription shows as canceled.
Test your processes
Done when: your own people have run every case, unaided, and seen the customer-facing output.
Set up and train your team
Done when: every user has the right role and each location has a named superuser for the switch.
Clear the external dependencies
Done when: your store address is live, integrations are repointed, and 1.0 exports are stored outside TWICE.
Switch new orders to 2.0
Done when: every 1.0 intake channel is closed and you have placed a real transaction in 2.0.
Run both systems until 1.0 is finished
Done when: the last pre-switch order is closed and your records are stored outside TWICE.
If you do not take bookings
Work through every step anyway. Expect 1.0 to empty in days rather than seasons. Several steps exist because a booking is made on one date and fulfilled on another: running both systems down, blocking stock out on a 1.0 booking, releasing deposits from the 1.0 order.Confirm anything outside the default scope
Confirm anything beyond the default scope with your TWICE contact rather than assuming it moved. This path covers what migrates by default.Related articles
Launch path
The same sequence for a new account rather than a migrated one.
TWICE Commerce overview
What the platform does and how its pieces fit together.