POS Sales History Migration

Native imported transactions, reconstructed records, and a readable archive serve different needs. Agree the reporting and customer service outcome before selecting a method.

Review dates, taxes, returns, tenders, customer links, and line items. Test whether creating a historical record affects stock, notifications, accounting, or current reports.

• Receipts and line items → supported records or archive
• Customer association → verified identity crosswalk
• Returns and taxes → retained reporting context
• Import side effects → reviewed test results

An illustrative archive can retain receipt details and source totals without creating new sales in the destination. A native-history requirement needs a separate feasibility decision.

• Define the outcome: native transactions, a searchable archive or retained source access. Do not present these as interchangeable.
• Agree required date coverage and verify a known receipt, its line items, tender, customer association and any return.
• Reconcile a period total with source reports and retain tax, timezone and currency context.
• If a native import is proposed, check inventory movements, customer messages, accounting exports and reports in a controlled test.
• Shopify lists separate methods for historical orders; its customer CSV does not carry orders. X Series documents a standard bulk sales import limitation.

Use the migration checklist to assign the decision owner and acceptance evidence. Confirm inclusion in the written scope after a secure sample review.

Current vendor instructions inform this guide; account access and the selected workflow still need confirmation.

• Shopify migration methods
• Shopify customer CSV requirements
• Lightspeed X Series historical sales limitations