ERP migration
Field-level mapping, validation, and rollback between Tally Prime and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Tally Prime
Source
Dolibarr ERP
Destination
Compatibility
10 of 13
objects map 1:1 between Tally Prime and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Tally Prime to Dolibarr is a structural migration from a Windows desktop accounting tool built for Indian GST compliance to an open-source modular ERP/CRM that runs on PHP and MySQL. Tally Prime's proprietary flat-file database cannot be queried via SQL, so all extraction relies on XML template exports through Tally's built-in export function. We flatten Tally's nested Groups and Ledgers into Dolibarr's plan comptable or custom chart of accounts, reclassify Vouchers into Dolibarr's invoice and payment document types, and map Godowns to Dolibarr's warehouse module. GSTIN validation, exchange rates, and opening balances transfer as structured fields. We do not migrate TDL customisations, workflows, or GST-related configurations; these require manual rebuild in Dolibarr using its module activation and PHP-based extension model.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Tally Prime object lands in Dolibarr ERP, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Tally Prime
Ledger
Dolibarr ERP
Account (plan comptable)
1:1Tally Ledgers are the atomic account records in the chart of accounts. We export Ledgers via Tally XML template with opening balance, closing balance, mailing address, and GSTIN fields, then create corresponding Dolibarr third-party or accounting account records depending on the Ledger type (sundry debtor maps to customer third-party; sundry creditor maps to supplier third-party; others map to accounting accounts in the plan comptable). Primary group assignments and the affects-reporting flag are preserved as account category metadata in Dolibarr.
Tally Prime
Group
Dolibarr ERP
Account Category (Rubrique)
1:1Tally Groups define the hierarchy above Ledgers and carry a primary/affects-reporting flag. We map Groups to Dolibarr account categories in the accounting module, preserving the reporting-affects relationship so that the trial balance and financial statements aggregate correctly in Dolibarr. Groups that represent a collection of sub-ledgers (like Cost of Goods Sold or Direct Expenses) map to the equivalent heading in the target plan comptable.
Tally Prime
Parties (Sundry Debtors and Sundry Creditors)
Dolibarr ERP
Third Party (Customer or Supplier)
1:1Tally Parties with GSTIN, PAN, credit limit, and shipping/billing addresses map to Dolibarr Third Parties. Sundry Debtors become Dolibarr customers; Sundry Creditors become Dolibarr suppliers. GSTIN validation is performed against the GST portal API during pre-migration audit; any invalid GSTINs are surfaced for customer correction before import. Credit limit, payment terms, and bank details transfer to Dolibarr Third Party extra fields.
Tally Prime
Currency
Dolibarr ERP
Currency
1:1Tally's currency definitions and exchange rates map to Dolibarr's multi-currency setup. We export the active currencies and their most recent exchange rates and load them into Dolibarr's currency configuration. For businesses operating primarily in INR, the base currency is straightforward. Foreign-currency transactions from Tally (with realised and unrealised gain/loss entries) transfer as separate lines in Dolibarr's accounting entries.
Tally Prime
Voucher (Sales)
Dolibarr ERP
Facture (Invoice)
1:1Tally Sales Vouchers map to Dolibarr Customer Invoices (Facture client). Voucher number, voucher date, party reference, line items (stock item + quantity + rate), and tax breakdown (CGST + SGST or IGST) transfer as structured fields. Tally's GSTIN-linked party reference is resolved to the Dolibarr Third Party created during the Party import phase. Voucher number retention is agreed upon with the customer during scoping to avoid duplicate invoice numbering in Dolibarr.
Tally Prime
Voucher (Purchase)
Dolibarr ERP
Facture fournisseur (Supplier Invoice)
1:1Tally Purchase Vouchers map to Dolibarr Supplier Invoices (Facture fournisseur). The same field mapping applies as for sales vouchers, with the party reference resolved to the Dolibarr supplier Third Party. TDS deduction entries in Tally map to Dolibarr accounting entries linked to the invoice. Purchase invoice PDF attachments from Tally are not carried forward as native Dolibarr attachments unless the customer exports them separately.
Tally Prime
Voucher (Payment, Receipt, Contra, Journal)
Dolibarr ERP
Banque/Recette/Caisse/Journal
1:1Tally Payment vouchers map to Dolibarr bank and cash payment entries; Receipt vouchers map to bank and cash receipt entries; Contra vouchers map to internal transfer entries; Journal vouchers map to Dolibarr manual journal entries (Écritures comptables). We map Tally's debit/credit account references to Dolibarr debit/credit lines within each document, preserving the original voucher narration as the document note. Bank ledger references in Tally map to Dolibarr bank account records created during the Ledger import phase.
Tally Prime
Voucher Type
Dolibarr ERP
Document Type (Type de documents)
lossyTally's custom voucher type definitions (naming series, numbering prefixes, applicability to specific ledgers) map to Dolibarr's document type configuration. Each voucher type becomes a corresponding document model in Dolibarr's accounting module. Numbering series continuity is preserved where possible by setting Dolibarr's document sequence to start after the last Tally voucher number.
Tally Prime
Stock Item
Dolibarr ERP
Product (with stock tracking)
1:1Tally Stock Items with UOM, opening quantity, rate, and HSN/SAC code map to Dolibarr Products with the stock module enabled. We create Dolibarr products in variant mode if Tally has multiple units of measure per item. HSN/SAC code transfers as a product extra field. Opening quantity and rate transfer to Dolibarr's stock warehouse initial stock entry. Stock item pricing from Tally price lists maps to Dolibarr customer-specific price lists.
Tally Prime
Godown
Dolibarr ERP
Warehouse (Entrepôt)
1:manyTally Godowns represent physical storage locations. We map each Godown to a Dolibarr Warehouse (Entrepôt). When Tally stores the same stock item at multiple godowns with different quantities, we create separate Dolibarr warehouse stock entries per location. Dolibarr's warehouse module must be activated in the Dolibarr Modules section before stock migration; this is a configuration step the customer performs with our guidance. Godown-level stock reports from Tally drive the per-warehouse quantity entry in Dolibarr.
Tally Prime
Cost Centre
Dolibarr ERP
Project (Projet) or Internal Cost Centre
lossyTally Cost Centres function like departments or cost pools for expense allocation. We map them to Dolibarr Projects with cost-tracking enabled, or to the internal cost centre feature if the Dolibarr accounting module's cost centre extension is activated. Tally does not enforce cost centre assignment on vouchers, so we flag any voucher with a cost centre reference and map it explicitly. Projects in Dolibarr provide budget-versus-actual tracking that has no direct Tally equivalent.
Tally Prime
Budget
Dolibarr ERP
Budget (forecast records)
1:1Tally Budget masters associate Groups or Cost Centres with period-based budget values. We map these to Dolibarr budget or forecast records where the Dolibarr accounting module's budget extension is active. Note that Dolibarr's native budget module has different data-entry mechanics from Tally's budget master; we provide a written budget mapping table during handoff so the customer's accountant can re-enter budget values in Dolibarr's preferred format.
Tally Prime
Price List
Dolibarr ERP
Price List (Tarif client spécifique)
1:1Tally price lists associate stock items with party-type-based pricing (retail, wholesale, special). We map these to Dolibarr customer-specific price lists (Tarifs) attached to Third Parties. Where Tally price lists use quantity-breaks, we create Dolibarr price list lines with min/max quantity thresholds. Price-list conditional logic from Tally (such as date-effective pricing) is documented in the mapping notes for the customer's admin to configure manually in Dolibarr.
| Tally Prime | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Ledger | Account (plan comptable)1:1 | Fully supported | |
| Group | Account Category (Rubrique)1:1 | Fully supported | |
| Parties (Sundry Debtors and Sundry Creditors) | Third Party (Customer or Supplier)1:1 | Fully supported | |
| Currency | Currency1:1 | Fully supported | |
| Voucher (Sales) | Facture (Invoice)1:1 | Fully supported | |
| Voucher (Purchase) | Facture fournisseur (Supplier Invoice)1:1 | Fully supported | |
| Voucher (Payment, Receipt, Contra, Journal) | Banque/Recette/Caisse/Journal1:1 | Fully supported | |
| Voucher Type | Document Type (Type de documents)lossy | Fully supported | |
| Stock Item | Product (with stock tracking)1:1 | Fully supported | |
| Godown | Warehouse (Entrepôt)1:many | Fully supported | |
| Cost Centre | Project (Projet) or Internal Cost Centrelossy | Fully supported | |
| Budget | Budget (forecast records)1:1 | Fully supported | |
| Price List | Price List (Tarif client spécifique)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Tally Prime gotchas
Proprietary database requires XML-template export for all migrations
Stock quantities can reset to zero after Tally version upgrades
TSS subscription required for official data import/export features
Voucher renumbering risk when importing into Tally Prime
GSTIN-linked parties require pre-validation before import
Dolibarr ERP gotchas
Foreign key constraint errors on cross-distribution database restore
SQL injection vulnerabilities in version 9.0.1
Custom fields stored as JSON in extraoptions require field-by-field deserialization
Decimal precision and rounding configuration affects price fields
No native iOS/Android app forces reliance on browser
Pair-specific challenges
Migration approach
Discovery and Tally data audit
We audit the source Tally Prime company across ledger count, voucher count by type, stock item count, godown list, active cost centres, budget masters, price lists, and any TDL custom fields. We guide the customer through the XML template export and run Tally's built-in exceptions report to surface voucher-level errors before any migration work begins. We also confirm TSS licence status, restore default XML templates if modified, and capture the trial balance, stock summary, and GST returns as source-of-truth reference reports.
Dolibarr environment provisioning and module activation
We guide the customer through Dolibarr installation (self-hosted or partner-hosted) and the activation of required modules: Comptabilité (accounting), Facturation (invoicing), Produits (products), Stock (inventory), Banques (bank accounts), and Projets (projects or cost centres) if applicable. We configure the chart of accounts in Dolibarr's accounting module, selecting the appropriate plan comptable (India-compatible or generic) and setting the base currency to INR. This step also includes configuring Dolibarr's Third Party categories for customers and suppliers before any party data is imported.
Chart of accounts and party mapping design
We design the object mapping between Tally and Dolibarr: Groups map to account categories, Ledgers map to accounts or third parties, Parties map to Dolibarr third parties with GSTIN as a required extra field, and Godowns map to Dolibarr warehouses. We produce a written mapping document covering every distinct Tally voucher type and its Dolibarr document type equivalent, along with notes on which voucher types require special handling (TDS vouchers, reversed entries, memo vouchers). The mapping document is reviewed and signed off by the customer's accountant before migration begins.
Sandbox migration and reconciliation
We run a full migration into a test environment using production data volume. The customer's finance team reconciles the trial balance (total debits equals total credits), GST returns (GSTR-1 and GSTR-3B summary totals), and stock summary (quantities by warehouse). We provide row-count reports per object type and a general ledger comparison against Tally's Balance Sheet and P&L. Any mapping corrections, missing accounts, or voucher type misclassifications are resolved in this phase before the production migration run.
Production migration in dependency order
We run production migration in dependency order: currencies and exchange rates first, then chart of accounts (Groups then Ledgers), then Third Parties (customers and suppliers with GSTIN), then Products and warehouses, then open-period vouchers (opening balance journals, sales, purchases, payments, receipts, journals), then closing period transactions. Each phase emits a row-count reconciliation report. Godown-level stock quantities are loaded after the product list is established, using the per-godown stock data extracted from Tally's stock report.
Cutover, validation, and TDL rebuild handoff
We freeze Tally Prime as the system of record during cutover, run a final delta migration of any transactions entered during the migration window, and validate the Dolibarr trial balance against the final Tally reference report. We deliver a written inventory of all Tally TDL custom fields and their Dolibarr ExtraField equivalents for the customer's admin to rebuild, plus a written list of all custom voucher types requiring document type mapping review in Dolibarr. We do not rebuild workflows or GST compliance configurations; these are separate Dolibarr configuration engagements.
Platform deep dives
Tally Prime
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between Tally Prime and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Tally Prime and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between Tally Prime and Dolibarr ERP.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Tally Prime: Not publicly documented.
Data volume sensitivity
Tally Prime doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Tally Prime to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Tally Prime to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Tally Prime
Other ways to arrive at Dolibarr ERP
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.