Moving from Tally, a legacy ERP or an old ERPNext version without losing a ledger. Masters and opening balances migrate with reconciliation reports; history stays where it is or moves in agreed slices; upgrades from version 13, 14 or 15 to version 16 run on a copy first with a rollback plan.
Problems we are called in for
How the work runs
The same six waypoints and three gates as every implementation.
- Survey · 2 weeks
- Chart · 2 to 4 weeks
- Build · 4 to 12 weeks by tier
- Rehearse · 3 to 5 weeks
- Cross over · 1 to 2 weeks, plus the parallel run
- Settle · 30 days
- Next leg · Optional add-on, as scoped
What is included
- Migration templates for mastersCustomers, suppliers, items, chart of accounts, and opening balances
- A dry run on a copyThen reconciliation of trial balance, stock, open receivables and payables and bank before cutover
- A written decision on which history moves and which stays in the old system for reference
- For upgradesA custom-code audit that lists what each version step will touch
- Custom work found in core moved into a separate app,So the next upgrade stays routine
- The upgrade rehearsed on a staging copy and tested by your users, with a rollback plan and a cutover date you choose
How it works: cutover without losing a month-end
We pick a cutover date at a period end, migrate masters and opening balances as of that date, and keep the old system read-only for reference. The cutover only counts as done when the first month-end has closed in ERPNext. Where Tally must stay for statutory accounts, invoices and receipts sync to it on a schedule instead, as they do every day at JAT Metal Pressing.
Proof
- Sub Zero Insulation TechnologiesERPNext upgraded from version 14 to version 16, alongside a new dealer portal whose quotations flow into it
- AdComp Systemsa 30 to 40 year-old municipal finance system replaced by a fund accounting and payroll platform on ERPNext; the first city live in about four months
- SmartCourtAdComp's legacy court application replaced in about six months, without stopping the courts that relied on it
- Living Liquidzgoods receipts synced from the legacy .NET system on a schedule while the invoice cycle moved to ERPNext, with Tally kept for accounts
Technology
- ERPNext
- Tally
ERPNextWhere we have done it
Sub Zero lets dealers configure a reefer box in 3D, in five languages
A self-service B2B portal with a real-time 3D parametric configurator, feeding the ERP.
Dealers configure and quote a box themselvesSub Zero Insulation Technologies ManufacturingJAT Metal Pressing moves from Excel to order-linked manufacturing
Sales orders drive planning, work orders, QC and dispatch at a Mumbai automotive components maker.
Delivery tracked from order to dispatchJAT Metal Pressing E-waste and IT asset recoverySheeltron refurbishes 100–120+ laptops a day with automated grading
Item wizard, serial tracking, score-based QC grading and dynamic pricing for recovered IT hardware.
100–120+ laptops a day
Government and public sector
SmartCourt: the court management platform we built for AdComp Systems
AdComp's court platform: dockets, hearings, payments and state reporting for US courts.
35,000+ cases
FAQ
Masters and opening balances migrate. Historical vouchers usually stay in Tally for reference. Where accounts must remain in Tally, we sync invoices and receipts to it on a schedule.
Yes. Upgrades run on a copy first, with a rollback plan and a checklist of custom code that needs attention.
Usually masters and opening balances as of the cutover date, with historical vouchers left in the old system for reference. Where you need history in ERPNext for reporting, we move it in agreed slices and reconcile each one.