Ürün ayrıntıları İngilizce olarak görüntülenir. Çeviriler yakında gelecek.
Kısa bilgiler
- Fiyat
- $499.00 USD
- ERPNext versiyonları
- —
- Kurulum süresi
- 30 dk.
- Lisans
- Bir kerelik kalıcı
- Diller
- 11 language
Tek Seferlik Satın Alma
Tally to ERPNext Migrator
A build-to-order Frappe app that imports Tally masters and vouchers into ERPNext with accurate ledger, group and GST mapping, opening balances, and reconciliation reports. ECOSIRE scopes, builds, installs, and supports it for your specific Tally company file.
$499.00USD
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
Temel Özellikler
Tally XML import parser that reads native `Gateway of Tally > Export` output (masters and vouchers) plus a structured Excel/CSV fallback for hand-cleaned data
Staging DocType that stores every raw Tally record with its original GUID, so imports are auditable and re-runnable without data loss
Configurable ledger-to-account mapping that places Tally groups under the correct ERPNext `Account` roots (Asset, Liability, Income, Expense, Equity)
Group hierarchy reconstruction — parent/child Tally groups become nested `Account` and `Item Group` trees with `is_group` set correctly
Voucher-type mapping from Tally (Receipt, Payment, Contra, Journal, Sales, Purchase) to the right ERPNext documents (`Payment Entry`, `Journal Entry`, `Sales Invoice`, `Purchase Invoice`)
Opening-balance import that posts period-opening `Journal Entry` records and sets item opening stock via `Stock Entry` / opening `Stock Reconciliation`
GST field mapping — GSTIN, HSN/SAC, place of supply and tax ledgers mapped to ERPNext GST accounts and `Sales/Purchase Taxes and Charges` templates
Master de-duplication and matching so repeated Tally party names collapse to single `Customer` / `Supplier` records instead of duplicates
Batched, queue-driven import via Frappe background jobs and scheduler events so large company files load without worker timeouts
Idempotent import keys (Tally GUID mapped to ERPNext docname) so a re-run updates rather than duplicating already-migrated documents
Whitelisted API methods and doc-event `hooks.py` validation that block malformed vouchers before they hit the ledger
Reconciliation report set: Tally vs ERPNext Trial Balance, opening-balance parity, voucher counts by type, and an exception log for unmapped ledgers
Role-scoped migration console (custom role profile) so only finance leads can run or approve a migration batch
Dry-run mode that validates and previews the full mapping against staging before any document is committed to the live ledger
Bu Ürün Hakkında
Indian SMEs moving off Tally hit the same wall: years of ledgers, groups, stock items and vouchers live inside a Tally company file, and ERPNext's stock Data Import Tool expects clean, DocType-shaped CSVs it cannot produce. Manual re-keying of opening balances and historical vouchers is slow and error-prone, GST fields rarely line up one-to-one, and a naive import leaves your Chart of Accounts and Trial Balance out of sync from day one. ERPNext core gives you the destination DocTypes but nothing that understands Tally's XML structure, its group hierarchy, or the difference between a Tally "Receipt" and a "Payment" voucher.
Neden Tally to ERPNext Migrator
Tally XML import parser that reads native `Gateway of Tally > Export` output (masters and vouchers) plus a structured Excel/CSV fallback for hand-cleaned data
Staging DocType that stores every raw Tally record with its original GUID, so imports are auditable and re-runnable without data loss
Configurable ledger-to-account mapping that places Tally groups under the correct ERPNext `Account` roots (Asset, Liability, Income, Expense, Equity)
Group hierarchy reconstruction — parent/child Tally groups become nested `Account` and `Item Group` trees with `is_group` set correctly
Voucher-type mapping from Tally (Receipt, Payment, Contra, Journal, Sales, Purchase) to the right ERPNext documents (`Payment Entry`, `Journal Entry`, `Sales Invoice`, `Purchase Invoice`)
Opening-balance import that posts period-opening `Journal Entry` records and sets item opening stock via `Stock Entry` / opening `Stock Reconciliation`
ECOSIRE builds a proper Frappe app — with its own module, DocTypes and hooks.py — that ingests Tally exports (XML from Gateway of Tally > Export, or structured Excel) and maps them into ERPNext. A staging DocType captures each raw record so nothing is lost; server scripts and whitelisted methods then transform Tally masters into Account, Customer, Supplier, Item and Item Group records, and Tally vouchers into Journal Entry, Sales Invoice, Purchase Invoice, Payment Entry and Stock Entry documents. We build a configurable mapping layer so your Tally ledger groups land under the correct ERPNext account roots (Asset, Liability, Income, Expense, Equity), and your GST ledgers map to the right Sales Taxes and Charges / Purchase Taxes and Charges templates and HSN/GSTIN fields.
Technically, the migration runs through Frappe's job queue rather than a fragile one-shot script: batches are enqueued via scheduler events and background jobs so a large company file imports without timing out, with idempotent keys so a re-run does not duplicate documents. Doc-event hooks validate each record on insert, a client script drives the mapping-review screen inside ERPNext, and role-scoped permissions keep the migration console limited to your finance leads. Every run produces validation and reconciliation reports — Tally Trial Balance vs ERPNext Trial Balance, opening-balance parity, voucher counts by type, and an exceptions list — so you sign off on the numbers before go-live, not after.
Because this is build-to-order, we start from your actual Tally data. After a scoping call we take a sample company export, confirm the ledger-to-account mapping, GST treatment, and which voucher types and date range you need, then build and test against your data on a staging site. Typical delivery is 2-4 weeks from confirmed scope depending on data volume and the number of edge cases in your Tally file. You get the installable app source for your Frappe/ERPNext v15 or v16 site, a UAT pass on staging with a rollback plan, and a post-go-live support window — no instant download, because a migration is only worth doing if the ledgers reconcile.
Ne elde edeceksin
- Installable Frappe app source (your version) — the migrator app with its module, DocTypes, server/client scripts and `hooks.py`, licensed for your ERPNext site
- Installation and configuration on your Frappe/ERPNext v15 or v16 site, including the ledger-to-account and GST mapping tuned to your Chart of Accounts
- Technical documentation — DocType reference, mapping-configuration guide, whitelisted API methods, and re-run/rollback procedure
- User guide plus a live training session for your finance team on running imports, reviewing mappings, and reading the reconciliation reports
- UAT on a staging site against your real Tally export, with a signed reconciliation sign-off and a documented rollback plan before go-live
- Post-go-live support window for defect fixes and mapping adjustments on the delivered scope
- Git repository handover with full commit history so your team (or ECOSIRE) can maintain and extend the app
- Reconciliation report pack (Trial Balance parity, opening-balance and voucher-count checks) generated from your migration run
Bu kimin için
Finance Controller at a Tally-run SME
Owns the Chart of Accounts and the Trial Balance. Needs the opening balances and GST ledgers to reconcile to the paisa in ERPNext before signing off, and wants exception reports rather than blind trust in a script.
ERPNext Implementation Partner
Rolling out ERPNext to a client currently on Tally and needs a reliable, repeatable data-migration component instead of writing throwaway import scripts per engagement. Values the git handover and configurable mapping layer.
SME Business Owner switching ERPs
Wants to leave Tally for ERPNext without losing years of history or re-hiring an accountant to re-key data. Needs a fixed-scope, build-to-order engagement with a clear go-live date and a rollback safety net.
IT / Systems Admin managing the ERPNext site
Responsible for the Frappe bench and the staging/production sites. Needs an app that installs cleanly on v15/v16, runs through the job queue without breaking workers, and ships with docs and a repo they can maintain.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden Tally to ERPNext Migrator uygulamasının ZIP dosyasını indirin.
Uygulamayı bankınıza ekleyin
ZIP dosyasını tezgahınızın uygulamalar klasörüne çıkarın veya çıkarılan uygulamanın yolunu içeren "bench get-app" komutunu çalıştırın.
Sitenize yükleyin
Tally to ERPNext Migrator yüklemek ve şemasını uygulamak için `bench --site SITE_NAME install-app APP_NAME` komutunu ve ardından `bench move'u çalıştırın.
Lisansınızı etkinleştirin
Sitenizdeki ECOSIRE Lisans ayarlarını açın ve lisans anahtarınızı etkinleştirin. Ücretsiz ecosire_connect ve ecosire_license_client uygulamalarını gerektirir.
Tally to ERPNext Migrator Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Fit to your Tally file | Built and tested against your actual company export | Depends entirely on your developer's Tally knowledge | Generic mappings, assumes a clean standard file | |
| Voucher and ledger mapping | Configurable group-to-account and voucher-type mapping | Hand-coded per engagement, rarely reusable | Fixed mapping, limited overrides | |
| GST field handling | GSTIN, HSN, place of supply mapped to ERPNext tax templates | Only if the developer builds it | Often partial or region-generic | |
| Reconciliation and sign-off | Trial Balance parity + exception reports before go-live | Whatever you have time to check by hand | Usually import counts only, no parity report | |
| Large-file reliability | Queue-driven batches, idempotent re-runs | Often a one-shot script that times out | Varies; may block on big files | |
| Delivery model | Build-to-order, 2-4 weeks, fixed scope + timeline | Open-ended dev cycle, variable cost | Instant install but you fit your data to it | |
| Support and ownership | Support window + full source and git handover | Tied to the individual developer | Vendor support, closed extension points | |
| Rollback safety | Staging UAT with a documented rollback plan | Rare unless you build it in | Typically none |
Tally to ERPNext Migrator hakkında Sıkça Sorulan Sorular
+How long does delivery take?
This is a build-to-order engagement, not an instant download. Typical delivery is 2-4 weeks from confirmed scope — the range depends on the volume of Tally data, how many voucher types and years of history you need, and the number of edge cases in your ledger structure. We give you a firm timeline after the scoping call and a review of a sample Tally export.
+Do I get the source code, and can my team maintain it?
Yes. You receive the full Frappe app source for your ERPNext version and a git repository handover with commit history. It is a standard Frappe app (module, DocTypes, `hooks.py`, server/client scripts), so any Frappe developer — your team or ECOSIRE — can maintain and extend it.
+Which ERPNext versions are supported?
We build and test for Frappe/ERPNext v15 and v16. We confirm your exact bench version during scoping and target that version; if you later upgrade, the app can be updated as part of a support engagement.
+What about support and updates after go-live?
Every build includes a post-go-live support window for defect fixes and mapping adjustments on the delivered scope. Beyond that window, we offer ongoing support and enhancement engagements — for example adding new voucher types, extending GST handling, or re-running the migration for additional company data.
+How do you make sure the numbers reconcile?
We import into a staging site first and generate reconciliation reports — Tally Trial Balance vs ERPNext Trial Balance, opening-balance parity, and voucher counts by type — plus an exception log of any unmapped ledgers. You review and sign off on those numbers during UAT before we touch your production site, and there's a documented rollback plan if anything is off.
+Will it handle GST fields correctly?
Yes. We map GSTIN, HSN/SAC codes, place of supply, and your Tally GST ledgers to the corresponding ERPNext GST accounts and `Sales/Purchase Taxes and Charges` templates. The exact mapping is confirmed against your Chart of Accounts during scoping so tax figures carry over accurately rather than being approximated.
+What do you need from us to start?
A scoping call and a sample Tally export (XML or Excel) of the company data you want migrated. From that we confirm the ledger-to-account mapping, GST treatment, voucher types, and date range, then quote a fixed scope and timeline.
Teklif isteyin
Tally to ERPNext Migrator
A build-to-order Frappe app that imports Tally masters and vouchers into ERPNext with accurate ledger, group and GST mapping, opening balances, and reconciliation reports. ECOSIRE scopes, builds, installs, and supports it for your specific Tally company file.
- Tally XML import parser that reads native `Gateway of Tally > Export` output (masters and vouchers) plus a structured Excel/CSV fallback for hand-cleaned data
- Staging DocType that stores every raw Tally record with its original GUID, so imports are auditable and re-runnable without data loss
- Configurable ledger-to-account mapping that places Tally groups under the correct ERPNext `Account` roots (Asset, Liability, Income, Expense, Equity)
- Group hierarchy reconstruction — parent/child Tally groups become nested `Account` and `Item Group` trees with `is_group` set correctly