How to migrate from Tally/Excel to an ERP

What this guide covers

A decision about how to migrate from tally/excel to an erp usually arrives during ordinary work: a bill is ready, a purchase is delayed, a customer wants a date, or the owner needs a reliable number. The question becomes expensive when different people use different records to answer it. In a made-to-order engineering factory business, the immediate symptom might be a new order, material shortage and scheduled dispatch. A useful article must connect the software or procedure to that real event, identify who makes the next decision and show what proof is left behind.

This guide is written for Indian MSMEs. It treats the following as separate questions: whether a product advertises a feature, whether that feature is included in the proposed plan, whether staff can run the process with their own data, and whether the result can be reconciled with the official books. Evidence comes from vendor or government documentation listed below. Screens, prices, partner arrangements and statutory provisions can change after the research date. No unpublished feature, market-share statistic, search-volume number or customer saving is assumed.

Start with the records: stock register, chart of accounts, job cards, approved SOPs. Check the definitions: BOM accuracy, stock by location, open orders, approvals, role permissions, integrations. Watch for: dirty masters, unowned exceptions, expensive customisations. These are practical test inputs, not a verdict about a vendor.

Direct answer

How to migrate from Tally/Excel to an ERP should be handled through a controlled record, a clear owner, a sequence of checks and a documented exception path. For this topic the primary control is data cutover register. One item exists as 1 box in Tally and 24 pieces in Excel. Normalise units and reconcile physical counts before upload. The practical goal is to leave a result that another member of the business can verify later without relying on someone's memory.

This article provides a working method, an example register and a validation checklist. Any figures used in examples are illustrative. Regulatory steps are deliberately separated from practical recordkeeping so that a CA, safety expert or qualified professional can verify the current official requirements.

Records and information you need

Before starting, gather the following. Use the source named in your own company rather than recreating the information in a new sheet.

Make the first validation narrow. If the transaction relates to ₹2,40,000 of illustrative billing, confirm the customer, invoice number, quantity and amount before calculating a ratio or preparing an external document. Large reports often conceal one missing credit note or one duplicate bill that changes the decision. Where a document is absent, mark the record pending and write down who must produce it.

How to do it: detailed procedure

Step 1: Define the outcome and the trigger

Write the event that starts the work and the exact evidence required to finish it. For data cutover register, the trigger might be an incoming document, a production release, a customer demand or a closing date. Use a single identifier that all departments can recognise. Without this, later follow-up becomes a discussion of whose sheet is current. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Step 2: List the required source records

Collect stock register, chart of accounts, job cards, approved SOPs. Check document dates and responsible departments. Every copied value should have a source link or a voucher reference. If two reports disagree, do not average them; record the disagreement and resolve it in the originating system. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Step 3: Name one accountable owner

Choose the role able to confirm the final output, not merely the person who types data. State the backup role and who can authorise an exception. A clear owner must be able to answer which data cutover register items are pending and what evidence would close each item. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Step 4: Validate the first critical field

Check Opening ledger balances, party masters, item units, BOMs, godowns, batch balances, purchase/sales open documents, audit trail and sign-off. against the original register. Capture the value, date, unit and source. Note whether the entry was measured, entered from a document or inferred from someone’s message. A mismatched identity or rate should be corrected before any dependent calculation or communication is released. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Step 5: Validate the second critical field

Check Opening ledger balances, party masters, item units, BOMs, godowns, batch balances, purchase/sales open documents, audit trail and sign-off. with the role responsible for the record. For a made-to-order engineering factory business, this often means reading one transaction end-to-end rather than relying on totals. Preserve the version and transaction number so staff can re-check it later. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Step 6: Check the physical or commercial reality

Test Opening ledger balances, party masters, item units, BOMs, godowns, batch balances, purchase/sales open documents, audit trail and sign-off. using a real document, a quantity count or direct customer/supplier confirmation. Reporting is useful only if it agrees with work actually completed. Record the reason for any variance, including timing difference, partial delivery and correction. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Step 7: Test the first exception

Use a case such as One item exists as 1 box in Tally and 24 pieces in Excel. Normalise units and reconcile physical counts before upload.. Stop the standard route if a mandatory approval or safety condition has failed. Note who gets the exception, the deadline for resolution, and the evidence required before the item can continue. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Step 8: Recalculate or reconcile

Check Opening ledger balances, party masters, item units, BOMs, godowns, batch balances, purchase/sales open documents, audit trail and sign-off., if relevant, then compare the outcome with ledger, order, challan or portal values. Show both original and corrected totals. A number that adds up inside a spreadsheet may still be wrong if its units, classifications or source dates are wrong. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Step 9: Review the approval boundary

Ask whether the operator can close the task or whether owner, accountant, quality head or qualified specialist sign-off is needed. Do not silently treat a WhatsApp reply as statutory filing, a bank authorisation or an approved engineering change. Record the final approver’s decision. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Step 10: Close the action with an audit trail

Write the completion date and link the final document back to the source. Capture exceptions, reversals and any pending supporting evidence. When data is changed, preserve what changed, who changed it and why. This prevents the same unresolved item from appearing as a new problem next week. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Step 11: Measure what changed

Track both speed and correctness. Appropriate measures may include pending count, age of unresolved records, number of first-time-right entries, amount at risk or days from trigger to closure. Pick two measures the team can count by hand and compare like-for-like periods. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Step 12: Make the routine repeatable

