Square for Retail Migration Guide

Record the Square application, plan and locations, along with any online store or apps that retain separate data. The item library, customer directory and historical orders should be treated as separate datasets.

Square documents item library export and bulk import through its Dashboard. Export all intended items rather than an accidental filtered subset, retain the original file and work from a copy.

A Square Token identifies a variation in its account. Square’s instructions distinguish updating the same account from transferring to another Square account. Keep account-specific tokens in your mapping evidence; do not assume they are identifiers another POS can use.

Choose an item with multiple variations, one barcode with leading zeros and an item sold in more than one location. Preserve identifier text and match the receiving location names. Check tax and price setup separately from simply finding the item in the library.

An item file is not a customer export or an order archive. Identify the available customer fields and proposed match rules. Gift cards, loyalty and historical transactions need their own review; no all-data transfer is implied.

For an inbound Square move, use its current template and confirm required fields and import permissions. For an outbound move, inspect the destination’s template before changing the export. Reconcile variation counts and stock for each included location after a representative test.

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

• Square item import and export instructions