Most Square POS migration failures are preventable. Catalog uploads usually break because an edited spreadsheet no longer matches Square’s current template; saved cards require a separate, compliant transfer; gift cards, subscriptions and appointments need their own cutover plan; and pending offline payments can be lost if a device is reset too soon.
The safest approach is to freeze the source account, create untouched exports, repair data in the original workbook, migrate in stages, and validate counts, money and a live transaction before staff switch systems.
As an Amazon Associate I earn from qualifying purchases.
Start with a freeze, backup and rollback point
Do not begin by deleting items, signing out devices or changing locations. Treat the existing Square account as the source of truth until the replacement system has passed testing.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Freeze routine changes. Choose a short test window during which staff do not add products, alter prices or create customers in both systems. Keep the Square account read-only for the test period where operationally possible.
- Export the item library. Save the file exactly as downloaded and make a second untouched copy. Square recommends a distinct backup export so you can revert if an edit or import removes information.
- Export financial and customer records. Save customer data, sales and transaction reports, gift-card reports and any accounting exports needed to reconcile the old and new systems.
- Record your cutover baseline. Note item and variation counts, inventory by location, open orders, customer count, outstanding gift-card value, subscriptions, appointments and any card-on-file customers. These figures become your reconciliation checklist.
- Document dependencies. List printers, scanners, cash drawers, payment readers, tax rules, modifiers, receipt settings, staff permissions, Wi-Fi credentials and each physical sales lane.
A rollback point is more than a copy of the catalog. Keep the original files, reports and the date and time of each export together so a discrepancy can be traced to a specific change.
#1 Best Overall
Repair catalog and inventory imports
Catalog imports are the most common technical failure. Square’s importer expects the current template’s structure, not merely a spreadsheet containing similar information.
Use the current template without altering its structure
Download a fresh item-library export or current import template from Square Dashboard. Keep the original column order, retain empty columns and do not delete or rename the Token column or edit Token values. Save only as .xlsx or .csv; Square states that the item import tool will not work with .xls, .xlsm or other file types.
Do not copy data into a homemade workbook and assume matching headings are sufficient. The export can contain structural fields that are not obvious in a spreadsheet program. If a destination system has its own format, maintain two files: an untouched Square-format workbook and a separate mapping sheet for the destination.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Fix values that the parser treats as invalid
- Unique names: Every item must have a unique item name. Repeated names can cause rows to reject or merge unexpectedly.
- Categories and descriptions: Item and variation category values must align, and descriptions must use the values expected by the template. Inconsistent category or description text across related rows is a frequent cause of rejection.
- Commas and delimiters: Remove commas from fields when the import parser interprets them as separators. If a comma is essential to a customer-facing description, test that field in a small file first and confirm how the parser handles quoted text.
- File format: Save as Excel workbook or comma-separated values, then reopen the saved file to confirm it still contains the expected columns and rows.
Import a small representative sample before sending the complete catalog. Include an item with variations, an item with a modifier, taxable and non-taxable items, a product with a SKU and an item stocked at more than one location. A sample exposes mapping problems without putting the full library at risk.
Protect SKUs, GTINs and leading zeroes
Spreadsheet programs can silently change identifiers. A CSV editor may remove leading zeroes from a SKU or display a long SKU in scientific notation. Those altered values no longer match labels, purchase records or inventory counts.
- Format SKU columns as Text before opening or pasting values.
- Prefer the
.xlsxexport when possible, because it is less likely to reinterpret identifiers during ordinary editing. - Inspect several long SKUs and every SKU beginning with zero before saving.
- GTIN fields must contain digits only and use a length supported by the importer. Remove spaces, punctuation and hidden characters.
If a spreadsheet program has already converted values, return to the untouched export rather than trying to reconstruct identifiers from the damaged file.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Use the error report correctly
A partial upload is not a reason to start over blindly. Download Square’s error report, identify the rejected rows and correct the original workbook, not the error report. The report is a diagnostic output; it is not designed to become your next import file. Re-upload the corrected original after checking the same rules for names, categories, descriptions, identifiers and file type.
Keep a versioned copy after each correction. If a second upload rejects different rows, you can compare versions and isolate the change that caused it.
Plan for fields that do not transfer
Tax rates and modifiers may not carry through a transfer. Rebuild them manually in the destination, then test the resulting price and tax calculation on representative items. Compare the displayed tax, the receipt and the amount posted to the payment record; a catalog that looks correct can still calculate incorrectly at checkout.
Move customers and saved cards as separate projects
A customer-directory export and a card-on-file transfer are not the same operation. Complete the ordinary customer export first, then handle payment credentials through the formal processor-to-processor process.
Export ordinary customer records
In Square Dashboard, use Customers > Customer directory > Import / Export > Export customers. Preserve the resulting file and record its customer count. Before importing it elsewhere, decide how the destination will match duplicate email addresses, shared phone numbers, blank fields and customers who appear in multiple locations.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Do not assume that importing names and contact details also imports purchase history, marketing consent, loyalty status or payment methods. Check the destination’s field mapping and consent requirements separately.
Transfer saved cards only through a compliant processor
Square does not provide a general spreadsheet export of usable card numbers. The account owner must contact Square Support to request a card-data transfer. Square says it transfers card data only to another PCI DSS Level 1-compliant processor and sends an encrypted file directly to that processor. The average export timeframe is up to two weeks; the receiving processor then has its own import work, which Square describes as taking up to 15 business days after it receives the encrypted file. These are service-time estimates, not guarantees.
The new processor must map Square card and customer IDs to its own customer records. Give it a clean matching key—usually the destination customer ID plus verified contact information—and resolve duplicates before charging any migrated card. Never email card details, put them in a shared drive or ask staff to copy them into a spreadsheet.
Schedule this work well before the payment cutover. A customer import can finish in a day while the compliant card-transfer process takes weeks. Until the mapping is confirmed, keep a secure, approved method for customers to enter a card again.
Handle gift cards, subscriptions and appointments separately
Square’s card-data migration process explicitly excludes gift cards, subscriptions and appointments. They are liabilities or scheduled obligations, not ordinary customer fields.
Reconcile gift-card value before honoring cards in the new POS
Export gift-card summaries and inspect individual transaction histories in Square Dashboard. Reconcile four values:
- issued value,
- redeemed value,
- remaining balance, and
- liabilities between locations.
Compare the total outstanding balance with the destination’s gift-card liability report. Investigate cards with a zero balance, partial redemptions, refunds, transfers between locations or unusual adjustments. A barcode scanner can help validate physical cards during testing, but it does not transfer balances by itself.
Rank #4
If the destination cannot import Square gift-card numbers, maintain a controlled lookup ledger containing the card identifier, verified balance, migration date, adjustment history and the employee who approved the entry. Publish a clear redemption policy for customers and confirm the accounting and legal treatment in your jurisdiction before converting or replacing cards.
Subscriptions and appointments need an operational cutover
Export subscription details, renewal dates, entitlements and cancellation status into a restricted working file, then recreate them in the destination’s subscription or scheduling tools. Export future appointments with customer contact details, service, staff member, location and time zone. Assign an owner to contact customers if an appointment time or payment method changes. Do not mark a workstream complete merely because the customer record exists; verify the next charge or appointment itself.
Prevent offline-payment and device losses
Pending offline payments are the highest-risk cutover item because the money may not yet have reached Square. Square states that pending offline payments can be permanently lost and the funds will not be captured if prohibited actions are taken first. It also says offline payments should be uploaded within 72 hours from the first payment.
Safe sequence before sign-out, reset or replacement
- Reconnect the device to a reliable internet connection.
- Open the Square app and confirm that every pending offline payment has uploaded and no offline banner or pending queue remains.
- Check the transaction report against the receipts and cash count.
- Only after the queue is clear, sign out, delete the app, switch modes or locations, or factory-reset the device.
Never perform those actions while offline payments are pending. The 72-hour period is an upload window, not permission to delay the upload until the last minute.
Troubleshoot the Square app without risking a live lane
Perform disruptive steps after hours where possible. Square’s troubleshooting sequence is:
- Update the device operating system and Square app.
- Check the app’s required permissions.
- Force-quit and reopen the app.
- Sign out and sign back in only after confirming there are no pending offline payments.
- Restart the device.
- Reinstall the app as a last step, again only after pending payments are uploaded.
Stage replacement hardware and network credentials before the old lane is taken offline. Keep the old device available until the replacement has passed a transaction test and all historical payments are reconciled.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Stage a destination migration instead of switching everything at once
A staged sequence limits the number of variables that can fail together. Shopify’s official migration guide is a useful example because it separates products, customers, reviews, orders and inventory quantities; the same order works as a general model for another destination.
- Products: Import the cleaned catalog, variations, SKUs, prices, categories, descriptions, taxes and modifiers. Confirm that each item is unique.
- Customers: Import ordinary customer records and resolve duplicate matches before attaching orders or payment methods.
- Reviews or other customer content: Transfer only if the destination supports the required identifiers and consent. Verify that each review remains attached to the correct product.
- Orders: Import historical orders after customer and product IDs are stable. Check order totals, refunds, discounts, taxes and payment status.
- Inventory quantities: Load quantities by location last, after the catalog and location mapping are fixed. Freeze stock movements during the final count or record every movement made during the count.
Run the staged import in a test environment or with a limited sample first. Do not connect live payment capture until the sample has passed reconciliation.
Validate the replacement system before go-live
Use a written comparison rather than relying on a visually similar dashboard. The following checks expose the gaps that most often become expensive after launch.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall| Area | What to compare | Pass condition |
|---|---|---|
| Catalog | Items, variations, categories, descriptions, SKUs and GTINs | Counts match the source baseline and identifiers retain their exact characters. |
| Inventory | On-hand quantity by location and stock movement timing | A physical or controlled sample matches in every location. |
| Customers | Names, contact fields, duplicate handling and consent records | Each source customer has one intended destination record or a documented exception. |
| Orders | History, refunds, discounts, taxes and payment status | Selected orders reproduce their original totals and statuses. |
| Gift cards | Issued, redeemed, remaining and inter-location liability | The destination liability agrees with the reconciled ledger. |
| Saved cards | Processor eligibility, ID mapping and token status | A test customer can use the mapped method without exposing card data. |
| Taxes and modifiers | Rules, rates, included/excluded tax and modifier pricing | Test receipts and accounting entries calculate correctly. |
| Hardware | Readers, scanners, printers, drawers and network credentials | Each lane completes a sale, prints or sends a receipt and closes the day. |
| Reporting | Sales, tender, tax, inventory and end-of-day reports | Reports contain the fields the owner and accountant require. |
| Support | Escalation path and response expectations | Staff know who handles payment, hardware and data discrepancies. |
Run a complete low-value test
Before switching lanes, perform a low-value sale that includes a taxable item, a discount or modifier where relevant, a receipt, a refund and an end-of-day close. Confirm the payment appears in the destination report, the inventory decreases at the correct location, the tax is posted correctly and the refund returns to the intended tender. Test a gift card and a migrated customer separately if those workstreams apply.
Go-live checklist and recovery rules
- Announce a precise cutover time and stop sales on the old lane at that moment.
- Bring every Square device online and verify that no offline payments remain.
- Capture a final transaction, inventory and gift-card report from Square.
- Record any sales, refunds or stock movements made during the final count.
- Enable the destination lanes and run the low-value test before serving customers.
- Keep the old account and exported files accessible but restrict edits.
- Compare the first end-of-day totals from the destination with the final Square baseline.
If a discrepancy appears, do not “fix” it by editing both systems. Stop the affected workflow, preserve the reports and identify whether the cause is a missing record, a duplicate, a timing difference, a tax rule or a payment-status mismatch. Correct the destination through its documented adjustment process and record the reason.
Common symptoms and the fastest safe response
| Symptom | Likely cause | Action |
|---|---|---|
| Import rejects the whole file | Wrong extension or altered template | Start from a fresh Square export, preserve columns and Token values, and save as .xlsx or .csv. |
| Only some rows fail | Duplicate names, mismatched category or description, delimiter or identifier errors | Download the error report, correct the original workbook and re-upload. |
| SKUs no longer scan | Leading zeroes removed or long values converted to scientific notation | Restore from the untouched export and import the SKU column as text. |
| Customer records imported but cards do not work | Customer export was mistaken for a card transfer | Begin the account-owner request with Square Support and the PCI DSS Level 1 receiving processor. |
| Gift-card balances differ | Gift cards were excluded from card migration or location liability was missed | Reconcile summaries and individual histories, then use a controlled ledger or supported import. |
| Payments disappear after device reset | Offline queue was still pending | Do not reset devices with pending payments; reconnect and upload first. Escalate immediately if a payment was already lost. |
| First-day tax or inventory totals are wrong | Manual tax/modifier rebuild or location mapping error | Pause the affected lane, compare a test receipt and stock count, and correct the destination rule before continuing. |
A successful migration is not the moment the new app opens; it is the point at which catalog, money, customer obligations and operational records agree well enough that staff can sell without creating a second reconciliation problem. Preserve the Square exports, complete the staged tests and keep a documented exception list until every outstanding balance and scheduled obligation has an owner.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
