You have picked new software. The demo looked good, the team is open to it, and everyone is keen to start. Then someone asks, "What happens to all our old data?" Often nobody has a clear answer.
Most small and mid-sized businesses in India run on a mix of Excel sheets, Tally exports, WhatsApp attachments and a few records that live only in one person's head. Moving that into a proper system is not hard, but it does need a plan. This article gives you one.
Start by deciding what actually needs to move
The instinct is to move everything. That is usually a mistake. Old data carries old errors, and importing ten years of messy records into a clean new system just makes the new system messy.
Sort your data into three groups:
- Must move: active customers, vendors, products or services, open orders, unpaid invoices, current stock, and employee records in use today.
- Move as summary: past years' sales or expenses, where you only need totals by month or by customer for reference.
- Keep as archive: old vouchers, closed jobs and historical files. Store them safely in Excel, PDF or your Tally data folder, and do not import them.
This one decision can cut the size of the migration a great deal. Your accountant should be part of it, since some records must be kept for statutory reasons whether or not they live in the new system.
Step 1: Clean the data before you move it
Cleaning is the least exciting step and the one that matters most. Do it in the original files, not after the import.
Look for these common problems:
- Duplicates. "Sharma Traders", "Sharma Traders Pvt Ltd" and "M/s Sharma Traders" may be the same customer. Pick one name and merge the rest.
- Inconsistent formats. Dates written as 05/03/2025, 5-Mar-25 and "March 5" in the same column will break an import or, worse, get read as the wrong date.
- Phone numbers and emails. Remove spaces, brackets and stray country codes so every number follows one pattern. Check that emails have an @ and a proper domain.
- GSTIN and PAN. A GSTIN has 15 characters and a PAN has 10. Flag anything that does not fit, and fix it or mark it as missing rather than guessing.
- Blank required fields. If the new software needs a customer's state to calculate GST correctly, find out which records lack it now.
- Numbers stored as text. Amounts with commas, rupee symbols or trailing spaces often import as text and cannot be added up.
A practical tip: add a column called "Checked" and mark each row once reviewed. For a few hundred records, one person can finish this in a day or two. For thousands, split it by region or product category and share it between team members who know the records.
Step 2: Map old columns to new fields
Your Excel sheet has columns. The new software has fields. They rarely match one-to-one. A mapping sheet is a simple table with three columns: where the data is now, where it should go, and what needs to change.
For example:
- "Party Name" in Tally becomes "Customer Name" in the new system.
- "Address" is one long cell in your sheet, but the new system wants separate fields for street, city, state and PIN code. Someone has to split it.
- "Status" in your sheet says "Pending", "pending", "Pndg" and "P". The new system has a dropdown with fixed options. Decide which value maps to which.
If you use Tally, you can usually export masters (ledgers, stock items) and reports to Excel or XML, depending on your version. Export what you need, then treat it like any other spreadsheet and clean it. Do not expect the export to be import-ready. Ledger groups and voucher types in Tally have their own logic that may not translate directly.
Writing this mapping down also forces useful questions early. What happens to a field the new system does not have? Do you need a custom field, or can you drop it?
Step 3: Run a small test import first
Never import everything on the first attempt. Take a sample of around 20 to 50 records that includes some awkward ones: a customer with a long name, a vendor with no GSTIN, a product with several price levels, an invoice part-paid.
Import the sample into a test environment, or a copy of the new system, not your live one. Then check:
- Did every record arrive, or were some rejected silently?
- Do names, addresses and numbers look right on screen?
- Do totals match? Pick five customers and compare their outstanding balance in the old and new systems.
- Do GST amounts and tax splits (CGST/SGST or IGST) come out the same?
- Do special characters, including Hindi or other regional-language names, display properly?
Fix the issues in your source file or mapping, then run the sample again. Repeat until it is clean. Only then do the full import.
Step 4: Choose a cut-over date and freeze the old system
The riskiest moment in any migration is the gap between "last export from the old system" and "first day on the new one". If your team keeps entering invoices in Excel while you migrate, the new system will be out of date on day one.
Reduce that risk with a simple approach:
- Pick a cut-over date that suits your business cycle. A month-end or the start of a financial quarter is easier to reconcile than the middle of a busy week.
- Do the main migration a few days earlier using data up to that point.
- On the cut-over day, import only the new entries made since then. This is a much smaller job.
- After that, the old system is read-only. No one enters new data there.
Tell the team the date well in advance and say clearly where they should enter data from that day on.
Step 5: Verify, then keep a safety net
After the full import, do a proper reconciliation. Do not rely on the screen looking right.
- Compare record counts: number of customers, vendors, products and open invoices, old versus new.
- Compare totals: total receivables, total payables, stock value.
- Spot-check at least 20 individual records by hand, chosen at random.
- Ask the people who use each record daily, such as the sales lead or the accounts executive, to look at their own data and sign off.
Keep a full, untouched copy of your old data in a safe place for at least the period your accountant advises. If something turns up later, you can trace it back to the source.
Mistakes we see most often
- Skipping the cleaning step because the deadline is close. The errors then show up in invoices sent to customers.
- Having one person do everything. If that person is on leave or leaves, nobody knows how the data was changed. Keep the mapping sheet and a short log of what was done.
- Importing straight into the live system with no test run.
- Forgetting attachments. Contracts, signed quotes and KYC documents often sit in folders or email. Decide how they will be linked or uploaded.
- Not planning for user access. Check who can see which data after the move. Imported records should follow the same permissions as the rest of the system.
What to ask your software partner
Whether you buy a ready-made product or have something built, ask these questions before you sign:
- Who does the data migration, your team or theirs, and is it included in the price?
- Which file formats can the system import (CSV, Excel, XML)?
- Is there a test environment where we can try an import first?
- How are errors reported? Will we get a list of rejected rows?
- Can we export all our data back out in a standard format if we ever leave?
The last question is worth asking even if you never plan to leave. A vendor who answers it plainly is usually one who will be straightforward about the rest.
The short version
Decide what needs to move, clean it, map it, test a small batch, set a firm cut-over date, and check the results against the old numbers. None of these steps needs special tools, only some patience and one person who owns the process.
If you are planning a move to new software and want to talk through your data, you can reach the team at Native Software.
