Switching guide

Plan the merchant software move before the cutover.

A migration is not complete because a file imported. Products, accounts, balances and outstanding work need an agreed scope and a reconciliation that the merchant can approve.

OperiQ product team8 minute read

01

Write down what is moving

Start with the records the team must use on the first working day: products, customers, suppliers, stock, opening balances and outstanding documents where suitable source information exists. Identify anything that will remain in an archive or require a manual decision.

The written scope should name responsibilities, exclusions, temporary source-file handling and the acceptance checks used before launch.

02

Validate before the final import

Exports often contain duplicates, incomplete fields, obsolete records or totals that do not reconcile. A test import creates time to classify those issues without putting the live opening position at risk.

Unsupported rows should appear in an exception report. They should not be changed silently merely to make an import complete.

  • Inspect available exports
  • Agree field mapping and exclusions
  • Run a test import
  • Review exceptions and samples
  • Reconcile opening totals
  • Approve the final cutover

03

Train around roles and exceptions

Owners, managers and counter staff do not need identical training. Each role should practise the work it will perform, including a return, unavailable stock, account query and end-of-day exception.

The launch decision should be deliberate. Confirm data, users, devices and support arrangements before switching rather than allowing the calendar alone to decide.

See the workflow

Use a real merchant scenario.

Explore the product with fictional data, or bring a workflow you want to test in a guided conversation.

Explore the demoAll guides →