Included in your core POS

Move your store
to spinachPOS.

Bring your data from Clover, Square or Lightspeed. Match it, review it, then make the move.

Open migration tools

Catalog & customers

Products, quantities, variants, categories, tax rates and customer profiles.

Historical sales

Original transactions in a separate archive, without changing live sales or stock.

Opening balances

Verified outstanding gift-card value and loyalty points, recorded in their ledgers.

A careful move. A fresh start.

Example · Square product export

Review before importing

2 valid · 1 needs correction · Nothing saved yet

shirt-001Linen shirtReady
hat-002Canvas capReady
tote-003Market totePrice required
Illustrative review: errors remain outside the import until corrected.
  1. 1

    Export and back up

    In Clover, Square or Lightspeed, export CSV files for products, customers, categories, tax rates, transactions and outstanding balances. Exports vary by edition. This is a file-based migration, not a direct account connection. Keep the original files safely backed up.

  2. 2

    Prepare your store

    Set your store currency and Retail / Restaurant / Both mode. In Back office → Move your store, select the old POS and the original location ID. Reuse that same ID for every file from that location; each file's data type is detected from its columns and can be changed. Download a column template if your export needs reorganizing.

  3. 3

    Match the columns

    Add your CSV files (up to 10 MB and 20,000 rows each). Queue all your exports at once — products, customers, taxes, sales, balances — then match columns for one file at a time. Match original record IDs, names, prices, inventory and other fields. Prices are in dollars unless the header says cents. Map first and last names or a full name for customers. Keep barcodes and IDs as text. Unmapped fields are discarded.

  4. 4

    Review, then import

    Review row errors and totals before confirming. Valid rows import; invalid rows need correction. Existing products and matching customers are not overwritten. Save the results file, resolve conflicts and retry: the same original IDs from the same location are skipped, not duplicated. Keep the page open until it finishes.

  5. 5

    Reconcile and go live

    Check stock, products, customer counts, tax settings and balances against your exports. Import categories and taxes first, parent products before variants, and customers before linked transactions or loyalty balances. Test a sale before switching over.

Protect every balance.

Activate Gift Cards or Loyalty before importing their balances. Stop redemptions in your old system at the agreed cutover time. Gift cards need a full 8–32 digit number, a known or replacement 4–8 digit PIN and a positive outstanding balance. PINs are hashed; the import archive stores only the card’s last four digits. Customers with existing loyalty activity cannot receive an opening balance.

Know what needs separate setup.

Historical sales are available under Import history, not live register receipts, refunds or tax reports. Import one transaction per row; line items can be preserved as original receipt details. Payment credentials, employee PINs, photos, kitchen routing, modifier groups, subscriptions, open checks, layaways and orders are not automatically transferred. Set those up separately or ask support to help with your cutover.

Ask for migration help