tawlat

Switching · From local ERP or custom software

Move from your local system to tawlat, onto a product that's actively maintained.

Whether you're on a custom Windows POS built years ago by a local developer, a locally-licensed accounting tool with a thin POS bolt-on, or an Excel-based system that grew with the business, the move to tawlat brings your data across, replaces single-developer dependency with a continuously-updated product, and gives you cloud, mobile, and multi-channel — without rewriting your operation from scratch.

  • Live within 2 to 7 days
  • Free hands-on migration
  • XLSX, CSV, SQL, PDFs, even photos
Your local system
tawlattawlat
A quiet, one-shift switch, hands-on, included.

Why teams move from a local system to tawlat

Six reasons we hear most often. The point isn't that your current system is bad — it served you. The point is that the way restaurants run in 2026 has moved on, and a frozen one-off can't keep up.

  • An active product, not a frozen one-off

    Your local system was probably built once and left to age. tawlat ships new addons, security patches, payment integrations, and reporting features continuously. No single-developer dependency, no "is anyone still maintaining this?" question.

  • Cloud, mobile, multi-device

    tawlat runs in the cloud and works on Android tablets, phones, and any modern laptop. No "the server PC is down" day, no "we have to be on that one machine". Walk-in tablet for the waiter, kitchen display in the back, cashier at the till — all on the same live data.

  • Modern, mobile-first UI

    Designed for thumb-speed on a working shift. Less hunt-and-peck at the cashier, less staff training, less frustration on a busy Friday night.

  • Direct local support

    Phone and WhatsApp in your timezone, in your language. Not "let me check with the developer who built this and see if he's available". A team that owns the product end to end.

  • Multi-channel by default

    Dine-in, takeaway, delivery, QR menu, online ordering — all on one system, sharing one live menu and one customer book. No bolt-on plugins, no separate tools to keep in sync at end of day.

  • Hands-on migration from anything

    We accept XLSX, CSV, SQL backups, PDFs, even photos of paper menus. Our team handles the import — you don't have to wrestle with the export format alone.

Your local system vs. tawlat, side by side

Ten rows that matter on a switching decision. "Local system" here covers custom Windows POS, locally-licensed accounting tools with a POS bolt-on, Excel-based setups, and Sage / QuickBooks Desktop + ad-hoc POS — the category, not any single product.

  • Active development
    Your local system

    Often frozen; depends on the original developer or a small shop

    tawlat

    Continuously updated with a public roadmap

  • Cloud + mobile
    Your local system

    Usually Windows desktop bound; needs a specific PC

    tawlat

    Cloud-based, runs on tablet, phone, laptop, anywhere

  • User interface
    Your local system

    Often dated, slow, designed years ago

    tawlat

    Modern, mobile-first, designed for speed on every workstation

  • Multi-channel ordering
    Your local system

    Cashier-focused; online and delivery are usually bolt-ons

    tawlat

    Dine-in, takeaway, delivery, QR menu, all on one live system

  • Support model
    Your local system

    Depends on the original developer's availability

    tawlat

    Local team, direct contact (phone + WhatsApp)

  • Integrations
    Your local system

    Limited; payment and delivery often handled manually

    tawlat

    Major JO / GCC payment processors and delivery platforms supported

  • Backups & disaster recovery
    Your local system

    Manual, often the owner's responsibility

    tawlat

    Encrypted automated daily backups, restored in one tap (Backups addon)

  • Migration in
    Your local system

    Whatever the vendor / developer hands you, if anything

    tawlat

    Hands-on migration from XLSX, CSV, SQL backups, PDFs, or photos

  • Dedicated restaurant addons
    Your local system

    Frozen feature set, custom requests billed by the hour

    tawlat

    15+ first-party addons (Hostess Suite, House Accounts, Call Bridge, Push to Sell, Comeback Vouchers, Delivery Ops, Email Reports)

  • Local invoicing (JO / GCC)
    Your local system

    Often custom-coded and out of date as tax rules evolve

    tawlat

    Built into the core, updated as JO and GCC rules change

What comes across from your local system

