Skip to content

Migrating to a new POS: a four-week plan that does not lose data

Most migrations go wrong in the catalogue, not the software. Here is a week-by-week plan that front-loads the data work and leaves the busiest branch until last.

By Wameed field teamOnboarding and support

6 min read

In short: Changing POS is a data project with a software installation at the end.Week 1: export everything (products, customers, suppliers, two years of sales, the invoice archive) and verify it opens; record the last invoice number and hash per device.Week 2: clean the catalogue (duplicates, units, VAT per product, cost prices, dead stock, variants), the highest-return work.Week 3: import, onboard terminals with ZATCA, set users and permissions, connect integrations and pilot on one terminal.Week 4: cut over at a clean boundary, count stock, test a B2B clearance, and move the quietest branch first and the busiest last. Never run both systems on one terminal.

Changing point-of-sale systems is not a software installation; it is a data project with a software installation at the end. Here is a plan that reflects that.

Week 1: export and assess

Export everything from the old system before you cancel anything:

  • Products with barcodes, cost prices, sell prices and VAT treatment
  • Categories and modifiers
  • Customers with contact details and any VAT numbers
  • Suppliers and open purchase orders
  • Sales history for at least the last two years
  • The invoice archive, in XML where available

Verify the exports open. A CSV that will not parse is not an export.

Record the last invoice number and hash per device. Seechanging POS without breaking ZATCA.

Get the old vendor's retention terms in writing.

Week 2: clean the catalogue

This is the real work, and it is worth doing properly because you are about to live with the result for years.

  • Duplicates. Two rows for the same product, usually from a barcode typed twice.
  • Units. Decide, per product, whether you buy and sell in the same unit, and record the conversion where you do not.
  • VAT treatment. Per product, confirmed with your accountant — seeVAT basics.
  • Cost prices. Missing cost prices mean no gross margin reporting, forever, until someone backfills them. Do it now.
  • Dead stock. Products not sold in twelve months: archive rather than import.
  • Variants. Fifty separate SKUs that are really one product in five sizes and two colours should become one product with children.

A shop with 3,000 products should expect two to three days on this. It is the highest-return work in the entire migration.

Week 3: configure and pilot

  • Import the cleaned catalogue into the new system. Review the import report — what did not match, and why?
  • Onboard terminals with ZATCA. Every device. See theonboarding guide.
  • Set up users and permissions. Who can discount, refund, void, change prices, see reports.
  • Configure printers and the receipt template. Print one and scan the QR.
  • Connect integrations — delivery platforms one at a time, the accounting sync, payment provider, and your online store and WhatsApp number if you use them.
  • Pilot on one terminal at one branch, for real sales, for at least three days.

Compare the pilot terminal's daily report against the old system's for the same period. Differences are findings, not noise.

Week 4: cut over

Choose the boundary. End of a trading day, ideally end of a VAT period, ideally a quiet weekday.

On the day:

  1. Old system stops issuing — completely, on that device
  2. Count stock, physically, and enter the counted quantities as opening balances
  3. Start the new system
  4. Issue a test invoice and verify: QR scans, totals correct, accepted by ZATCA
  5. Verify one B2B invoice clears
  6. Have a manager on the floor for the whole first shift

Order of branches: quietest first, busiest last. If something is wrong, you want to find it where it costs least.

The two weeks after

  • Watch the ZATCA acceptance dashboard daily. Early rejections are configuration.
  • Reconcile cash daily, and take variances seriously in week one — they are usually process, not theft.
  • Check gross margin on your top 20 products against what you expected. A wrong cost price shows up here.
  • Keep the old system's archive somewhere you control.
  • Collect staff complaints in one place and fix the top three. Small friction compounds.

The five things that go wrong

  1. Stock not counted at cutover. Then nobody knows whether a discrepancy is data or loss.
  2. Cost prices not imported. Margin reporting is dead until someone backfills.
  3. Both systems live on one terminal. Breaks the ZATCA hash chain.
  4. Busiest branch first. Maximum pain, minimum learning.
  5. Old subscription cancelled before export verified. Sometimes unrecoverable.

How long it really takes

  • Single shop, clean catalogue: one week
  • Single shop, messy catalogue: three weeks, most of it week 2
  • Three to five branches: four to six weeks
  • Ten or more branches: plan a branch a week after the first two

Rushing week 2 is the most common and most expensive mistake. Everything else is recoverable.

Related:changing POS without breaking ZATCA,Foodics alternatives,Rewaa alternatives andopening a second branch.

Frequently asked questions

How long does it take to migrate to a new POS?

A single shop with a clean catalogue: about a week. With a messy catalogue: three weeks, mostly cleaning. Three to five branches: four to six weeks.

What should I export before leaving my old POS?

Products with barcodes, costs and VAT treatment, categories and modifiers, customers with VAT numbers, suppliers and open purchase orders, sales history for two years, and the invoice archive in XML if available.

Why count stock on cutover day?

Because even a perfect catalogue import does not mean your quantities are right. Without a count you cannot tell whether a later discrepancy is data or loss.

Which branch should I switch first?

The quietest; the busiest branch goes last so any problem is found where it costs least.

What goes wrong most often?

Stock not counted at cutover, cost prices not imported, both systems live on one terminal, the busiest branch first, and cancelling the old subscription before verifying the export.

  • #الانتقال بين أنظمة الكاشير
  • #تغيير نظام الكاشير
  • #ترحيل البيانات
  • #نظام كاشير جديد
  • #migrate POS
  • #switch POS system
  • #POS migration plan
  • #catalogue import

Share this article

Ask about your own shop

Thirty minutes on your products, your tax setup and your hardware — not a slide deck.

Keep reading