No. Before the switch, set the migration scope, then use your own sample to make counts and identifiers match; without a sample run, “migration is possible” has no place in the switch plan. How to do it: Migration: scope first, then sample.
Each data set has only three destinations: migrate into the new system, archive only, or stay accessible in the old system. Run the sample with a real store export in a non-production environment, checking fields, accented characters, dates, identifiers, amounts and readability. For every mismatch, record which class it falls into; do not close it out as “close enough.” Limited pilot: limited pilot. Rollback rehearsal: rollback.
We do not carry out migration for you, do not do on-site cutover, and do not guarantee that 100% of your data will migrate. General information; last checked 2026-09-27.