tawlat is built to be the new home for the data you already have, in whatever format your current system gives you. This is what we typically import in a local-system migration.

  • Menu, modifiers, categories

    From XLSX, CSV, or even a PDF / photo of your printed menu. Items, categories, modifiers, and sale prices imported into the structure your team already knows.

  • Recipes & ingredients

    If your system holds recipes (in any form — spreadsheet, table, or document), we map them into tawlat's recipe map with ingredient links and per-portion quantities.

  • Customer book

    Phone numbers, names, addresses, last-visit context, and any wallet balances — indexed for instant lookup at the till and on the phone.

  • Supplier book & open POs

    Suppliers, contact details, ingredient links, open purchase orders, and payment terms move over together.

  • Tax & accounting settings

    VAT rate, service charge, payment-method mix, and report templates configured to match your accountant's existing process.

  • Staff, roles, permissions

    Your existing roles map to tawlat's permission groups. Manager-only actions stay manager-only on day one.

How the move from a local system works

Three phases, roughly one week, and one quiet shift for the cutover. Your local system keeps running the whole time.

  1. 01

    Get your data out, in any shape

    Day one. You share whatever your system can give us: an Excel export, a CSV dump, a SQL backup, screenshots, a PDF of your menu, even a database file from the running app. We map every field to tawlat's schema, flag any custom features that don't translate cleanly, and confirm the timeline with you. The audit also covers what to do if the original developer is no longer reachable.

  2. 02

    Parallel import

    Days two to three. Menu, customers, history, and supplier data load into tawlat in the background while your local system keeps running every shift. Your team trains on real data, on the workstations they'll actually use.

  3. 03

    Cutover in one shift

    Pick the quietest service of the week. Before cutover, you take a final backup of your local data as a safety net (we'll guide you through where to grab the right files). The team switches to tawlat, the local system retires, and you're live, end to end.

Frequently asked about leaving a local system

If something's not here, the easiest path is a 5-minute call. We've moved restaurants off custom Windows POS, off locally-licensed accounting tools, and off Excel-based setups.

  • What if my local system can't easily export data?

    That's typical. We accept whatever you have — SQL database files, screenshots, PDFs, photos of printed reports, even hand-written records. AI-assisted import handles the unstructured stuff (a photo of your menu becomes a structured menu), and our team does the manual mapping for anything that needs human judgement.

  • What about my custom features — the things only my system does?

    Day-one audit covers each custom feature explicitly. We tell you straight whether tawlat handles the same behavior out of the box, via an addon, or not at all. If something isn't supported and matters to your operation, we'll flag it before cutover — no surprises after the move.

  • What if my original developer is no longer available?

    Common situation. We've worked with restaurants where the original developer retired, moved on, or simply stopped picking up. As long as the system is running on a PC you control, we can extract the data — from the database file, from the running app's exports, or by writing a one-off script against the database. The day-one audit confirms what's reachable.

  • Can I run tawlat alongside my local system during the move?

    Yes, that's the default. Parallel running is the whole point of the import phase. You only cut over when your team has trained on real data and you're confident.

  • What about my hardware?

    Most off-the-shelf receipt printers, cash drawers, scanners, and customer-facing displays work with tawlat directly. Your Windows PC won't be the operating workstation anymore (tawlat runs on tablets and phones), but it stays in your control for archives or for running the old system read-only after cutover.

  • Do I sign a long-term contract?

    No. tawlat bills monthly with cancel-anytime, or yearly with a discount. No mandatory multi-year plan, no early-termination fee.

  • What about my Windows licenses and old install?

    Up to you. Once you migrate, the Windows PC becomes a normal computer again — no license-tied obligation to keep paying for the local POS / ERP. Many owners keep the old install running read-only on the same PC for a month or two as a safety net.

Book a switching call from your local system.

Show us what you have today in a 15-minute call — even if it's a screenshot, a database backup, a folder of Excel files, or a photo of your printed menu. We'll walk through what carries over, the timeline, and what your team gains by moving onto an active product with direct support.

Book a switching callSee pricing