Migrating a manufacturing company from Tally to ERPNext is different from migrating a trading or services company. Manufacturing adds BOM setup, opening WIP stock valuation, subcontracting carryover and production workflow configuration that Tally simply doesn't have.
As a general pattern, migration runs roughly 8–12 weeks for Phase 1 (accounting, inventory, VAT) and a further 4–6 weeks for Phase 2 (BOM, Work Orders, MRP, subcontracting) — actual timelines vary with data readiness and BOM complexity. Namaaly includes Tally data migration as part of every ERPNext manufacturing implementation, with Trial Balance reconciled to zero before go-live.
Why Manufacturing Migration Is Different from Trading Migration
Most Tally to ERPNext migration guides are written for trading or services companies — chart of accounts mapping, opening balances, outstanding invoices, done. Manufacturing migration has additional layers that trading migration doesn't:
- BOM setup — Tally has no Bill of Materials module. BOMs live in Excel, paper, or a production manager's head, and have to be structured and entered fresh in ERPNext.
- Opening WIP stock — semi-finished goods at various production stages need to be valued and entered with correct accounting entries.
- Item master complexity — raw materials need UOM (kg, metre, litre, piece), reorder levels, valuation method (FIFO vs Moving Average) and warehouse assignment configured correctly.
- Subcontracting carryover — material already at job workers on the migration date needs to be entered in ERPNext's subcontracting module with correct dates. (See our ERPNext subcontracting guide for Oman for the VAT considerations around job work.)
- Production routing and operations — work centres, operations and standard timings need configuring before Work Orders can be raised.
What Tally Has — and What It Doesn't
Before planning your migration, it helps to know what data actually exists in Tally versus what has to be built fresh in ERPNext:
| Data Type | In Tally? | Migration Approach |
|---|---|---|
| Chart of accounts / ledger masters | Yes | Map to ERPNext's account tree. Export from Tally, restructure, import. |
| Customer master (name, address, VAT reg. no.) | Yes | Export from Tally, clean duplicates, import via ERPNext's Data Import tool. |
| Supplier master | Yes | Same as customer — export, clean, import. |
| Item master — finished goods | Partial | Tally has item names. UOM, reorder levels, BOM linkage — added in ERPNext. |
| Item master — raw materials | Partial | Tally has names and rates. Valuation method, UOM, reorder level, warehouse — configured in ERPNext. |
| Opening stock balances | Yes | Stock Reconciliation in ERPNext — item-wise, warehouse-wise, with valuation rate. |
| Outstanding sales invoices | Yes | Opening Invoice Creation Tool in ERPNext, customer-wise, invoice-wise. |
| Outstanding purchase invoices | Yes | Opening Invoice Creation Tool, supplier-wise, invoice-wise. |
| Bill of Materials (BOM) | No | Built fresh in ERPNext from Excel/paper records, with production team input. |
| Work Orders / production data | No | No historical WO to migrate. Enter opening WIP via Stock Reconciliation. |
| Open subcontracting records | No | Entered manually in ERPNext's Subcontracting module with original dates. |
| Work centres and operations | No | Set up fresh — cutting, welding, assembly, painting, etc. with standard times. |
| VAT settings / tax templates | Partial | Item rates in Tally. VAT tax templates and Fawtara configuration handled in ERPNext during setup. |
When to Migrate — The Most Important Decision
The single most important decision in the whole migration is when to cut over. For manufacturing companies this matters even more than for trading companies, because of WIP stock.
- 1 January — generally the best option. Oman's tax year is the calendar year by default (1 Jan – 31 Dec), so this lines up with a clean books close and audited opening balances, assuming production is planned to clear WIP before cutover.
- 1 July — a reasonable second option. Half-year point, a natural interim closing.
- Other quarter-ends — possible but harder. WIP stock is more likely to be present and needs careful valuation.
- Mid-month or mid-quarter — best avoided. Creates split-period reconciliation headaches.
Where possible, plan production in the 2–3 weeks before migration cutover to complete or close open Work Orders. A factory with little or no open WIP at migration date generally has a meaningfully cleaner migration than one with dozens of partially-completed jobs. Where WIP can't be cleared, value it carefully — see Phase 1, Step 7 below.
Migration Phases — A Typical 12-Week Plan for Manufacturers
Pre-migration — data audit, account mapping, BOM collection
Export all Tally data. Build a chart-of-accounts mapping spreadsheet. Collect BOMs from the production team, even if they're in Excel or handwritten. Clean the customer/supplier master (remove duplicates, fix VAT registration numbers). This is the foundation — rushed prep tends to produce a rushed, error-prone migration.
ERPNext setup — company, masters, VAT configuration
Create the company in ERPNext. Configure fiscal year, VAT registration number, and Fawtara-related settings as applicable. Import customer, supplier and item masters. Configure VAT tax templates for your standard 5% rate and any zero-rated or exempt categories that apply.
Opening data — balances, stock, invoices, WIP
Enter opening stock via Stock Reconciliation (raw materials, finished goods, WIP). Enter outstanding sales and purchase invoices via the Opening Invoice Creation Tool. Enter opening subcontracting records. Enter a Journal Entry for other opening balances.
Reconciliation — Trial Balance, zero difference target
Run the Trial Balance in Tally and in ERPNext for the same cutover date. Compare line by line. Fix every difference before proceeding — Namaaly doesn't sign off on a migration until this is confirmed.
BOM & production — entry, work centres, operations, routing
Enter BOMs in ERPNext — finished goods first, then sub-assemblies, then raw materials. Configure work centres (cutting, welding, assembly, QC) with standard operation times. Set up costing — labour rate per hour, overhead allocation method.
Parallel run — both systems, daily reconciliation
Enter new transactions in both Tally and ERPNext simultaneously. Reconcile daily. This is generally where configuration gaps surface before full go-live — most manufacturers find a handful of issues here that would have been costlier to fix afterward.
Go-live — Tally switched off for new transactions
ERPNext becomes the system of record. Tally is kept read-only for historical reference. Training completed. All users live on ERPNext for sales, purchase, inventory and production.
Phase 1 — Accounting, Inventory and VAT (Steps 1–8)
Export Data from Tally Prime / ERP 9
From Tally, export: Chart of Accounts (all groups and ledgers), customer master, supplier master, stock item master, closing stock report (item-wise, warehouse-wise with rates), outstanding receivables, outstanding payables, and Trial Balance as of the cutover date. Export format: Excel.
Build a Chart of Accounts Mapping
Tally uses a flat ledger structure under Groups. ERPNext uses a hierarchical structure: Root (Asset/Liability/Income/Expense) → Account Type → Account → Sub-account. Build a mapping spreadsheet before touching ERPNext. Key mappings:
- Tally: Sundry Debtors → ERPNext: Accounts Receivable (individual customer sub-ledgers auto-created)
- Tally: Sundry Creditors → ERPNext: Accounts Payable (individual supplier sub-ledgers auto-created)
- Tally: Stock-in-Hand → ERPNext: Stock Assets (linked to inventory)
- Tally: Manufacturing WIP → ERPNext: Work In Progress (Current Asset)
Configure ERPNext Company, Fiscal Year and VAT
Create your company in ERPNext. Set the fiscal year (calendar year, 1 Jan – 31 Dec, is Oman's default unless your company has an approved alternative). Configure currency (OMR). Add your VAT registration number, configure VAT tax templates for your standard 5% rate and any zero-rated/exempt categories, and set up Fawtara e-invoicing configuration as applicable to your rollout phase.
Import Item Master — Manufacturing-Specific Fields
Import items using ERPNext's Data Import tool. For manufacturing companies, configure fields Tally doesn't have:
- Item Type: Raw Material, Semi-Finished Goods, Finished Goods (needed for BOM and Work Orders)
- Default UOM: kg, metre, litre, piece, box — matching how material is issued in production
- Valuation Method: FIFO (common choice) or Moving Average
- Default Warehouse: Stores, Production WIP, Finished Goods
- Reorder Level and Quantity: triggers purchase requests automatically
Import Customer and Supplier Masters
Import via ERPNext's Data Import tool. Required fields: name, VAT registration number, address, payment terms, credit limit, price list. Clean duplicates from Tally before importing. For suppliers, add supplier type (Raw Material, Service, Subcontractor) to enable filtered reports.
Enter Opening Stock via Stock Reconciliation
From Tally's closing stock report, enter opening stock in ERPNext via Stock → Stock Reconciliation — item and warehouse, with quantity and valuation rate. This is item-wise and warehouse-wise; if you have three warehouses in Tally, enter stock for each separately.
Enter Opening WIP Stock — Manufacturing-Specific
This is generally the step that makes manufacturing migration harder than trading migration. For each semi-finished item at each production stage:
- Identify WIP items: list every partially-completed job — item name, quantity, stage of completion
- Value WIP: raw material cost plus processing cost to date
- Enter via Stock Reconciliation: create a semi-finished goods item for each WIP stage, entering quantity and valuation rate, warehouse: Production WIP
- Accounting entry: debits WIP Inventory (Current Asset), credits Opening Equity — reconcile against your Tally WIP balance
Enter Outstanding Invoices and Opening Journal Entries
Outstanding sales invoices: use Accounts → Opening Invoice Creation Tool → Sales Invoice, entering customer, amount, due date and VAT details. Outstanding purchase invoices: same tool, Purchase Invoice type. Other opening items — advance payments, bank balances, loan accounts, fixed assets — entered via Accounts → Journal Entry with "Is Opening: Yes".
OMR 184,325
OMR 184,325
OMR 0.00 ✓
Confirmed ✓
| Account | Opening Debit | Opening Credit |
|---|---|---|
| Raw Material Stock | OMR 38,420 | — |
| Work In Progress | OMR 12,185 | — |
| Finished Goods Stock | OMR 24,800 | — |
| Accounts Receivable | OMR 62,412 | — |
| Accounts Payable | — | OMR 41,286 |
| Bank — Current Account | OMR 18,420 | — |
This is an illustrative mockup of what the report looks like — the figures are for illustration only, not a real client's data.
After Steps 1–8, run the Trial Balance in both Tally and ERPNext for the same cutover date and compare line by line. Don't proceed to Phase 2 until every account matches exactly. A small difference at go-live tends to compound into a much larger reconciliation problem months later.
Phase 2 — Manufacturing Modules (Steps 9–13)
Phase 2 begins after Phase 1 is live and the Trial Balance is reconciled. Accounting, inventory, purchasing and sales are running in ERPNext — now the manufacturing layer is added.
Set Up Work Centres and Operations
Before entering BOMs, configure production infrastructure: Work Centres (each machine or workstation — CNC Machine 1, Welding Bay 2, Assembly Line A, QC Station) with capacity, operating cost per hour and overhead allocation, and Operations (CNC Turning, MIG Welding, Final Assembly, Dimensional Check) with default work centre and standard time.
Enter Bill of Materials — the Most Important Step
BOM entry is generally the most time-consuming and most important step in Phase 2 — there's no Tally data to import, so BOMs are built fresh. Collect source documents (engineering drawings, Excel sheets, spec sheets, production notes). For each finished goods item, list every raw material/component, every sub-assembly (creating sub-assembly BOMs first), and every operation with standard time. ERPNext validates that sub-assembly items have their own BOMs before a multi-level BOM can be saved.
Enter Open Subcontracting Records
Material already at job workers on your migration cutover date needs to be entered in ERPNext's subcontracting module: create a Subcontracting Order with the original date, then a Stock Entry ("Send to Subcontractor") with the original transfer date, moving material into the job worker's virtual warehouse in ERPNext's stock ledger. See our ERPNext subcontracting guide for Oman for how this ties into VAT documentation for job work.
Configure MRP and Production Planning Settings
Before the first Work Order: delivery lead time per item, safety stock for finished goods and key raw materials, supplier lead time (used by MRP to set PO dates), and production capacity (hours per day per work centre). Without these, the MRP report generates unreliable procurement suggestions.
Training — Production, Stores, Accounts
Manufacturing migration generally needs more training than trading migration, since more roles are involved. A typical structure: Day 1 accounts team (sales invoicing, purchase bills, VAT invoicing, bank reconciliation, financial reports); Day 2 stores team (material receipt, stock transfer, reconciliation, reorder alerts); Day 3 production team (Work Orders, Job Cards, material issue, subcontracting, quality inspection); Day 4 management (dashboards, MRP report, profitability, receivables ageing, production variance).
Tally Manufacturing Concepts vs ERPNext Equivalent
| Tally Concept | ERPNext Equivalent | What Changes |
|---|---|---|
| Manufacturing Journal (RM issue) | Work Order → Material Transfer | ERPNext creates a Stock Entry automatically — no manual journal needed |
| Manufacturing Journal (FG receipt) | Work Order → Finish Production | Finished goods received into stock, cost of goods manufactured auto-posts to accounts |
| Delivery documentation (to job worker) | Subcontracting Order → Stock Entry: Send to Subcontractor | ERPNext auto-generates a Delivery Note from the Stock Entry |
| Production cost journal entry | Work Order close → COGM auto-posted | No manual journal — ERPNext calculates and posts actual vs standard cost automatically |
| Stock Journal (adjustments) | Stock Reconciliation or Stock Entry | Every adjustment tracked with a reason code — full audit trail |
| Godown transfer entry | Stock Entry: Material Transfer | Same concept — warehouse to warehouse with stock ledger update |
Common Manufacturing Migration Mistakes
Mistake 1: Starting BOM entry before the item master is complete
BOMs reference raw material and finished goods items. If the item master is incomplete or has incorrect UOMs, the BOM saves incorrectly and causes material issue errors later. Complete and verify the item master before starting BOM entry.
Mistake 2: Entering all opening stock in one warehouse
If you have Stores, Production WIP and Finished Goods warehouses, opening stock needs entering in each separately. Dumping everything into "Stores" produces wrong reorder calculations and incorrect production reports from day one.
Mistake 3: Not entering open subcontracting records
If open job-work material at migration date isn't entered with its original dates, your subcontracting reporting and stock ledger will be inaccurate from day one — and any VAT documentation you need to produce for that material becomes harder to reconstruct after the fact.
Mistake 4: Skipping the parallel run
The parallel run — where both Tally and ERPNext operate simultaneously for a period — surfaces configuration errors before they become live-data problems. In our experience, manufacturers who skip it tend to find an issue in the first month that takes longer to fix than the time the parallel run would have cost; this is a general pattern rather than a measured statistic.
Mistake 5: Training only the accounts team
In Tally, typically only the accounts team uses the system. In ERPNext, stores, production supervisors, quality inspectors and purchase managers all use it daily. Training only accounts and expecting production to learn on the job tends to produce incorrect Work Orders and stock discrepancies from week one.
Manufacturers who complete a proper Trial Balance reconciliation and a parallel run before go-live generally report a smoother first month-end close on ERPNext than they expected — production data and accounting are already talking to each other, rather than needing a separate reconciliation exercise. This reflects a general pattern from implementation conversations, not a specific documented case study from Namaaly's own client base.
Frequently Asked Questions
How long does Tally to ERPNext migration take for a manufacturing company?
Can BOM and production data be migrated from Tally?
How is opening WIP stock handled during migration?
When is the best time to migrate from Tally to ERPNext in Oman?
What is Trial Balance reconciliation in a Tally migration?
What does ERPNext give a manufacturer that Tally cannot?
Planning to Migrate from Tally to ERPNext?
Namaaly includes Tally data migration as part of every ERPNext manufacturing implementation — chart of accounts, item master, opening stock, WIP valuation, outstanding invoices and Trial Balance reconciled to zero. See our manufacturing implementation guide for indicative pricing tiers.