How to Switch POS Systems Without Losing Customer Data — 2026 Guide

Switching POS is real work — anyone selling "one-click" is selling you something. But with a written plan, a clean export, and a mid-week 3am cut-over, restaurants do this every day without losing a receipt. This is the checklist we hand every operator migrating to Online eMenu from Petpooja, Foodics, Toast, Square, Lightspeed, POSist or a legacy on-premise system.

The 6 Reasons Restaurants Switch POS in 2026

We surveyed 340 operators across India, GCC, UK and Europe who switched POS in the last 12 months. Six reasons showed up over and over, usually in combination.

1. Pricing crept up. Toast, Square and Lightspeed charge 2.49-2.9% transaction fees on top of subscription. On $80k monthly revenue that's $2,000+ gone every month. A flat plan (Online eMenu ₹199/mo India, $9/mo international) recovers the cost in one billing cycle.

2. Aggregator sync started failing. Swiggy, Zomato, Talabat and Careem change APIs quietly. Older integrations break silently — orders disappear, 86-ing an item doesn't propagate. Refunds and one-star reviews follow.

3. WhatsApp gap. Most POS bolted WhatsApp on as a ₹1,500-₹2,000/mo third-party plug-in that doesn't share the guest database. Operators want native WhatsApp writing to the same CRM as dine-in.

4. Offline breakdown. Cloud POS is fine until the internet drops. Tier-2 India, monsoon GCC and rural Europe discover vendor "offline mode" often doesn't sync back cleanly.

5. Contract lock-in. Petpooja/POSist annual contracts, Toast hardware commitments, Lightspeed autorenewals. In 2026 operators want monthly billing with no lock-in.

6. Poor support. 48-72 hour ticket queues. Staff who don't speak Hindi, Arabic or the operator's language. WhatsApp-first support (24/7, seven-minute first response) is now table stakes.

What Data Actually Needs to Migrate

Not everything in your old POS matters. Here's what moves, in priority order.

Menu, prices and modifiers. Item names, categories, prices, tax codes, modifier groups (extra cheese, no onion, spice level), photo URLs, availability flags. Largest workload and where most name-mismatch bugs originate.

Guest database. Name, phone, WhatsApp opt-in, email, birthday, tags (VIP, allergic, corporate), preferred payment. Deduplicate on phone before import — the same guest appears 3-4 times in older databases.

Loyalty balances. Points, tier, expiry, lifetime spend. Highest-risk table — see the FAQ.

Past orders (last 12 months). Order ID, timestamp, items, discounts, tax, payment, channel. 12 months is enough for repeat-order analytics and audit trails. Archive the rest as CSV.

Tax records. GST/VAT filings, HSN codes, e-invoice IRNs, credit notes. India: 8 years. GCC: 5 years for ZATCA Phase 2. EU: 10 years for VAT audits.

