Switching POS systems: a practical migration checklist
Plan a checkout changeover with clean product records, sample imports, opening counts, staff practice and a controlled first shift.
Last updated October 31, 2026
Moving to a new checkout is a change to daily trading, product records and staff routines. Plan what must move, test a small sample and choose a clear changeover time. Keep the old system accessible until you can explain the new opening balances and retrieve the records you still need.
If you are moving from a basic till and a spreadsheet, the same steps apply. Your first job is to turn informal records into a product list that the new system can use consistently.
POS migration checklist
Assign one person to coordinate the move and name a backup. Set a date for each checkpoint:
- Confirm the new system supports your required trading workflows.
- List the records to transfer and the records to archive.
- Download and protect the original exports.
- Map the old fields to the new provider's current template.
- Import and test a representative sample.
- Train staff and rehearse the changeover.
- Capture final movements and opening stock.
- Review the first live shift before retiring old access.
Do not choose a date only because hardware has arrived. The checkout selection guide can help resolve requirements before you commit to a migration.
POS data export
Separate the datasets. Products, stock quantities, suppliers, customers, sales history, gift-card balances and open orders may use different exports or need specialist migration support. List each one with its owner, record count and destination.
Keep an untouched copy of every original file and work on duplicates. Record the export time and time zone. Restrict access to files containing customer information and use the provider's supported secure migration route for sensitive account or payment-related records.
Ask what an export leaves out. Images, attachments, discount rules and linked records may not be included in a product spreadsheet. Being able to read a file is different from being able to recreate every workflow from it.
Clean product data before migration
Check missing codes, duplicate items, inconsistent units and unclear variants. Preserve leading zeros in barcode values by treating them as text. Distinguish a blank quantity from a confirmed zero, and a retail price from a purchase cost.
| Source detail | Check in the destination |
|---|---|
| Internal product code | Same identity, with no accidental duplicates |
| Barcode | Full value preserved and correct item found when scanned |
| Size, color or pack | Correct variant or bundle behavior |
| Price and cost | Separate fields with the intended currency |
| Stock quantity | Correct location, unit and quantity type |
Use the current provider template rather than renaming columns by guesswork. Shopify's product CSV reference documents required fields and dependencies, and directs stores with multiple locations to a separate inventory CSV for quantities. Other platforms have their own rules.
POS migration test plan
Choose a small sample that includes your awkward products, not only the easy ones. Include variants, a zero-stock item, a long barcode and a product with a discount. Use a vendor-approved test environment or a clearly controlled trial.
After importing, scan each item and compare the result with the original record. Check descriptions, prices, stock, receipts and reports. Test the return of one item from a larger transaction and the correct treatment of damaged goods.
Check what another import would do before attempting it. Shopify's import guidance explains that matching records can be overwritten and that blank fields can clear existing values. It recommends backing up product data first. A second upload is not automatically a harmless retry.
Keep a short defect list with the failing step, expected result and owner. Repeat failed cases after the correction. Move to the full catalog only when the sample passes.
POS opening stock count
Set a cutoff time and define how movements around it will be handled. Count each location, record late deliveries and separate goods in transit. Use the stocktake tool to prepare a count sheet if you need one.
For a fictional example, the final count shows 72 candles at 8 p.m. If three sell before the new system starts, its opening balance should reflect those sales once. Importing 69 as the opening quantity and replaying the same three sales would reduce stock twice.
Choose one method for bridging the gap and record it. The checkout stock guide explains how to reconcile quantities by movement.
Train staff on a new POS
Practice ordinary sales, failed payments, refunds, unreadable labels, price corrections and closing. Train people using the permissions they will have on shift. An owner demonstration can hide steps that require approval for a cashier.
Put the support contact, outage procedure and escalation owner beside the checkout. Use the shift handover tool to record unresolved issues so the next team knows which workarounds have been approved.
POS go live checklist
Before the first live customer, check the active location, staff access, payment connection, receipt details and starting cash. Confirm the imported catalog and opening stock totals. Keep a dated sign-off from the person responsible for each area.
Set a fallback decision point. Name who can pause the rollout and how transactions will be recorded if that happens. Avoid running both systems as independent live checkouts without a reconciliation plan, because split records make the next opening balance harder to trust.
Frequently asked questions
Can I move sales history to a new POS?
It depends on both providers and the available migration route. Product import support does not establish support for past sales. Ask whether transferred history is searchable, usable for returns and included in reports. Keep a readable archive if the new system cannot reproduce what you need.
When should I cancel my old POS?
After the first live records reconcile, required exports are checked and the provider confirms how you will handle older returns and remaining balances. Review notice periods before the move. Set cancellation against those concrete checks, rather than assuming the first successful sale means the migration is finished.