0%
SUN-THU: 9:00AM - 06:00PM (AST)
Qatar ERP
Contact Us
Contact Us
ENG
Skip to content
Migration

Migrating from Tally to an ERP in Qatar: what to expect

Tally runs the books of thousands of Qatari trading and services companies. The move to an ERP usually starts with e-invoicing, multi-branch stock or a second company, and it goes well or badly depending on how the data is handled.

Talk to a consultant +966 54 176 1946

Why companies leave Tally, and when they should not

Tally is a capable ledger, and companies that only need a ledger should keep it. The move happens when the business needs what a ledger cannot do: e-invoicing integration without workarounds, stock across warehouses with batches and landed cost, CRM connected to invoicing, payroll with GRSIA and WPS, approvals, multi-company consolidation, or Arabic documents and interface for a team that does not work in English. At that point Tally is surrounded by spreadsheets, and the spreadsheets are the system.

The destinations we migrate to are Zoho Books for companies that want a Qatar-edition cloud ledger connected to CRM and Inventory, Odoo for companies that need operations inside the ERP, and ERPNext for companies that want an open-source ERP without per-user licences. The migration work is similar on all three.

What migrates

DataApproach
Chart of accountsMapped to the new structure, usually simplified; groups become account types
Customers and suppliersExported, deduplicated across Arabic and English names, VAT numbers validated
ItemsExported with units, tax codes and opening stock by warehouse with cost
Opening balancesTrial balance at cut-over, with receivables and payables by open document
Open documentsUnpaid invoices and bills, open orders, advances
HistorySummarised by month, or migrated in detail where reporting needs it

How the migration runs

Export from Tally to spreadsheets or XML, profile the data for duplicates and gaps, agree cleansing rules with finance, map fields to the target, load into a staging company, reconcile the trial balance, receivables, payables and stock to Tally, fix and reload until they match, then load for cut-over with the same scripts. The data migration page describes the discipline in detail.

Qatar specifics

Tally installations in Qatar often hold customer names in English only, VAT numbers in remarks fields, and tax codes set inconsistently. The migration is the moment to fix them: bilingual names, VAT numbers in their own validated field, and tax codes that make the return come out of the ledger. E-invoicing is configured on the new system before the first invoice, not after.

Timing and cost

Cut over at a month-end or the financial year start, run one close in parallel, and keep Tally read-only afterwards. A Tally-to-Zoho-Books migration for a single company typically takes three to six weeks; into Odoo or ERPNext with stock and operations, eight to twelve. Migration is priced as a fixed workstream within implementation.

Explore related pages

Where to go next, depending on what you are trying to decide.

ERP data migration

The migration workstream.

Zoho Books

The cloud ledger destination.

Zoho migration

Into Zoho.

Odoo migration & upgrade

Into Odoo.

ERPNext migration

Into ERPNext.

ERP vs accounting software

When a ledger stops being enough.

Questions before you book

Yes, summarised by month or migrated in detail; Tally is kept read-only for reference either way.

Yes. Every load is reconciled to Tally before cut-over and signed off.

Usually it is simplified; the mapping is agreed with finance.

Zoho Books for a connected cloud ledger, Odoo for operations, ERPNext to avoid licences. We recommend after seeing the business.

Three to six weeks to Zoho Books; eight to twelve to Odoo or ERPNext.

Want this done on your system?

Tell us what you run today and we will say what it takes.

+966 54 176 1946 WhatsApp

Book a free consultation

A 30-minute call, no obligation. We will tell you if we are not the right fit.

We use your details only to answer this enquiry. No lists, no resale.