Staff logins and roles. Employee list, PIN codes (rotate them, don't reuse), roles, shift schedules.

Aggregator credentials. Merchant and outlet IDs for Swiggy, Zomato, Talabat, Careem, Deliveroo, Uber Eats. You re-link, not migrate — but keep the IDs handy.

Receipt and KOT templates. Header, GSTIN/TRN placement, footer, logo. Screenshot before you cancel — most POS won't let you download the raw template.

The Pre-Migration Checklist (10 Items — Before You Cancel the Old Contract)

Do all ten before you touch the cancellation form.

1. Export menu CSV — items, modifiers, prices, tax codes.
2. Export guest database CSV — phone, email, tags, WhatsApp opt-in.
3. Export 12 months of orders CSV — items, discounts, taxes.
4. Export loyalty balances CSV — points, tier, expiry.
5. Screenshot receipt and KOT templates.
6. Note aggregator merchant IDs — Swiggy, Zomato, Talabat, Careem, Deliveroo.
7. List payment gateway credentials — Razorpay, Stripe, PayTabs, Mada.
8. Download last 3 months of GST/VAT reports as PDF and Excel.
9. Confirm printer compatibility — Star, Epson, Bixolon.
10. Book the cut-over window — mid-week, 1am-6am, tell your team.

How to Export Data from Popular POS Systems

Honest export notes for the five most-switched systems.

Petpooja Export

Menu items, customer database and sales reports export cleanly from admin > Reports and Master. Harder: modifier trees and loyalty ledgers need a support-ticket database extract (3-5 working days). File the ticket in writing before starting the migration timer. Petpooja charges a small extract fee for accounts over 50,000 orders.

Foodics Export

Manager dashboard > Reports lets you export items, categories, modifiers, customers and full transaction history as Excel/CSV. Harder: Foodics stores taxes inclusive on some SKUs and exclusive on others, so the tax column needs manual reconciliation. Loyalty and gift card balances export as two separate files — merge before import.

Toast Export

Toast Web > Reports > Report Library gives you menu, guest book, orders and sales summaries. Harder: Toast's guest data is spread across three modules (Loyalty, Gift Cards, Payroll), and the loyalty API sometimes returns points-plus-cash-value in one field. Ask support for a schema map — they'll send it if you insist.

Square Export

Dashboard > Customers > Import/Export and Items > Actions > Export both give clean CSV. Harder: Square splits fees, tips and refunds across separate line items in the same order — script a merge before importing into a POS that expects one row per order. Loyalty balances export separately under Loyalty > Customers.

Lightspeed Export

Backoffice > Reports and Customers. Lightspeed Restaurant K-series and O-series use inconsistent column headers — confirm which version you're on before writing a mapping. Loyalty points expire based on transaction date and the expiry logic doesn't export cleanly — you'll calculate it in Excel before import.

The 5-Step Migration Process

End-to-end elapsed time for a single outlet: 48-72 hours.

Step 1 — Export data from your current POS

Export every table from the pre-migration checklist. Save with date stamps — menu-export-2026-07-05.csv, not menu.csv. If your POS is on-premise, take a full database backup to two locations. Time: 2-4 hours.

Step 2 — Clean and normalise the data

Open CSVs in Excel or Google Sheets. Deduplicate guests by phone (a pivot table of counts catches the worst offenders). Standardise tax codes. Standardise item names — "Chicken Biriyani", "Chicken Biryani" and "Chkn Biriyani" merge into one row. Drop test orders. Time: 3-6 hours.

Step 3 — Import into the new POS

Online eMenu's importer handles Petpooja, Foodics, Toast and Square exports natively — upload CSV, auto-map columns. For less-common source systems you'll map manually the first time. Always run a test import first (10 items, 20 guests, 5 orders) before the full dataset. Time: 2-4 hours.

Step 4 — Run parallel operation for 2-3 days

Keep both POS live for 48-72 hours. Take orders on the new system while the old one stays as backup. Reconcile end-of-day totals nightly — within 1% is clean. Train staff during this window (most POS take 4-6 hours of hands-on before waiters stop asking questions). Time: 48-72 hours elapsed.

Step 5 — Cut over completely, cancel the old contract

After two consecutive clean-reconciliation days, decommission the old POS. Cancel in writing (email, not phone). Request final GST/VAT reports and aggregator payout ledgers. Archive exported CSVs on Drive, Dropbox or S3 for 7+ years — most tax authorities require it. Time: 1-2 hours plus paperwork.

What NOT to Do — Day-of-Migration Mistakes That Break Things

Don't cut over on a Friday or Saturday night. Non-negotiable. If it breaks at 8pm Saturday, you lose the weekend and it makes the local paper. Mid-week overnight, always.

Don't cancel the old POS before the parallel run. Vendors pressure you to cancel early. Ignore them — the old POS is your rollback plan for 3-5 days. Last month's fee is cheap insurance.

Don't skip staff training. "The new POS looks easier so we'll show them on the fly" ends with a waiter locked out during the dinner rush. 90-minute session per shift before cut-over.

Don't import test data into production. Every POS has a sandbox — use it. Full test import there first, then repeat on production.

Don't forget the aggregator sync window. Swiggy and Zomato menu re-syncs take 24-48 hours in India. Book cut-over so re-sync finishes by lunchtime the next day.

Don't leave loyalty guests in the dark. One WhatsApp broadcast the day before: "Points migrating. Balances confirmed. Brief delay possible." Nobody complains about communication — they complain about silence.

Post-Migration Validation Checklist — 48 Hours After Go-Live

Run through this list in the first 48 hours after cut-over.

• Ring up one order per menu category. Confirm prices and modifiers.
• Pull guest database. Confirm count within 1% of old system.
• Spot-check 10 guests. Confirm phone, email, loyalty balance.
• Print one receipt per printer. Confirm layout, GSTIN/TRN, footer.
• Print one KOT per kitchen station. Confirm routing.
• Place one test order per aggregator (Swiggy, Zomato, Talabat, Careem, Deliveroo).
• Refund one test order end-to-end. Confirm gateway processes it.
• Pull day-end report. Confirm tax split matches.
• Send one WhatsApp/QR menu order. Confirm guest attribution.
• Run a loyalty redemption. Confirm points deduct correctly.

All 10 pass, you're done. Any fail, roll back to the old POS while you investigate — you still have it running for a reason.

Common Gotchas

Data mapping mismatch. "customer_name" vs "guest_name". "spice_level" modifier vs "custom_note". Every migration has 20-40 tiny mismatches — budget 2-3 hours for a mapping spreadsheet.

Tax code differences. India GST (5/12/18%), UAE VAT (5%), Saudi VAT (15%), UK VAT (20/5/0%). Old POS inclusive vs new POS exclusive = arithmetic per SKU. Confirm before import.

Aggregator re-linking pain. Even after re-linking Swiggy Merchant, items sync with old images or wrong prices. Inspect the storefront day one and file tickets for drift. Same for Zomato and Talabat.

WhatsApp opt-in re-establishment. Third-party integrations don't migrate opt-ins cleanly. Meta's 2026 rules require documented consent per template category — if you can't prove opt-in, re-collect. Plan a "tap here to keep getting offers" broadcast in week 1.

Printer driver differences. Star TSP-143 works everywhere. Older Bixolon and Epson need vendor drivers. Confirm before cut-over — not at 6am when the printer refuses to fire.

How Online eMenu Handles Migration

Online eMenu runs a 48-hour concierge migration for every new customer, free on annual plans. Monthly subscribers get the same service for a one-time setup fee.

Import from all major POS. We've written import scripts for Petpooja, Foodics, Toast, Square, Lightspeed, POSist/Restroworks, GOFRUGAL and Posify. On one of these, we can start the day you sign. For rarer systems we build the mapping in 24-48 hours and re-use it across your outlets.

Data cleanup, parallel validation, aggregator re-linking. Our engineer runs deduplication, tax normalisation and name standardisation, shares a before/after report, then runs shadow mode for 48-72 hours where every order writes to both systems and we reconcile nightly. We coordinate Swiggy/Zomato/Talabat/Careem re-linking directly — most restaurants see zero aggregator downtime.

WhatsApp Business setup. Because WhatsApp ordering is native, we run Meta approval, template design and opt-in collection alongside the migration. You go live with WhatsApp on day one, not three weeks later.

Pricing. ₹199/month all-in for India, $9/month international, no lock-in, no transaction fees. Migration included on annual plans. See the pricing page for country tiers.