Create a one-page checklist for data cutover register and review it at a fixed point in the week or month. Assign a backup owner. Revisit the checklist after a rejection, dispute, regulation change or repeat operational error rather than continuing to use an outdated version. Evidence to save: a source document, a signed or authorised decision, and the resulting entry in the appropriate register. What often goes wrong: the team completes the visible action but does not communicate a changed date or update the underlying record. Avoid marking a step complete until its downstream owner can see the result.

Copyable register or template

Use the following template in a paper register, Excel, Google Sheets or an existing ERP field. Copy the columns and change them to suit the particular legal or operational requirement. Entries below are illustrative, not real company information.

Status rules: Open means the responsible person has not started; pending means evidence is requested; blocked means a mandatory check failed; checked means evidence has been compared; closed means final approval or filing has been recorded. Maintain a separate reason code for reversals. Never delete a failed control just to make the total number of open items look better.

Worked example from an Indian business

Consider a hypothetical made-to-order engineering factory business. One item exists as 1 box in Tally and 24 pieces in Excel. Normalise units and reconcile physical counts before upload. Say there are 24 line items under review and 6 carry discrepancies. The initial exception rate is 6 ÷ 24 × 100 = 25%. This number measures the selected sample, not performance of all factories. After corrections, suppose 2 items still lack evidence; the remaining exception rate is 2 ÷ 24 × 100 = 8.33%. Use the same denominator when comparing periods and keep corrected items visible in the audit trail.

Now distinguish timing from underlying correctness. If a bill is dated the final day of a period but received several days later, the problem may be a cut-off or document hand-off rather than misconduct. If a rate differs from the PO, separate the price dispute from the physical receipt. If the count differs from a dispatch challan, confirm the unit, the location and any part return. The specific error dictates who should act and which record gets corrected. Reporting every discrepancy as “data issue” will hide the cause.

An additional example measure should follow the actual risk. In quality or maintenance, count rejected units, rework hours or stopped-machine hours using source logs. In purchasing, record delayed deliveries and the resulting blocked jobs. In accounts and collections, calculate a financing cost only when that supports the decision; a hypothetical ₹1,50,000 unresolved for 12 days at 12% annual interest costs about ₹592 on a simple daily basis. That is not a statutory rate. Always choose a measure that directly represents the situation.

How to handle exceptions

Missing source document: leave the entry pending, request the source from the originating role and preserve the request date. Incorrect amount, classification or quantity: stop any dependent transaction that would create an incorrect liability or customer commitment. Disputed commercial terms: separate the disputed part, keep the undisputed work moving when lawful and authorised, and record the next response deadline. Potential safety or fraud issue: stop the affected activity and involve the competent person immediately. Unclear statutory treatment: verify with the relevant official portal and qualified adviser before submitting or paying.

For this topic in particular: Plan rollback and parallel operation with defined stopping criteria. Treat a vendor help article as background, not as a substitute for a government notification or a trained professional's conclusion about an individual case. The procedures above are a business control template, not professional certification.

Measures and management review

A useful weekly review asks five questions: how many items started; how many were closed; what remains pending beyond the agreed time; which root cause appears most; and which approval sits with the owner. Make a small chart of pending age bands only after underlying records are reconciled. In a made-to-order engineering factory setting, a new order, material shortage and scheduled dispatch may otherwise be hidden under a broad “open” count.

Avoid celebrating reduced open tickets when the register has simply stopped capturing new cases. Cross-check a sample against original invoices, order messages, challans or shift entries. Ask the staff closest to the work whether the register reflects the day. If they maintain a second private sheet, discover which missing field or permission made the workaround necessary.

How lamp relates to this task

lamp's documented role is to read available orders, bills, purchase orders and stock records from connected sources, surface issues for owners, and prepare specified follow-ups that require approval before sending. Depending on the case, it can help identify missing follow-up or draft a supplier or customer request against those records. A legal filing, payroll calculation, equipment safety sign-off or accounting adjustment must remain with the applicable responsible system and authorised person. Do not claim lamp can file returns, certify compliance, automatically post to the ledger or control machinery unless that capability has been separately verified.

Frequently asked questions

What is the first action for how to migrate from tally/excel to an erp? Start with the original record and the person authorised to confirm it. Write down the exact missing evidence before creating new reports.

Can a spreadsheet handle this? Often yes for a small number of records, provided ownership, protected formulas, backups and version control are explicit. Repeated reconciliation failures signal a need for stronger controls.

When should an owner get involved? When there is a material financial exposure, a changed commercial promise, an approval beyond staff authority or a statutory or safety exception.

Can this be completed without buying ERP? The paper or spreadsheet register can be used immediately. A system investment is justified only after the critical control and its data requirements are clear.

How often should the checklist be reviewed? At the timing relevant to the transaction: each dispatch, weekly supplier follow-up, monthly finance close, or an appropriate technical interval. Do not invent a statutory interval.

What should the internal audit test? Choose completed and blocked cases, then trace identity, source record, authorisation, correction and downstream reports. Test a reversal rather than only a successful item.

Which data should stay outside public messages? Bank details, employee identities, customer-specific commercial terms and confidential drawings should be handled using authorised channels and role-based access.

What is the biggest limitation of a template? A generic template cannot interpret every product, state-specific regulation, contract or machine risk. Adapt it under the firm's policies and have the correct specialist review it.

Official sources and further reading

• Tally Help: features, accounting, stock and job work

Research date: 23 October 2026. Verify regulatory references and thresholds at publication. No market statistics or software pricing have been inferred.

Related lamp resources

• Production Delays
• Weekly Production Plan
• Order Capacity Calculator