Data migration

Check the records before they become the starting point.

We agree the scope, review the available exports, report warnings and blockers and run a test migration before the final cutover.

Migration reviewOperiQ Merchant workspace using fictional demonstration data
Illustrative destination · fictional data

Before any import

Confirm what is available and what needs attention.

Written scope

The datasets, source formats, exclusions, mapping decisions and acceptance checks are agreed before identifiable data is supplied.

Validation first

Preview and validation identify blockers, warnings, duplicates and unresolved references before apply.

Customer sign-off

Stock, balances, VAT and sample documents are checked before final go-live approval.

A controlled sequence

From export to reconciled starting point.

  1. 01ScopeAgree records and exclusions.
  2. 02ValidateReview warnings and blockers.
  3. 03TestRun the migration in the isolated workspace.
  4. 04ApproveReconcile and confirm launch.

Migration scope depends on the current system, available exports and data quality. Everything included is confirmed in writing before work begins. No guarantee is made that every legacy field can be imported.

Start with a sample export and a written scope.

Do not send real merchant files through the public demonstration form. The approved authenticated migration process is used after account setup.